By Nudge team
A practical guide for business and operations teams
Updated
The customer’s message starts the service window
The useful timestamp is the customer’s latest inbound WhatsApp message. Save that time when the message arrives through the official platform. Do not calculate from when a staff member opened the inbox, when the AI generated a reply or when the business sent its last message.
This sounds simple, but it changes how a team works. If a customer writes on Monday afternoon and the business replies on Tuesday morning, the Monday message still controls the original deadline. A new message from the customer creates a new service context; a string of business reminders does not.
Use Meta’s current WhatsApp Business Platform documentation as the final source for live platform behavior. Product rules can change, so operational teams should review the current documentation before altering a production workflow.
A business reply does not restart the clock
Treat the clock as a customer-controlled boundary. If your team or automation sends another free-form message, that outbound message does not create more time. This prevents a workflow from extending its own permission simply by continuing to send.
The safest implementation stores a dedicated “latest customer message” value and never overwrites it with an outbound timestamp. Staff can still see the full conversation, but the sending decision should read from the customer timestamp every time.
CustomerCan you share the available appointment times?
BusinessYes. I’ll check the calendar now. Is Thursday or Friday better for you?
The reply is tied to the customer’s request. Save the latest inbound time and the next action.
Inside the window, continue the service conversation
An open window is not permission for an AI to say anything. Replies should stay grounded in business-approved services, prices, hours, policies and actions. If the answer is missing or the customer asks for a person, hand the conversation to the team.
Use the open period to complete useful work: answer the question, collect only the details needed for the next step, check real availability, make a booking or record an agreed handoff. Avoid filling the conversation with repeated nudges merely because a free-form reply is technically available.
Outside the window, use an approved template when appropriate
When the service window has closed, a business-initiated message should follow the platform’s approved template path. The template category and wording must match the real purpose. An appointment update should not hide a promotion, and marketing language should not be presented as a transactional notice.
Approval is not a permanent guarantee that every future send is suitable. Before sending, check whether the customer has replied, booked, opted out or entered a conversation with a staff member. Cancel stale work instead of sending a message that no longer makes sense.
The free WhatsApp 24-hour window and template checker helps a team reason through this choice. It is a planning aid, not a substitute for Meta review or legal advice.
Keep consent separate from the 24-hour timing decision
Timing does not replace consent. Send marketing only when the contact has opted in, keep evidence of that choice and honour later opt-outs. If someone says STOP, marketing must stop even if a window is open or a campaign was already queued.
A marketing opt-out and an active service request are different. Do not send promotions, but keep a genuine booking, support issue or requested update assigned to the right person. The contact’s choice should not make their open service request disappear.
Put the rule in the sending code, not only in an AI prompt
A reliable system checks the latest inbound timestamp immediately before every free-form send. It also checks consent before marketing and checks whether a human has taken control. These are application rules. Asking the AI to “remember the policy” is not enough.
Queue workers should repeat the same checks because circumstances can change after a message is scheduled. A customer may reply, a teammate may take over or an opt-out may arrive. The final send gate should always use current records rather than the state captured when the job was first created.
See the broader WhatsApp AI lead follow-up workflow for how timing, next actions, templates and human ownership fit together.
Use this checklist before every automated follow-up
- Find the customer’s most recent message, not the business’s most recent reply.
- Calculate how much time has passed since that customer message.
- If the service window is open, answer only within the business’s approved scope.
- If it is closed, use an approved template for business-initiated contact.
- Before marketing, verify recorded opt-in and check for any later opt-out.
- Stop scheduled messages when the customer replies or a person takes over.
The goal is not to maximize the number of messages. It is to make every useful next step happen without sending the wrong message at the wrong time.