WhatsApp's 24-hour window is the period, defined by Meta's policies for the WhatsApp Business API (WhatsApp Business Platform), during which a business can freely reply to a customer —text, images, documents, buttons— after that customer last wrote in. Once 24 hours pass without the customer writing again, the conversation closes for session messages and can only be reopened with a message template approved by Meta. Understanding it well prevents lost sales and support tickets from not being able to reply in time, and it's the reason automation and a platform like LiveConnect, a Meta Business Partner, make such a difference in day-to-day operations.
What the 24-hour service window is
When a customer writes to your WhatsApp number for the first time, or writes again after a period without contact, a 24-hour service window opens. Within that period, the business can send any type of session message without needing prior approval from Meta: answer a question, send a catalog, confirm an order, or resolve a support case. It's the logic of a normal messaging conversation.
The count runs from the customer's last inbound message, not from the first one. Every new message the customer sends resets the clock to 24 more hours. As long as the conversation stays "alive" on their side, the business keeps the window open and can keep replying with free formatting.
What resets it and what closes it
The window resets only when the customer writes: a text message, a voice note, a reaction, or even tapping a button on a template all count as interaction and open a fresh 24 hours. What the business sends within the window doesn't extend it — if the customer doesn't reply, the countdown keeps running from their last message.
If 24 hours pass without the customer writing, the window closes. From that point on, the business can no longer send free-form session messages; to write to that customer again it needs to use a message template previously approved by Meta. The customer, on the other hand, can write whenever they want and reopen the conversation without restrictions.
Session messages vs. message templates
| Aspect | Inside the window (session message) | Outside the window (template) |
|---|---|---|
| Who can start it | The business, replying to the customer | The business, at any time |
| Prior approval from Meta | Not required | Yes, the template must be approved |
| Format | Free text, images, documents, buttons | Fixed structure with defined variables |
| Cost | Part of the open service conversation | Billed according to the template category |
| Typical use | Answering questions, follow-up, closing a sale | Reminders, re-engagement, notifications, marketing |
Neither replaces the other: session messages sustain the ongoing conversation; templates are the only authorized way to write again once the customer hasn't replied within 24 hours. If you want to understand how each conversation type is billed, this WhatsApp API pricing guide explains it in detail.
What happens if you let the window close without replying
The most common risk isn't technical, it's operational: a customer writes after hours or on a weekend, no one on the team sees it in time, and the 24 hours run out before anyone drafts a reply. At that point the free-form message is no longer possible; you either wait for the customer to write again or send an approved template, which adds friction and, in some cases, a cost tied to that template.
For a business selling or supporting customers over WhatsApp, that friction turns into tickets that drag on, leads that go cold, and customers who feel like "no one answers." When each salesperson also handles chats from their own phone, the problem gets worse because no one has visibility into how long each conversation has been open.
Common mistakes that close the window too early
- Not distributing the load across agents: if a single number receives dozens of conversations and only one person replies, several windows can easily expire without anyone noticing.
- Not having expiration alerts: without an indicator of how much time is left, the team finds out the window closed only after trying to reply and having the message fail.
- Misunderstanding what resets the window: a message from the business doesn't reset the countdown; only an inbound message from the customer does. Assuming otherwise leaves "expired" conversations that no one notices.
- Not having reactivation templates ready: if the only approved template is too generic or doesn't fit the case, reopening the conversation takes longer than necessary while a new approval is requested from Meta.
- Covering support hours only during office hours: customers who write at night or on weekends can go unanswered within the window if there's no chatbot covering those hours.
How to avoid losing the ability to reply
AI chatbots as the first response
A chatbot connected to the WhatsApp Business API can reply instantly as soon as the customer writes —24/7, without depending on an agent being available— keeping the window open while human support is scheduled or the question is resolved automatically. It's the simplest defense against windows closing due to a slow first reply.
Alerts and visibility into remaining time
A support platform can show each agent how much window time is left on every open conversation, and prioritize the ones about to expire. That way the team doesn't discover the window closed after already trying to reply — it acts beforehand.
Message templates ready for reactivation
Having templates approved in advance —a follow-up reminder, order confirmation, an invitation to pick the conversation back up— lets you reopen any expired case without depending on an urgent approval from Meta. This is especially useful for re-engagement and remarketing campaigns.
Routing and multi-agent support
When several agents handle the same number with multi-agent support, automatic assignment distributes the load and keeps conversations from piling up unowned until the window expires.
Benefits of managing the 24-hour window with LiveConnect
LiveConnect combines activating the WhatsApp Business API with the tools needed so the service window stops being an operational risk:
- AI chatbots that cover the first reply after hours and during demand spikes, handing off to a human agent when the conversation calls for it (more detail in this guide on bots vs. human agents).
- WhatsApp CRM with per-contact history, so any agent immediately sees when the customer last wrote and how much window time is left.
- Campaigns with approved templates to reactivate closed conversations in an orderly way, with segmentation and metrics, without risking the number through improvised bulk sends.
- Omnichannel support: the same service-window logic also applies on Instagram and Messenger; LiveConnect centralizes support across all channels in a single inbox.
LiveConnect plans start at USD $89/month — compare them in the pricing section on this same page. Template and conversation costs are billed by Meta according to category and volume, and may vary by case.
How to get started
- Diagnosis: we review how many conversations your team handles today and how often replies get lost due to missed 24-hour windows.
- Activation and setup: LiveConnect activates or migrates your number to the Official API and configures chatbots, expiration alerts, and reactivation templates around your operation.
- Team rollout: your team starts handling conversations with full visibility into remaining window time, without depending on anyone's memory.
Are conversations expiring without you noticing? Message us on WhatsApp or check the plans and pricing: a LiveConnect specialist will show you how to automate service-window management for your business.
