The quick answer
Permission explains whether a person wants to hear from your business. The 24-hour window explains when you can reply without an approved template. They solve different problems, so check both before sending.
A customer asks whether a sofa comes in blue. Your team answers, sends a photograph and promises to confirm availability tomorrow. The next afternoon, the reply box asks for a template. Nothing has necessarily broken: the conversation may simply have moved outside its service window.
Understanding this distinction makes WhatsApp easier to operate. Your staff can choose the right next step instead of repeatedly pressing Send, switching numbers or treating an old customer list as permission for every future promotion.
Start with two separate checks
WhatsApp’s policy requires appropriate recipient permission, and permits free-form replies during the 24 hours following the customer’s latest message. Outside that window, messages must use approved templates. A template approval does not itself prove that a particular recipient agreed to receive that message.
Give your team two questions: “Does this person expect this communication?” and “Which message format is allowed now?” Recording those answers separately is clearer than a single label called approved. A past purchase, imported telephone number or open deal should never silently answer both questions.
| Check | What your team should look for |
|---|---|
| Customer permission | What was agreed, for which business and purpose, and when |
| Service window | The time of the latest message from the customer |
| Message format | Free-form reply or the appropriate approved template |
| Contact preference | Any later request to stop or change the communication |
Follow the customer’s message, not your own
Imagine a customer messages at 10:00 on Monday. Your team replies at 10:15. The business reply does not create a fresh 24 hours. If the customer writes again at 16:00, that new incoming message is the event that refreshes the window.
Now imagine nobody replies until Tuesday afternoon. The useful action is to select a suitable approved template, with the correct purpose and language, or wait for the customer to contact you. Sending a reminder to yourself, reopening the conversation screen or changing its assignee does not alter the customer’s last-message time.
Use the displayed window status as a working aid, then investigate unexpected restrictions. A delayed receipt, disconnected number or account problem is a different issue. Teams should not explain every failed message as “the window” without checking its actual outcome.
Collect permission people can understand
A useful permission request names the business and describes the messages. For example: “Send me booking confirmations and changes from Oak Studio on WhatsApp.” If the business also wants to send offers, make that choice understandable rather than hiding it inside a long purchase form.
Keep evidence that helps a colleague explain the choice later: the wording shown, the source form or interaction, the date and the contact. Avoid collecting extra personal information just to prove a simple preference. Decide who can view the evidence and how corrections are handled.
- Use plain language that fits the actual service.
- Keep optional promotional preferences separate from essential service choices.
- Make the preferred contact channel easy to change.
- Review imported lists before they enter an active audience.
Choose a template for the actual purpose
Write down what the message is trying to achieve before choosing its template. Confirming an existing appointment and promoting a new service are different tasks. A template name such as “customer_update” should not obscure the substance of the message.
A clear service update might say that the requested quotation is ready and offer a way to continue. Adding an unrelated discount can change the nature of that communication. Review the current category and approval status in the connected account rather than assuming an old approval covers every new variation.
Maintain a small library your team can navigate: confirmations, changes, requested follow-ups and relevant promotions. Include a short internal note explaining when to use each one. This is often more valuable than hundreds of nearly identical templates.
Treat a stop request as a customer instruction
A customer may ask to stop in ordinary language rather than using a precise keyword. Give staff a clear process for updating preferences and stopping scheduled outreach. The change needs to reach campaign audiences and queued follow-ups, not remain buried in a chat note.
Suppose a customer opts out of offers but later asks about an existing order. Handle that service question without automatically adding the person back to the promotional audience. A helpful response and a new marketing preference are separate decisions.
Agree how your business handles accidental contact: acknowledge the problem, correct the preference and investigate its source. Re-importing the same spreadsheet next week should not undo that correction.
Build a short pre-send routine
In Wamigos, use the conversation history and contact preferences as the starting point for the next action. Before enabling a flow or campaign in your connected workspace, walk through one customer with an open window, one outside the window and one who has asked to stop.
This is operational guidance, not a substitute for the current WhatsApp policies or advice about the law applying to your business. Rules, categories and account eligibility can change. Keep an owner for policy reviews, especially when expanding into another country or a regulated service.
Identify the purpose
Explain in one sentence why this person should receive the message now.
Check preference and timing
Review the permission record, latest incoming message and any stop request.
Choose and preview
Select the allowed format and check names, links, variables and language.
Observe the result
Review delivery or failure information before deciding whether any follow-up is appropriate.
Common questions
Does my reply restart the 24-hour window?
No. The relevant event is a new message from the customer. Do not calculate the window from the last message your business sent.
Does an approved template let me contact every number in a spreadsheet?
No. Template approval and recipient permission are separate. Review the audience and its contact preferences before sending.
Can a previous buyer receive all our future offers?
A purchase alone should not be treated as an unlimited preference for future promotions. Establish what the customer actually agreed to receive.
Are messages inside the window completely free?
Meta messaging charges and your software provider’s charges are separate. Check both current pricing arrangements instead of equating a service window with zero total cost.
What should an agent do when the reply box requires a template?
Check the latest incoming message and choose an appropriate approved template if contact is permitted. If the status seems wrong, investigate the conversation and connection before retrying.
Sources & further reading
Primary documentation reviewed 16 November 2026. Provider rules, pricing and eligibility can change. Check the linked source before making account or billing changes.






