The WhatsApp 24-hour window, and why your reply was refused
By Super Admin
A customer messages your business on Friday evening. On Monday morning an agent opens the conversation, types a reply, and WhatsApp refuses to deliver it.
Nothing is broken. This is the single rule that surprises almost everyone moving from the WhatsApp Business app to the Cloud API, and it is worth understanding properly rather than working around.
The rule
A business may send free-form messages to a customer only within 24 hours of that customer's most recent message.
The clock starts on their message, not yours. Every new inbound message restarts it. Outside that window, a free-form message is rejected by Meta — it does not reach the customer and it does not sit in a queue.
This is called the customer service window. It exists because WhatsApp is, to its users, a personal messaging app. The window is what stops a business they contacted once in March from messaging them in July.
What you do instead: templates
To start a conversation outside the window — or to begin one at all — you send a message template: a format approved by Meta in advance, with variables for the parts that change.
Hi {{1}}, your order {{2}} is out for delivery and should arrive by {{3}}.
Approval is usually quick, often minutes. You are approving the shape, not each send, so one approved template serves every order update you will ever send.
Three things worth knowing before you write one:
Every variable needs an example. Meta requires a sample value for each placeholder at submission time. Templates are rejected for omitting these more often than for anything about their content.
Categories are enforced. A template submitted as Utility that reads like marketing will be re-filed as Marketing by Meta rather than rejected — which is better, but changes what it costs and who may receive it.
Once a template lands, the window re-opens. The customer's reply restarts the 24 hours, and from there you are back to ordinary free-form conversation.
Messenger and Instagram are not the same
The 24-hour standard window applies on Messenger and Instagram too, but there is an additional allowance that WhatsApp does not have.
The Human Agent feature lets a human — not an automation — reply up to seven days after the customer's last message, by attaching a HUMAN_AGENT tag to the send. It exists for exactly the Friday-to-Monday case: a business closed for the weekend, answered by a person when the office opens.
It is requested in App Review under Features rather than Permissions, which is why it is easy to build a Messenger integration, never request it, and discover months later that every reply between hour 24 and day seven has been failing.
So, roughly:
| Free-form window | Beyond it | |
|---|---|---|
| 24 hours | Approved template only | |
| Messenger | 24 hours | 7 days with Human Agent, for human replies |
| 24 hours | 7 days with Human Agent, for human replies |
What this means for how you work
Speed stops being a nicety. On every other channel, a slow reply is rude. On WhatsApp it changes what you are permitted to send. A business that answers within hours never meets this rule; one that answers in two days meets it constantly.
Your tool should know. An inbox that lets an agent type a reply, send it, and then report a failure has wasted their time and taught them to distrust it. It should know the window has closed before they start typing, and offer the template picker instead. Ours tracks the last inbound timestamp per conversation and blocks the send path rather than letting Meta refuse it.
Templates are infrastructure, not marketing. Most businesses need three or four: an order update, a delivery notice, an appointment reminder, a "we're reopening your enquiry". Writing them once removes the problem permanently.
Don't try to keep the window open artificially. Sending something trivial to restart a clock is both against the spirit of the rule and visible to WhatsApp in your quality rating. The window is not an obstacle to route around; it is the thing that keeps WhatsApp usable enough that your customers are on it.
The part people get wrong
The most common misreading is that this is a rate limit or a spam filter that a better integration can avoid. It is not. It is a policy, enforced at the API, identical for every provider. Any tool promising to send free-form WhatsApp messages outside the window is describing something that will not work, and the number it is working from is likely to end up banned.
The second most common is assuming templates are for marketing. Most template traffic is service: order updates, delivery windows, appointment reminders. The template system is how WhatsApp lets a business be useful without letting it be a nuisance.
OmnioChat tracks the window per conversation, blocks free-form sends once it closes, and offers the template picker in the same place — so an agent finds out before they type, not after.