The 24-hour window, explained

Almost every question we get from businesses new to the WhatsApp Business Platform is really the same question wearing different clothes. Why can't I just message this customer back? Why did my message need approval? Why does the app say the conversation expired?

The answer is one rule, and it is worth understanding properly, because it shapes how you staff your inbox and how you write your automation.

The rule

The customer service window opens when a person messages you. From that moment you have 24 hours in which you can send them essentially anything: text, images, audio, video, documents, interactive buttons, lists, locations. None of it needs pre-approval. You are simply having a conversation.

If they message you again before the window expires, the timer resets to a fresh 24 hours. An active back-and-forth conversation therefore never runs out — the window only matters once the customer goes quiet.

When the window closes, the rules change completely. You can no longer send free-form messages. To reach that customer again, you must send a pre-approved message template.

Why it exists

It is easy to read this as an obstacle. It is more useful to read it as the thing that keeps the channel worth using.

WhatsApp is where people talk to their family. The reason a message from a business still gets opened there — while email goes unread and SMS gets ignored — is that businesses cannot message people at will. The window is the mechanism enforcing that. A customer's own message is what grants you access, and their silence is what takes it away.

Every business on the platform gets the benefit of that trust. The window is the price.

What this means in practice

Speed genuinely matters. Not because a customer will be annoyed by a slow reply, though they might be, but because a reply sent 25 hours later is mechanically a different and more constrained thing than one sent 25 minutes later. Response time is not just a service metric here; it decides which tools you have available.

Your automation should be doing the overnight shift. Where a bot answers immediately, the window is open and stays useful. Where every message waits for someone to arrive in the morning, you will spend template sends on conversations that free-form replies could have handled.

Handoffs are where windows get lost. A customer messages, a bot answers, the conversation is escalated to a human, and it sits in a queue. The clock is running the whole time. Anything that routes a conversation to a person who is not there is quietly spending your window.

Templates are not a workaround

Templates exist for business-initiated messages — an order update, a delivery notification, an appointment reminder, a one-time passcode. Meta reviews them before use and sorts them into three categories: marketing, utility and authentication.

They are not a way around the window; they are a different, deliberately narrower channel with its own rules and its own cost. A template that reopens the conversation gives you a new window once the customer replies, which is exactly the intended shape: templates start conversations, free-form messages continue them.

How MapleChat handles it

Every conversation in the inbox shows its window state, so nobody has to work it out from timestamps. When the window has closed, the composer says so and points to templates rather than letting someone type a message that would silently fail.

Sending a template is also the one action that implicitly takes a conversation away from the bot. It is the only message a human can send before explicitly stepping in — because sending one means you are re-opening a conversation deliberately, and automation should not then talk over you.

Window behaviour and template categories verified against Meta's Cloud API documentation on 17 August 2026. Meta changes platform rules from time to time; their documentation is always the authority.