Running a business
Build follow-ups that know when to stop
Editorial team · Reviewed
The hardest part of a follow-up sequence is often deciding when it no longer belongs. A message that was reasonable three days ago can become awkward after a reply, a booking, a date change or a request to pause.
A practical sequence
- Write the business condition that makes each sequence relevant.
- Set stop conditions for replies, booking, changed contact details and closed opportunities.
- Give the team a visible pause control and show the next scheduled step.
- Review uncertain delivery before retrying a message with the same intent.
Work through an example
A lead receives a consultation invitation on Monday and replies Tuesday with two detailed questions. A generic Thursday reminder asking whether they saw the invitation would ignore the live conversation. The sequence stops, and the owner answers those questions.
Where judgement matters
A message already handed to an external provider may not be recallable. The interface should distinguish cancelled before sending, delivered, failed and uncertain. A reassuring label must never replace evidence about what the recipient may have received.
Make it usable
Open the working tool and change the example to match your own event. Then adapt the structured template. Keep the original assumptions visible until the people responsible have confirmed them.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
A consultation reminder is waiting when the couple replies that their venue date changed. Continuing the old sequence would ask them to book a conversation about the wrong wedding. Treat a real reply as a reason to re-evaluate the automation, even when its scheduled message was once appropriate.
| Decision | Why it matters |
|---|---|
| Define stop conditions when creating the sequence. | Reply, booking, payment and an explicit decline can each make later steps irrelevant. |
| Distinguish a delivery retry from a new campaign. | A retry must not create a second intentional message with a different identity. |
| Require review when context changes. | A changed date or service request can invalidate previously approved wording. |
Make one usable artifact
Draw a three-message sequence with waits, approval points and stop conditions. Add one owner who can inspect why a run is paused.
Then test the difficult case
A payment confirmation and a scheduled reminder arrive at nearly the same time. Explain the check that prevents the obsolete reminder from being sent.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.