Follow Up
Follow up makes the agent get back in touch with whoever stopped replying in the middle of the conversation. It's optional, and starts turned off.
By the end of this guide you will know how to build the sequence, read the summed-up timeline and avoid the classic mistake of setting a delay nobody checked.
When it acts
Only for a conversation interrupted midway — never for a conversation already resolved or transferred. And any reply from the customer cancels the sequence: they go back to normal service, from where they left off.
The sequence
Each step begins when the previous one's delay ends. There are up to three attempts, plus the outcome:
After 6 hours without a reply
→ write the message on the spot, based on the conversation
After 2 more days
→ send a fixed text
"Hi! Just checking whether you're still interested 😊"
Still no reply for another 24 hours
→ end the conversationThe two message modes
Write the message on the spot — the agent writes it looking at the history, so the message makes sense at the point where the conversation stopped. You can give an optional hint ("if they talked about price, offer the price list"). Uses one credit per send.
Send a fixed text — goes out the same for everyone, word for word, and doesn't know where the conversation stopped. Costs nothing.
A good pattern is to write the first one on the spot — when context still matters — and use fixed text for the last one.
The outcome
The last step isn't an attempt: it's what happens after it. End the conversation, or transfer to a sector. Note that it also has a delay — the agent doesn't end the conversation the instant it sends the last message.
Read the summed-up timeline
The right-hand column shows the math nobody does in their head:
attempt 1 at 6h attempt 2 at 2d 6h Ends at 3d 6h
This is where you notice that adding attempts adds waiting time. Three attempts of two days each leave the conversation open for almost a week — which may be exactly what you want, or a surprise.
How to know it worked
- In the menu, Follow Up shows the attempt count.
- The timeline on the right matches what you had in mind.
- In Recent runs (⋯ menu), resumed conversations show up with the follow up being sent.
Common problems
I changed the delays and the stalled conversations didn't follow the new timing. Cause: the change applies to the next ones, not to those already in the queue. How to check: delays are calculated when the conversation stalls. Solution: expected — stalled conversations follow the delay that applied when they stalled.
The customer replied and still got a follow up. Cause: the reply came through a path that wasn't associated with the conversation. How to check: open the conversation and see whether the customer's message is there. Solution: if it is and the follow up went out afterwards, report it — the reply should cancel the sequence.
I can't add a fourth attempt. Cause: the limit is three. Solution: if you need more persistence, increase the delays or use the outcome to transfer to a sector instead of ending the conversation.