Academy › Build › WhatsApp and customers
The whole sequence on one sheet
By the end, you'll have one sheet with all three reminders and their timing, the stop condition, and a test run completed before using it with real customers.
By Yodai · Published on September 6, 2026 · Updated on October 12, 2026
To win back someone who leaves a booking or a purchase half-finished, you only need a few pieces: the exact time they left, three written reminders, where the first one jogs their memory and the second one helps before offering anything in return, and the rule that a no ends that conversation.
What's missing is putting those pieces into one document you, or anyone on your team, can follow without having to think about it. A sequence scattered across your notes and your memory gets forgotten on exactly a Tuesday night at nine o'clock, when you're closing up and nobody's checking their phone.
The sheet, at a glance
The sheet has four columns and three rows, one per reminder. Nothing more. If yours has more columns, there's an undecided decision hiding as a data point; if it has fewer, there's still something you need to decide before using it.
Below the table goes something that isn't a column: the stop condition. It's not a message, it's a rule for you and anyone who helps you send the reminders. It says this: if the customer buys, books, or replies that they're not interested, the sequence stops right there, even if there are reminders left to send. A no is a no, not a silence you fill by sending one more message.
The timing, not just the content
The content of each reminder is already in the table. What decides whether the sequence helps or annoys is the wait between one and the next. Here, you combine the time the customer left with the wait you've set for each reminder. The ones in this example are for a reservation that won't disappear in a few hours; if you sell same-day tables or appointments, they're spaced much closer together.
- Minute 0The customer closes out of the booking without finishing it.
- Hour 1You send reminder 1: it just reminds them of what they left unfinished.
- Hour 24You send reminder 2: it asks if something went wrong and offers help.
- Hour 72You send reminder 3, the last one: a concrete reason to decide now.
- Hour 73 onwardIf they haven't replied or bought, the sequence ends and nothing more gets sent.
Before you let it loose on real customers
An untested sequence is a promise, not a tool. Before using it with real customers, test it at home: with your own phone, or with someone you trust acting as a customer who leaves something half-finished.
- 1Abandon a cart on purpose
With your phone, add something to your own store's cart, leave your email and phone number, and close out without paying. Write down the exact time. - 2Time reminder 1
The abandoned cart email or text has to arrive within the window you chose. If it doesn't, check that the reminder is turned on and its timing, not the wording of the message. - 3Reply that you're not interested
Have your test customer reply to reminder 2 saying they're no longer interested. Check that you cross them off the sheet and that reminder 3 doesn't go out. If it does, the stop condition isn't clear on the sheet. - 4Finish the purchase partway through
In a second test, let reminder 1 arrive and then complete the purchase. Reminder 2 shouldn't go out. If it does, whoever's sending the reminders isn't checking first whether you already bought. - 5Repeat it at a different time of day
Test once during the day and once at night. Check what time the abandoned cart reminder would reach someone who leaves their cart at eleven at night, and if it lands in the middle of the night, change the timing.
- The sheet with the three reminders, their send time, and their goal, written down and saved.
- The stop condition placed right below the table: a purchase, a booking, or a no closes the sequence right away.
- The test run on your own phone: abandonment, reminder 1, a not-interested reply, and confirmation that reminder 3 never arrives.
- The sequence in use with real customers, with an alert for each reminder, not just written down in a document.
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. A customer books by phone at 8:00 p.m., right after leaving a WhatsApp booking half-finished at 7:00 p.m. At 8:30 p.m., reminder 1 shows up, nudging them about the booking they left unfinished. What's wrong with the sheet?
It's not the wording of reminder 1 that's wrong, it's the stop condition: whoever's sending the reminders isn't checking whether that customer already has a booking before sending the next one.
2. Reminder 2 asks if something went wrong with the booking, and the customer replies, "No thanks, I'm not interested anymore." Ten minutes later, reminder 3 arrives anyway with the limited-spots message. What do you decide?
The whole sequence stops for that customer, and you review which phrases count as a no before using it again; a no on reminder 2 has to close out reminder 3 too, not just stop the second message.
3. You've been using the sequence for two weeks, and reminder 3 barely gets any bookings, while reminder 1 does. Do you turn off reminder 3 or change it?
Change it before turning it off: check whether the reason it gives, limited spots or this week's price, is true and specific to your business; a generic reminder 3 doesn't convince anyone, and turning it off just hides the fact that it's not giving people a real reason to decide now.