Automatic follow-ups when a customer doesn't reply on WhatsApp
Customers go quiet in the middle of a booking, a quote or a support case. Here is how to follow up automatically on WhatsApp without breaking the 24-hour rule, annoying people or messaging them at 3 a.m.
MonoChat Team Updated: 7 min read
On this page
- Why customers go quiet
- The 24-hour window decides what you can send
- How long to wait before following up
- How many follow-ups is too many?
- Stopping rules: when the follow-up must not go
- Respect business hours and the customer’s time
- Example: a booking flow with no-reply follow-ups
- How to measure no-reply follow-ups
- How MonoChat does it
- Sources
To follow up automatically when a customer stops replying on WhatsApp, wait for their reply with a timeout, and when the timeout passes, send a short nudge. If the customer went quiet less than 24 hours ago, the nudge can be a normal message; after that, it must be an approved template. Send one or two follow-ups at most, only during sensible hours, and stop the moment the customer replies, opts out or a person takes over.
That covers the common cases: an abandoned booking flow, a quote nobody answered, a support case waiting on the customer. The rest of this guide explains the rules, the timing and the stopping conditions that make no-reply follow-ups helpful rather than annoying.
Why customers go quiet
People rarely ignore you on purpose. Typical reasons:
- They got distracted. A call, a meeting, a child. The chat drops off the top of their list.
- The question was hard to answer. “What’s your budget and timeline?” needs thought; “Morning or afternoon?” doesn’t.
- They needed to check something. A date with a partner, a document, a photo.
- They decided no, and didn’t want to say so.
A good follow-up helps with the first three and gives the fourth an easy way out. That means short, specific and easy to answer.
The 24-hour window decides what you can send
On the WhatsApp Business API, a 24-hour customer service window opens every time the customer messages you. Inside it you can send any message: free text, buttons, lists. Once it closes, you can only start again with an approved template message, until the customer writes again.
The clock starts from the customer’s last message, not yours. So:
| Customer last wrote | Your follow-up | What you can send |
|---|---|---|
| 2 hours ago | Now | Any message, including buttons and lists |
| 20 hours ago | Now | Any message, but it’s your last chance before the window closes |
| 30 hours ago | Now | Approved template only |
| 5 days ago | Now | Approved template only |
This has a practical consequence: a first follow-up inside the window is easier and cheaper to get right. You can phrase it naturally, refer to exactly where the conversation stopped and offer buttons, without template approval. Plan your first nudge for a few hours after the customer goes quiet, not a day later.
Choosing the template category
For follow-ups after the window, Meta decides the category from the content:
- Utility: tied to something specific the customer asked for, such as “Your booking for Saturday 14:30 is still waiting for confirmation.”
- Marketing: promotional or general re-engagement, such as “Still interested? Here’s 10% off.”
Keep utility templates free of promotion; a utility template that includes an offer is treated as marketing. Marketing templates need marketing opt-in, can be limited per user by WhatsApp, and Meta’s documentation states they are currently not delivered to United States phone numbers. Our guide to WhatsApp drip campaigns covers those limits.
How long to wait before following up
There is no single right number, but these starting points work for many businesses:
| Situation | First follow-up | Second follow-up | Then |
|---|---|---|---|
| Customer stopped mid-flow (booking, quiz, form) | 15–60 minutes | A few hours later, still inside 24 hours | Close or hand to a person |
| Quote or proposal sent, no answer | 3–6 hours | Next day (template) | One last template after 3–5 days, then stop |
| Support case waiting for the customer’s info | 4–8 hours | Next day (template) | Close with a friendly note |
| Customer asked a question, then went silent after your answer | Usually none | — | Leave it; they got what they needed |
Two rules of thumb:
- Shorter waits for live flows, longer for decisions. Someone who abandoned a three-question booking flow just got distracted. Someone deciding on a €5,000 quote needs time.
- Don’t follow up a resolved question. If the customer asked your opening hours and you answered, silence means success.
How many follow-ups is too many?
One or two in most cases, three at the very most. Each extra message adds less and risks more: a block or report from an annoyed customer hurts your number’s quality, and every template costs money.
Write the last message as a real ending:
No problem if now isn't the right time. I'll close this request for now.
If you'd like to continue, just reply here and we'll pick it up.It gives the customer a way back without pressure, and it gives you a clean point to stop.
Stopping rules: when the follow-up must not go
Define the exits before you build anything. A follow-up must never go if:
- The customer replied. Even “ok”. The conversation is live again.
- A person has taken over. If an agent is handling the conversation, automation stays out of it.
- The customer opted out or asked not to be contacted.
- The goal was reached another way, for example the booking was completed on the website or the order was paid.
- The conversation was closed by an agent or by the customer.
The most common mistake is a follow-up that doesn’t check whether the customer already replied. The result is “Just checking in!” two minutes after the customer wrote “Yes, Saturday works.”
Respect business hours and the customer’s time
An automated nudge at 02:00 is a bad look, and a reply at 02:00 that nobody answers until 09:00 is worse. Two checks help:
- Customer time. Don’t send follow-ups at night or very early, in the customer’s time zone if you serve several.
- Team availability. If the follow-up invites a reply that a person must handle, send it when someone is there to answer.
If a timeout fires outside your hours, either wait and check again later, or send a message that sets expectations:
Thanks for your patience. Our team is back at 9:00 and will pick this up first thing.Mind the 24-hour window here too. If the customer went quiet at 18:00 and your hours start at 09:00 the next day, a follow-up at 09:00 is still inside the window. If the gap is longer, for example across a weekend, it will need a template.
Example: a booking flow with no-reply follow-ups
A salon’s WhatsApp assistant asks the customer to choose a time. Here is the logic:
- Ask: “Which time suits you on Saturday? [11:00] [14:30] [Another day]”
- Wait for the reply, with a 30-minute timeout.
- Reply arrives → continue the booking.
- Timeout → go to step 3.
- Check the time. If it’s between 09:00 and 20:00, send: “Still want a Saturday slot? 14:30 is still free.” If not, wait one hour and check again.
- Wait for the reply, with a 6-hour timeout.
- Reply arrives → continue.
- Timeout → go to step 5.
- Send a closing message while the window is still open, tag the customer as “booking not completed”, and close the conversation.
No template is needed because everything happens within 24 hours of the customer’s last message. For a quote follow-up that spans days, step 4 onwards would use templates.
How to measure no-reply follow-ups
Track a few numbers per flow:
- Reply rate after each follow-up. If the second nudge almost never gets answers, drop it.
- Completion after a follow-up, such as bookings or paid orders that came after a nudge.
- Opt-outs and blocks after follow-ups. A rising number means too many messages or the wrong tone.
- Follow-ups sent outside hours. Should be zero; if not, fix the time check.
How MonoChat does it
You build no-reply follow-ups in MonoChat’s workflow automation with a few nodes:
- Timeout on waiting nodes. The Question Answer node, and event nodes such as New Message Received, have a Timeout switch with a value in minutes, hours or days. If the customer doesn’t reply in time, the flow takes the Timeout output instead of the reply path. That’s your “no reply within X” branch.
- Wait. The Wait node pauses for a set number of seconds, minutes, hours or days, for example before checking again.
- Time of day and weekday. An If node can check the date, the time (such as 09:00–18:00) or the weekday, so follow-ups only go during your hours.
- Open or closed. The MonoChat Toolkit app adds an Open or closed flow node that checks your business hours for you, plus nodes such as Once per customer to avoid repeating a nudge.
- Send the follow-up. Use Send Message inside the 24-hour window and Send Template Message after it. Then Set Customer Tag, Assign Session to a person, or Terminate Session to close the conversation.
Two honest notes. There is no “wait until 9:00” node: you wait a fixed time and check the hour with an If node, or loop until the Open or closed node says you’re open. And there is no trigger for “time since the conversation started”; build it from New Session Created plus a Wait.
To start, create a free account at app.monochat.ai and compare plans on the pricing page. For ready-made wording for your follow-up templates, see WhatsApp template message examples.
Sources
Put this into practice with MonoChat