WhatsApp 24 hour window with coexistence: who opens it and when

The 24 hour window is the period in which your business can reply through the WhatsApp Cloud API with free-form messages, no template required. With coexistence, the rule is simple and has no loopholes: only a message from the customer opens the window, and every new message from them resets the clock. Nothing your business sends opens or extends it, whether it goes out through the API or from the WhatsApp Business app on someone's phone. Outside the window, any business-initiated API message needs an approved template. The phone, meanwhile, keeps working as it always has and does not depend on the window at all.

That is the short answer. The rest of this post is for whoever is about to wire up automations on top of the number and would rather learn the rule here than from a failed send.

The rule in three lines

1. The customer opens it. They message you, the window opens for 24 hours.
2. The customer renews it. Each new message from them restarts the clock from zero.
3. You never touch the clock. API replies, your rep's reply from the phone, voice notes, photos, templates: none of it opens or extends the window.

Most of the confusion lives in line three. It feels natural to assume a conversation is "active" while your team is still talking. For the API, an active conversation is one where the customer wrote in the last 24 hours. That is the whole definition.

What opens the window and what does not

With coexistence the same number has two sides sending messages, so it helps to go case by case.

Opens or restarts the window:

• the customer sends a first message
• the customer replies to anything, including a template you sent
• the customer sends a thumbs-up, a photo or a voice note

Does not open or restart it:

• your system sends a message through the API
• a rep replies from the WhatsApp Business app on their phone
• your system sends a template
• someone on the team forwards a file from the phone

Look closely at the template line. A template lets you reach the customer outside the window, but it does not reopen the window. Their reply to it does.

Your phone does not run on the window

This is what makes coexistence different from a pure Cloud API setup. Your team stays in the WhatsApp Business app, and the app plays by its own rules, not the API's.

In practice:

• reps can reply from the phone at any hour, inside or outside the 24 hours
• messages sent from the phone are free and never show up on your API bill
• those messages appear on both sides, but they do not count toward the window

There is an upside and a catch. The upside: human support is never held hostage by a timer. The catch: the freedom of the phone is not a license to swap broadcasts for manual mass sending. That pattern is exactly what Meta penalizes, and number quality is shared by both sides. If your team starts pasting the same message to dozens of contacts from the phone to dodge a template, the blocks and reports land on the whole number. The post on WhatsApp number quality covers what drags it down and how it recovers.

Outside the window: templates

When a customer has not written in more than 24 hours and you want to start the conversation through the API, the answer is a template: a message format Meta has approved in advance. Appointment reminders, shipping notifications, re-engaging a lead that went quiet: outside the window, all of it has to go out as a template.

Two practical points:

• Templates cost money. Meta charges per message, using a public rate card that varies by country and by template category (marketing, utility, authentication). Rates change, so pull up Meta's current rate card before you budget anything.
• Service replies inside the window are currently not charged. One more reason to answer while the customer is still there instead of circling back tomorrow with a paid template.

Categories, approval and the usual reasons Meta rejects a template are covered in WhatsApp coexistence templates.

Quick reference: what applies when

A worked example

Say an HVAC company in Texas runs coexistence. The office manager answers from her phone, and a scheduling system sends confirmations through the API.

• Monday, 9:00 AM. A homeowner asks if someone can look at their AC this week. The window opens and runs until Tuesday, 9:00 AM.
• Monday, 9:10 AM. The office manager replies from her phone with two time slots. The window does not move.
• Monday, 4:00 PM. The homeowner picks Thursday at 1:00 PM. The window restarts and now runs until Tuesday, 4:00 PM.
• Monday, 4:02 PM. The system sends a free-form booking confirmation through the API. Fine, the window is open.
• Wednesday, 1:00 PM. The system wants to send a day-before reminder through the API. The window closed Tuesday at 4:00 PM, so the reminder must be an approved template.
• Wednesday, 1:20 PM. The homeowner replies "see you tomorrow." The window reopens until Thursday, 1:20 PM, and any last-minute change can go out through the API as free-form text again.

The failure this example prevents: if Wednesday's reminder had been set up as free-form text, it would simply not have been delivered. Nobody would notice until the tech showed up to an empty house.

Not to be confused with the 24-hour sync

There are two different "24 hours" in coexistence, and mixing them up leads to bad calls. The sync happens once, when you connect the number: Meta transfers up to 6 months of history from the app, a process that takes anywhere from minutes to hours, and after that everything flows in live. The 24 hour window is a permanent sending rule for the API that applies to every conversation, every day, as long as the number stays connected. One is an installation event; the other is an operating rule. The first one is explained in the WhatsApp 24-hour sync.

The mistakes we see most

Counting a rep's reply as a renewal. The team replied from the phone at 5 PM, so the automation can send free-form text tomorrow at 4 PM, right? Wrong. The clock belongs to the customer.

Building follow-ups as free-form text. Any automation that fires after a delay (reminders, satisfaction surveys, quote follow-ups) should be built as a template from day one, because by the time it fires the window has probably closed.

Using the phone to get around templates. It works one message at a time. At volume it becomes the manual mass sending Meta penalizes, and the whole number pays for it.

Treating the window as a per-contact status. It is per conversation and per clock. A customer who bought from you last year does not have an open window just because you have talked before.

Mixing it up with the sync. Waiting 24 hours after connecting "for the window to open" makes no sense. The window does not depend on the connection; it depends on the customer writing.

Checklist before you turn on an automation

• Every automated message is labeled "inside the window" or "outside the window"
• Every message that fires after a delay is an approved template
• The team knows phone replies do not renew the API window
• Nobody uses the phone for repeated sends that should be templates
• Template costs are estimated from Meta's current rate card for your country

Where to go next

If you are not sure your number qualifies, start with what WhatsApp coexistence is and then check the module page at WhatsApp Coexistence. If you have already decided, a Vazante account starts with 7 days for US$2.99 at sign up.