WhatsApp's 24-hour customer service window - when you can send free-form messages, when you need a template, how Avox shows it in the Inbox, automations, Calls and the API, and how to reopen a conversation.
WhatsApp separates messages a customer asked for from messages a business starts on its own. The line between them is the customer service window: a 24-hour period that opens each time a customer messages you. This is Meta's rule for every business on the WhatsApp Business Platform, and Avox follows it everywhere you can send from - the Inbox, automations, Calls and the Avox API.
The short version
Inside 24 hours of the customer's latest message, send anything. After that, send an approved template. When they reply, you have another 24 hours.
The window also shapes what Meta charges. Free-form replies inside the window carry no Meta charge. Template messages are charged per message by category, and Meta doesn't charge for Utility templates sent while a window is open. Rates and rules are Meta's and can change - see Pricing for how this shows in Avox.
Avox works out the window from the time of the contact's latest incoming message to the number you're replying from.

Avox checks the window again on the server when you press send, so a message never goes out in a window that closed while the conversation was open. In the window's final minute, Avox already treats it as closed, so a reply can't reach WhatsApp just after the window ends.
Automations reply to messages as they arrive, so their replies go out inside the window.
A call permission request - from Request calling permission on Calls, Request a call in the Inbox header, or an automation's Request a call step - is a regular message, so it uses the same window. Outside it, Avox shows "It's been over 24 hours since this contact last messaged you - send a template to reopen the conversation." For those customers, send an approved template of the Calling permission request type instead. See Calling on WhatsApp.
The Avox API sends whatever you ask it to. Outside the window, Meta refuses free-form
messages and the API returns the error code outside_messaging_window ("It's been more than 24 hours
since this person last messaged you. Send an approved template instead.") - see
API errors. Send a template message instead (see
Message types). In Meta's own terms this is error 131047, "Re-engagement
message" - see Meta error codes.
Meta can also accept a message and report shortly afterwards that it failed with 131047. You'll
see it as a failed status on Logs - open the event to see Meta's full payload.
You can try this path without a real customer: with a test key, sending to +15550000002
returns outside_messaging_window. See Testing.
Wait for the reply
When the customer replies, a new 24-hour window opens and the Inbox composer is available again.
The window counts 24 hours from the exact time of their latest message, not from the start of the day. If they wrote at 10:00 yesterday, the window closed at 10:00 today. The chat header shows Reply window closed once that happens.
No. Only the customer's messages restart the window. A long back-and-forth stays open because the customer keeps writing, not because you do.
Not with a free-form message. The window belongs to the number the customer wrote to, so reply from that number, or send a template from this one.
The Inbox composer sends text replies. Templates go out through an automation's Send a template action or the Avox API.
Yes. It's Meta's rule for every business on the WhatsApp Business Platform, so it's the same on every Avox plan.
Last updated