The WhatsApp 24-hour window, explained without the jargon
Why you can reply freely for 24 hours and then suddenly cannot, what resets the window, and how to handle the customer who answers on day three.
Every business new to the WhatsApp Business API hits the same wall in week one: a reply that worked yesterday is refused today. The 24-hour window is the reason, and it is simpler than the documentation makes it sound.
The rule in one sentence
When a customer messages you, a 24-hour window opens. Inside it, you can send whatever you like. Outside it, you can only send a template Meta has already approved.
That is the whole rule. Everything else is consequence.
Why Meta does this
The window is what keeps WhatsApp from becoming SMS in the 2000s. A business cannot message you out of nowhere unless the message is in a format a human at Meta has reviewed. Irritating when you are on the receiving end of the restriction; the reason the channel still gets opened when you are on the sending end.
What resets it
Only an inbound message from the customer. Every time they write, the clock restarts from that moment. Your own replies do nothing to it, so you cannot keep a window open by talking.
This catches teams out: a conversation that feels active can be closed. If the customer last wrote at 9am Monday and your colleague has been replying all day, the window still shuts at 9am Tuesday.
The three situations that actually come up
The customer replies three days later
Common, and fine. Their message opens a fresh window and you answer normally. Nothing was lost.
You need to follow up and the window has closed
Send an approved template. This is what templates are for. The useful ones are utility templates, because they are cheaper than marketing templates and they get approved more easily.
Your agent types a reply and it fails
That is a tooling problem, not a Meta problem. The window state should be visible on the conversation before anyone starts typing. In TicAte the countdown sits on the thread and the template picker appears the moment it closes.
What about chatbots and AI?
Same rule, no exceptions. A chatbot replying inside an open window is ordinary. A bot starting a conversation out of nowhere is not possible without a template. Any vendor implying their automation gets around this is describing something that will get your number restricted.
The practical setup
- Get three or four utility templates approved before you need them. Approval takes time you will not have in the moment.
- Make the window visible to agents, not something they discover by failing.
- Treat the window as a response-time target. A team that answers inside it never thinks about templates at all.
If you are still setting up, how the API connection works covers the steps, and the pricing explainer covers which messages cost money.
