Sales Automation
How to Automate WhatsApp Follow-Ups After 24 Hours Without Sending Outdated Messages
The hard part is not scheduling another message. It is deciding whether that message is still appropriate when the scheduled time arrives.
A buyer asks for a quotation on Monday. Your system schedules a reminder for Thursday. On Wednesday, the buyer calls, accepts the offer and pays. On Thursday, the reminder still asks whether they are interested.
That is the failure a good follow-up process should prevent. Automating WhatsApp follow-ups after 24 hours requires both the correct sending method and a fresh decision about whether the message still belongs in the conversation.
Understand the customer service window
For WhatsApp Business Platform messaging, Meta’s Business Messaging Policy permits free-form replies within 24 hours of the user’s last message. Outside that window, an approved template is required. Sending a template does not itself reopen the window; a new user message does. Permission and opt-out requirements still apply.
These rules concern the Platform. Do not assume that a timer shown in a CRM describes every messaging route in the same way. Confirm which channel your automation actually uses.
Write a follow-up with a specific purpose
Decide what the message should help the customer do: clarify a quotation, confirm an appointment or answer a remaining question. “Increase engagement” is too vague to write a useful customer message.
For a quotation, a draft might be:
Hello {{name}}, would it help to review any part of the quotation for {{requirement}}? Reply here and our team can help with the next step.
This is an original writing example, not an approved template. Submit the appropriate template through your provider’s process and use the category Meta assigns or approves for its actual purpose. Do not assume that mentioning a quotation makes a message a utility message.
Check eligibility again when the message is due
The record may have changed since scheduling. Before sending, the workflow should evaluate the latest state, not only the state that triggered the original schedule.
- Is contact still permitted, with no opt-out recorded?
- Is the opportunity still open and relevant?
- Has the customer replied or asked for a different date?
- Has the team completed the action through a call or another channel?
- Are a human conversation or a complaint currently active?
- Is the template available, and are all required values accurate?
- Is this a sensible time for the recipient?
If a required fact is missing, route the item for review instead of filling the gap with a guess.
Define stop, pause and reschedule separately
| New event | Suggested workflow response |
|---|---|
| Customer opts out | Stop applicable outreach and record the preference. |
| Order or booking confirmed | Stop sales reminders; use the relevant service process. |
| Customer replies with a question | Pause the stale nudge and assign the question. |
| Customer requests a later date | Replace the previous plan with the agreed timing. |
| Delivery fails | Inspect the reason before scheduling another attempt. |
These are recommended controls to configure and test. Do not assume every CRM implements them automatically just because it has a scheduling feature.
Test the awkward cases before a wider launch
Start with a small authorized test set. Include a customer who replies just before the reminder, a lead marked won after a phone call, a missing template variable and a delivery failure. Check the final outcome as well as the schedule screen.
Ask whether the workflow checks for duplicate sends if a task retries. Ask how a staff member can see why a message was skipped. A skipped reminder may be the correct result, especially when the customer has already moved forward.
Apply the process in SHVYA
Design the cadence around your actual pipeline and communication channel. During SHVYA setup, agree which events stop or change follow-up, who owns exceptions and how staff record outcomes from calls. Request a demonstration of the configured behavior before enabling it for live leads.
For message wording, use our quotation follow-up examples. If a scheduled message is accepted but never reaches the customer, use the delivery troubleshooting guide instead of adding more reminders.
Good automation remembers that the conversation can change. Its most useful action may be deciding not to send the message you planned three days ago.
