The message goes at its time and stops when it is no longer needed
Follow-up that works is not sending three messages; it is the sequence stopping at the right moment. A customer who bought and then receives "you did not finish your order" loses trust once and for good. The whole difference is the stop condition, not the copy.
- A time you set
- Stops on a reply or a purchase
- On approved templates
Any message that opens a conversation outside the 24-hour window needs a template Meta approved in advance.
Why follow-ups sometimes annoy
The reason is always the same: a message that arrived after the need for it ended. A reminder for a cancelled appointment, a cart follow-up for a cart already bought, an offer on a product delivered yesterday. The fix is not fewer messages but tying them to the customer's real state: if they reply, buy or cancel — it stops.
Building a sequence
Pick the trigger
A booked appointment, a completed order, an abandoned cart, or a fixed date you set.
Set the timing
24 hours before the appointment, or three days after delivery — in the customer's time zone, not yours.
Write the stop condition
The most important step: they reply, buy or cancel — and the rest of the sequence halts at once.
Approve the template
Anything sent outside the 24-hour window needs a Meta template. Utility templates are usually approved the same day.
What you can schedule
Appointment reminders
A day and an hour before, with a reschedule button. The single biggest reducer of no-shows in clinics and service centres.
Post-delivery follow-up
A message a few days later asking how the product is, opening the door to a second order — and usually a conversation the customer continues, so its replies are free for the first 1,000 per number each month.
A sequence that stops itself
Three messages on timing you set, and any reply or purchase halts the rest. You never chase someone who no longer needs chasing.
In the customer's time
A message landing at 3am reads as a nuisance whatever it says. Scheduling respects the recipient's time zone and your working hours.
Scheduled versus broadcast
| A broadcast to a list | ArabyBot | |
|---|---|---|
| Timing | One time for everyone | Each customer's own event |
| Someone who already bought | Gets the message anyway | The sequence stops |
| An appointment reminder | Does not fit | Exactly the purpose |
| A stop condition | None | On every sequence |
Questions people actually ask
Can I schedule a message to any number?
Only to people who opted in. Sending to a list that did not collects reports, lowers your number's quality rating, and then stops it.
What is the difference between scheduled and broadcast?
A broadcast is one message to a list at one time. A scheduled message is tied to an event specific to each customer — their appointment, their order — so each lands at its own different time.
Does the sequence stop if the customer replies?
If you set it that way, yes — and we always recommend it. A reply means the conversation is alive, and any automated message after it reads as though nobody read what they wrote.
Send at the right time, and stop at the right time
Reminders and follow-ups · a stop condition on every sequence · on approved templates
Start free