Log inStart Free Trial
Meta Tech Provider

Automatic follow-ups on WhatsApp: the wait step and template reminders

An automatic WhatsApp follow-up is a message sent after a set delay when the customer has gone quiet. Within 24 hours of the customer's last message, any text can go out through the API; after that, Meta delivers only an approved template, to someone who opted in. A good follow-up is canceled when the customer writes again or a person replies from the phone.

easyCoexistence adds Wait steps of up to 23 hours to WhatsApp automations, with follow-ups by text, AI, approved template or your own system, on the number you keep using in the WhatsApp Business app.

1,380 min

Longest single Wait step, 23 hours, so the next text step still lands within 24 hours of the customer's message.

24 hours

When the customer service window closes, Meta accepts only pre-approved template messages from the API.

App exempt

Messages sent from the WhatsApp Business app are not subject to the customer service window, per Meta's Coexistence guide.

2 conditions

Meta's opt-in rule: the person gave you their number, and you received their opt-in to receive your messages.

30 steps

Most steps in one line of an automation, 60 in all with branches, enough to chain several waits before a template reminder.

How does the Wait step work?

Wait, described as "Pause before the next step", holds a run for 1 to 1,380 minutes and then carries on with the next step. While it waits, the run shows Waiting in the Runs tab. When the time is up, the runner checks whether you replied to that chat from the WhatsApp Business app since the run began, before it sends anything; if you did, the run ends with "You answered this chat from your phone recently", whatever the pause setting says. A test never waits: "Try it" shows "Would wait 120 min" and runs the next step at once, so you can read the follow-up text right away.

What cancels a follow-up that is waiting?

Your reply from the phone ends it. A newer message from the customer ends it too, but only when that message starts the same automation again: the waiting run is marked "A newer message from the customer took over" and the new run starts from step 1. Switching the automation Off, turning automations off for the number or a refused key for the AI it uses also stop it. What does not cancel it trips people up: a customer reply that goes to a different automation, or to none, leaves the wait running. So put follow-ups in the automation that also catches the customer's replies, which is usually the Every message one.

What can a follow-up send, and when?

It depends on the time since the customer's last message, because Meta's 24-hour rule applies to what the API sends. One wait of up to 23 hours keeps the next text step inside that window. Waits that add up to more can push past it: a Reply with text or Reply with AI step there is skipped with "More than 24 hours since the customer's last message", while a Send a template step still goes out. Meta bills your own WhatsApp Business Account, with no markup from us: service messages after a free tier of 1,000 per number each month, templates per message by category and country.

Within 24 hours of the customer's messageAfter 24 hours
What can be sentAny text: Reply with text, Reply with AI, or your webhook's replyAn approved template only, with Send a template
How to build itOne Wait of up to 1,380 minutes, then a text or AI stepWaits adding up past 24 hours, then Send a template; or your AI or system sends it
What it needsThe window the customer's message openedAn approved template and the customer's opt-in
From the phone appYou write as usualYou can still write as usual: the app is not bound by the window

How do you send a template reminder after 24 hours?

Four ways, all through the API, because the WhatsApp Business app cannot send templates. Inside an automation, chain Wait steps past 24 hours and end with Send a template: pick an approved template of the number, its language code and its body variables; templates with named variables, a header picture or header variable, or a button with a variable cannot be picked yet. From your AI, ask "send the quote_reminder template to 5511999998888 with Ana as {{1}}", and ChatGPT or Claude calls send_template through the MCP connector. From your own system, send it through the Cloud API with the credentials get_api_credentials returns, or have it call the URL of an automation that starts from a webhook (the Updates from your system example) with the customer's phone as "to": its Send a template step fills the variables from the rest of the body, such as {{vars.webhook.name}}. A new template goes to Meta review first, with create_template or in WhatsApp Manager; approval usually takes minutes and can take up to about 24 hours.

Which follow-ups can you build today?

Four patterns that use only what the editor offers. Read each one left to right, in the order the steps appear in the diagram. The Wait goes right after the reply you are following up, and the automation that holds it should be the one that also catches the customer's next message, or the follow-up goes out even after they answer.

AI assistant with a 2-hour nudgeEvery message, Reply with AI, Wait 120, Reply with text. A new message restarts it, so the nudge goes out only after 2 quiet hours.
Away message, then a morning checkAfter hours, Reply with text, Wait 600, Reply with text "We're open now, do you still need help?" Your reply from the phone before then cancels it.
Next-day template reminderEvery message, Reply with AI, Wait 1,380, Wait 60, Send a template. It reaches anyone quiet for a day, so use it only if they all opted in.
Your system decidesEvery message, Reply with AI, Wait 1,380, Call my webhook. Your system returns {"reply": "..."} only when it has news; no reply sends nothing.

What keeps follow-ups welcome rather than spammy?

Meta's rules and your quality rating. Business-initiated messages need opt-in: the person gave you their number and agreed to hear from you. Meta's opt-in guidance notes that people can block or report a business, and that a quality rating that stays low leads to limits. One nudge after a silence reads as service, while a chain of reminders reads as pressure. Make the follow-up useful on its own (the quote, the booking link, the order status), say how to stop the messages, and honor a stop request made on any channel. Skipping chats you already handled by phone is built in, because your reply cancels the wait.

How to set it up

  1. Open the automation that answers the chatOn the Automations tab, open the automation that replies to customers, ideally your AI assistant on Every message.
  2. Add a Wait after the replyClick the + below the reply step ("Add a step here"), choose "Wait" and set Minutes to 120.
  3. Add the follow-upClick the + below the Wait and choose "Reply with text" with the nudge, such as "Hi {{first_name}}, any questions about the quote?"
  4. Save and testPress Save, then Test and "Run test": the result shows "Would wait 120 min" and the nudge, and nothing is sent.
  5. Watch the first real runsIn the Runs tab, a quiet chat shows Waiting and then Done; a chat you answered shows Skipped, with your phone reply as the reason.

Common mistakes

  • Putting the follow-up in a keyword automation. The customer's reply rarely repeats the keyword, so another automation takes it, the wait is not canceled and the nudge still goes out; put it in the Every message automation.
  • Ending a chain of waits past 24 hours on Reply with text. That step is skipped with "More than 24 hours since the customer's last message"; end on Send a template instead.
  • Sending reminders to contacts synced from the app. A contact in your phone is not opt-in, and blocks and reports from people who never asked lower the number's quality rating.
  • Expecting Reply with AI to decide whether to follow up. It must write something, and an empty answer fails the run; for choices use AI picks the path, Split into paths on a tag or field, or Call my webhook.
Doing this with EasyCoexistence

Your reply from the phone cancels a waiting follow-up on that chat. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

Can I follow up on a message I sent from my phone?

Not automatically: runs start from a customer's message, from a tag added to a contact or from a call to a webhook automation, never from a message you send. Tag the contact in Conversations to start a tag automation, follow up from the app yourself, ask your AI to use send_message within 24 hours of the customer's last message or send_template after that, or have your system watch your app echoes through a forward URL.

How many follow-ups can one automation send?

As many as fit in 30 steps per line, with each Wait up to 1,380 minutes: for example a reply, a wait, a nudge, two more waits and a template. Keep it to one or two, since each extra message is one more chance for a block or a report.

Do follow-ups respect my opening hours?

No. A Wait counts clock minutes, day or night, and there is no option to resume only while you are open. Pick a delay that lands at a sensible hour for most chats, put a Split into paths step after the Wait with an hours rule (open or closed) so the follow-up goes only while you are open, or let Call my webhook check the time and reply only when it suits you.

Do follow-ups count against the AI reply limit?

Only Reply with AI steps do: each one counts toward "AI replies per chat per hour, at most" for that chat. Text, template and webhook follow-ups never touch that limit or your AI key.

Keep reading

Ready to get started?

Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.

Start Free Trial

Verified on