The WhatsApp 24-hour messaging window, explained

If you take one thing away about the WhatsApp Business API, make it this: the 24-hour window. It governs what you can say, when, and how — and getting it wrong is the most common reason a business message silently fails to arrive.

What the window is

Every time a customer messages your business, a 24-hour customer service windowopens. Inside it, you can reply with almost anything — free-form text, images, documents — exactly like a normal chat. The clock resets each time the customer sends a new message.

When 24 hours pass with no new message from them, the window closes. Now you can no longer send free-form content. To reach that customer again, you must send a pre-approved template message.

Why WhatsApp does this

The window is Meta's spam control. It keeps WhatsApp feeling like a place for real conversations, not a broadcast channel businesses can blast at will. Customers stay in control: if they stop replying, you can only reach them through message types they've effectively pre-consented to (approved templates).

Inside vs outside the window

• Inside (open): free-form messages are allowed. Great for live support, back-and-forth, answering questions.
• Outside (closed): only approved template messages deliver. Great for notifications you initiate — reminders, updates, offers to opted-in customers.

The mistake that eats support tickets

Teams building directly against the API often send a free-form message to a customer who hasn't written in a day — and it just… doesn't arrive, sometimes without an obvious error. Multiply that across thousands of sends and you have a silent delivery hole and a lot of confused customers.

The fix is to check the window state on every single send and route accordingly: free-form if open, template if closed. Doing that reliably — tracking the last-inbound time per customer, per number — is fiddly to build yourself.

How walpio handles it for you

This is the problem walpio was built around. On every send, walpio checks the window:

• Window open → your text goes out as-is.
• Window closed → walpio automatically wraps the same text into your approved template and sends that instead.
• No approved template configured → you get an honest, explicit error, not a silent drop.

One endpoint, no window rules to remember in your own code, and the API response tells you which route was used. That's the difference between “we send WhatsApp” and “our WhatsApp actually arrives.”