The window closed. The conversation doesn’t have to.

The WhatsApp 24-hour window: who moved the clock?

Tap through this fictional kitchen-project enquiry. All times use one illustrative local clock, with no daylight-saving change. Watch what happens when the business replies—and when the customer does.

The simple calculation is: latest customer message time + 24 hours. At that expiry time, the free-form reply window is closed unless another customer message has reset it. Check the connected tool’s current sending guidance rather than guessing from yesterday’s date.

The window closed. Here’s your next sensible move.

First, check the latest inbound message. A colleague’s reply can make a thread look active even though the customer hasn’t written since Monday. Activity is not the same thing as eligibility.

If the window is closed, use an approved template appropriate to the actual reason for contact, subject to your account’s readiness and the customer’s permissions. Approval is not a guarantee of delivery.

If there isn’t a suitable template, don’t disguise a sales chase as a transaction update. Prepare the right template through your supported setup and wait for the required approval, or use another appropriate, permitted contact route.

A customer can also message you again and open a fresh window. Don’t make them perform a pointless “hi” ritual to receive information you could have prepared properly.

• Check whether the customer has asked you to stop or use another channel.
• Read the template’s actual wording, language, status and purpose before choosing it.
• Check account readiness, payment-method restrictions and any sending error.
• After sending, inspect its status. Queued, delivered, read and answered are different things.
• Give the next human action an owner. Don’t leave the enquiry parked under “template sent”.

A template can ask a question. Only their answer resets this clock.

Imagine your approved message is delivered at 10:15 on Wednesday. That outbound message alone does not start a new free-form reply period. A read receipt is not an inbound customer message either.

If the customer writes back at 11:00, count from 11:00. You can then continue the conversation within the new window, subject to the usual policy and account conditions.

Creating a new enquiry, assigning a different owner or connecting a CRM does not change Meta’s rule. Neither does sending “just checking in” often enough. Charming persistence has its limits.

Say something worth opening WhatsApp for.

The best starting point is the customer’s unfinished decision: a scope question, the detail they requested or the next step they agreed to. “Any update?” makes them do the remembering. Help them out.

These are original writing examples, not approved WhatsApp templates or a promise of a particular category. Outside the window, submit or select suitable approved wording through your provider’s supported process. Don’t paste these into a free-form composer and expect an exception.

Three separate questions: allowed, wanted and billed.

A message can use the right format and still be a bad idea. Check permission, relevance and requests to stop. A phone number captured on a form does not, by itself, settle every later WhatsApp use.

Template approval and the customer-service window do not describe the whole bill. Check current Meta charges, your provider’s charges and the software subscription separately. This guide deliberately does not turn “inside the window” into “everything is free”.

For Kibi: Meta bills you directly for WhatsApp. Kibi never charges your credits for it. If you connect through Twilio or MSG91, that provider bills you directly. Your CRM subscription is separate.

If you operate across countries, check your actual customer destinations and current provider terms. One team can have several conversations with different expiry times; there is no single daily reset for the whole business.

“It didn’t send” needs a reason, not another ten attempts.

If you use Twilio and see error 63016, its documentation identifies an out-of-window or unsupported send format. It also explains why typing template wording into an ordinary message body is not the same as sending a registered template.

Other failures need their own diagnosis. An unready number, unsuitable template status, payment restriction or customer opt-out is not fixed merely by changing the time of day.

In your connected tool, read the current error and check the provider’s documented remedy. Don’t tell the customer “sent” because you clicked a button. Keep the enquiry open for the person who will resolve it.

The little questions that cause surprisingly big confusion.

The rulebook, without the rabbit hole.

Official WhatsApp policy and Twilio documentation checked on 1 November 2026. The rule summary is for Business Platform/API messaging; account-specific sending guidance and current provider terms still apply.

The timeline, messages and team scenario are fictional teaching examples. The expandable Kibi screens are genuine captures from our isolated fictional demo, dated separately. This is a workflow guide, not a claim that we tested every provider or Meta account.

Choosing between the app and API is a different decision. Our setup comparison explains those roles; this article helps you handle the next conversation once the Platform window matters.