Solved

Staying up to date with an on-going flow . . .

  • 18 March 2022
  • 1 reply
  • 15 views

Badge +1

I’m starting an on-going “educational email” flow. 

I’ve written the first few so far spaced about a week apart, but I want to start opening it to people, then write an email or two a week to keep it rolling in close-to-real-time. (I don’t have the capacity to write weeks and weeks into the future.)

 

But I want to build in a safeguard so if I run behind, people don’t accidentally EXIT the flow. 

 

So I’ve sent the Time Delay after the current final email at 60 days. 

 

Check me on this:

If “Bob” has received the last email in the flow (eg, Email #4), and is sitting inside that 60 day holding period...

and something happens where I don’t get Email #5 written for 10 days since Bob got email 4...

I would be able to slip in a new time delay of 11 days, pop in Email 5, and Bob would receive #5, then go back to my 60 day holding tank till I get another one in there. 

Right?

icon

Best answer by Dov 18 March 2022, 17:07

View original

1 reply

Userlevel 7
Badge +61

Hi @matt.steinruck,

Thanks for sharing this question with us!

Not quite! A couple of notes on this.

First, we’ll only “hold” people in a time-delay if there is an email following a time-delay. If you simply had a “hanging” 60-day time delay with no email after that delay, then Bob would never be queued-up in the delay to begin with.

Now, let’s say you did have an email after that 60-day time-delay, Bob would be queued-up to receive the next email in 60 days. Once a user is queued-up in a time-delay, they will stick with the original timeline of the delay, even if you were to later swap out that time-delay for a different length time-delay. For example, Bob receives email 4, now enters the 60-day time-delay, waiting for email 5, now you switch that 60-day to a 10-day, Bob will still be queued up to receive email 5 in 60 days. So in short, once a user is queued-up for a certain delay, they “stick” with that timeline.

You also cannot “reshuffle” a user in a flow by moving time-delays around the flow, they’ll always be queued-up for the original email they’re meant to be queued-up for. I recommend checking out our article How Contacts Move Through a Flow (specifically the example with “Becky” on this point) and also just for more general insight on this topic.

Alternatively, considering your goal, you may want to consider sending bi-weekly campaigns to this group of users to simplify the process. 

With respect to building out the email templates themselves, I recommend checking out our article on managing templates, which guides you through cloning and saving existing templates (if say, you just want to tweak an existing template slightly for the next email in the sequence and re-use it).

Also, make use of the Klaviyo Showcase featuring the best-performing campaigns for ideas and inspiration.

I hope that clears things up. Thanks for being a member of our community.

Reply