The WhatsApp 24-hour window, explained properly

Almost every surprising thing about business messaging on Meta's platforms comes back to one rule, and the rule is usually explained badly. The conversation window is not a session, it is not a conversation length, and it does not start when you decide to talk to someone.

It runs for 24 hours from the customer's most recent message to you. That is the whole definition, and every consequence below follows from it.

What the clock is actually attached to

The window belongs to a pair: one customer, one business phone number. Each time that customer sends you a message, the clock resets to a fresh 24 hours. Nothing you do resets it.

This is where most of the confusion lives, so it is worth stating the failure cases directly.

• Your reply does not reset the window. If a customer wrote at 9am and you answer at 5pm, the window still closes at 9am the next day, not 5pm.
• Sending a template does not open a window. A template reaches someone whose window is closed, which is the point of templates. It does not entitle you to a free-form conversation afterwards. If they reply to it, their reply opens a window, and then you can write freely.
• The window is per number. A customer who has a window open with your support number does not have one open with your sales number.
• It is 24 hours, not one business day. A message that arrives at 4pm on Friday is unanswerable free-form by Monday morning.

What you can send inside the window

Anything. Text, images, documents, voice notes, buttons, lists. Whatever you type, in your own words, with no approval step. These are service messages, the ordinary case of a customer asking something and a business answering, and Meta does not bill them at template rates.

This is the cheapest and least restricted state your account will ever be in, which is a good argument for building your messaging around customers starting conversations rather than around you starting them.

What you can send once it closes

On WhatsApp, only an approved message template. Templates are formats you submit to Meta in advance, with variables you fill in at send time. They exist precisely so that a business can reach someone outside the window without the channel filling with unsolicited free text.

If you try to send free-form text anyway, the send fails. WhatsApp returns a specific error for it: code 131047, sometimes surfaced as 470, meaning the re-engagement window has elapsed. It is not a transient failure and retrying does not help. A platform that shows you "message failed" without telling you the window closed is hiding the one fact that would have told you what to do next.

Instagram and Messenger inherit the same 24-hour rule with a meaningfully worse escape hatch: they have no template mechanism for ordinary re-engagement.

• The human agent tag extends the reply window for conversations a person is actively handling. It applies to human responses rather than automated sending, and it has to be approved by Meta for the application in question.
• Message tags let a Messenger message go out for a specific permitted reason. Meta has retired most of the tags that once allowed re-engagement, so any guide describing a generous set of tags is describing an older platform.

The practical summary for those two channels: if the window closed and nobody is actively handling the thread, you usually cannot reach the person at all. Plan for that rather than discovering it.

Why the rule exists

It is easy to read the window as an obstacle. It is more useful to read it as the thing that makes the channel worth being on.

WhatsApp is where people talk to their families. The reason a message from a business gets opened within minutes is that the inbox has not been filled with messages nobody asked for. The window, the template review process, and the quality rating are the three mechanisms holding that property in place. A vendor promising to work around any of them is promising to spend your account's credibility.

What this means for how you staff and answer

The window turns response time from a service metric into a hard constraint, and there are only a few honest responses to that.

Know where the clock is on every open thread. The inbox should show it. Not as a colour, as a number: this thread has four hours left, that one closed yesterday. A team that cannot see the clock discovers it at send time.

Answer inside the window even when the answer is partial. "We are checking with the warehouse and will confirm today" is a real reply, it resets nothing, but it does keep the thread alive because the customer will often respond. A silent thread that closes turns your next message into a template.

Automate the routine answers. Most inbound messages are the same ten questions. Answering those automatically, from your own material, is what keeps human attention available for the threads that need it. That is a service quality argument before it is a cost argument.

Decide in advance what happens after hours. Someone messaging at 11pm will not be answered by a person. They can be answered by a grounded automated reply, or they can be told plainly when a person will pick it up. Both are better than a thread that goes quiet and reopens as a template two days later.

Reading the window off delivery receipts

Meta reports every outbound message's fate through delivery statuses: sent, delivered, read, or failed with a code. Failures are where the window becomes visible.

Three codes are worth recognising on sight, because they mean completely different things and get lumped together by weaker tooling:

Only the middle one is worth retrying. Retrying the first burns nothing but time; retrying the third is exactly the behaviour that damages a sender's reputation. Software that treats all three as "failed, retry" is making your account worse on your behalf.

The parts people get wrong most often

"We can extend the window by messaging them first." No. Only their message moves the clock.

"Templates are for marketing." Templates are for anything sent outside the window, including an order update. Their category decides what they may contain and what they cost, not whether you are allowed to use one.

"We will just use a chatbot to keep the thread alive." Automated messages you send do not reset the window either. Only inbound does.

"The customer replied to our template, so we are fine now." True, and this is the one that works. A reply opens a fresh 24 hours, and everything you send in that period is free-form and cheap. It is the reason a template with a genuine reason to reply is worth more than one with a good offer.

The short version

The window opens when the customer writes and closes 24 hours later. Inside it you may say anything. Outside it, WhatsApp allows an approved template and the other Meta channels allow very little. Nothing you send changes the clock.

Design around that and the platform is straightforward. Design against it and you will spend your budget on templates, and your account's standing along with it.