The WhatsApp 24-hour window, explained properly
The single rule that causes more confusion than anything else in the Cloud API — what it actually says, when the clock resets, and how to work with it rather than around it.
If you are new to the WhatsApp Business Cloud API, one rule will trip you up before any other. It is worth understanding exactly, because working around it badly is how businesses lose their quality rating — and eventually their number.
The rule
You may send a customer any message you like for 24 hours after their most recent message to you. This is the customer service window. Outside it, you may only send a pre-approved template.
Two details matter and are constantly missed. First, the clock is started by their message, not yours — replying does not extend anything. Second, every new inbound message resets the full 24 hours, so an active conversation effectively never closes.
What counts as opening the window
Any message from the customer to your business number: a text, a reply to a template, an image, a voice note, or a tap on a quick-reply button. A lead form submission does not — the person filled in a form on Facebook, they did not message you. This surprises people constantly. Your first contact with a new lead is therefore almost always a template.
Templates are not a workaround
It is tempting to treat templates as a nuisance to be routed around. Resist that. Meta scores your number on how people react to what you send, and templates that get blocked or reported drag that score down. A number rated Low gets its messaging limit cut; keep it up and the number is disabled.
Templates that survive contact with real customers tend to share three traits:
- They name the context. “You asked about the two-bedroom units on Facebook” beats “Hello from ACME.” The person filled in a form days ago and has forgotten.
- They ask one question. The goal of the template is to get a reply — the reply is what opens the window and lets you have a real conversation.
- They offer a way out. An easy opt-out reduces blocks, and blocks are what actually hurt you.
Designing around the clock
Once you see the window as a resource rather than an obstacle, the workflow becomes obvious. Send the template promptly while the person still remembers submitting the form. When they reply, you have a day of free conversation — use it to finish the job rather than letting the thread go cold and needing another template tomorrow.
If a conversation genuinely needs to span days, aim to have the customer send something before the window closes. A question they will want to answer is worth more than a follow-up they will ignore.
How we handle it
INUBIZ CRM shows the time remaining on every conversation and blocks a free-form send once the window has closed — before the request reaches Meta, so a rejected send never touches your quality rating. When the window is shut, the composer offers your approved templates instead. Your synced templates and their approval status live in Settings → Integrations; the user guide covers connecting the number.