The WhatsApp 24 hour window is a core rule of the WhatsApp Business Platform that dictates how and when you can reply to customers. It is a mechanism that keeps conversations user-initiated by dictating when a business must use a pre-approved message template. Understanding this rule is essential for building compliant and effective customer support workflows.

Key takeaways

  • The 24-hour window is a customer service period that begins when a user sends a message, not when the business replies.
  • Each new message from the user resets the 24-hour timer from that message's delivery time.
  • Inside the window, you can send free-form "session messages." Outside the window, you must use pre-approved "template messages."
  • This rule is fundamental to the WhatsApp Business API Explained: A Complete Guide and directly impacts your messaging capabilities, automation, and billing.
  • Automation is allowed within the window, but Meta's policy requires a clear and direct path for users to escalate to a human agent (Source).

What is the WhatsApp 24-Hour Window?

The WhatsApp 24-hour window is a time limit for responding to customers with free-form messages. Officially called the "customer service window," it starts whenever a user sends you a message. This action opens a 24-hour period during which your business can send conversational replies without needing special approval. Its main purpose is to manage when businesses can send free-form messages, determining whether a free-form reply is permitted or a pre-approved message template is required.

This window is the mechanism that determines which type of message you are allowed to send.

  • Window Open: You can send "session messages." These are non-template messages that can include ordinary text and, subject to applicable product rules, media such as images and documents. They don't need to be approved by Meta beforehand.
  • Window Closed: You must use "template messages." These are structured messages that you create and submit to Meta for approval before you can send them.

This rule is a central pillar of the WhatsApp Business Platform, designed to keep the user in control of the conversation.

How It Works: A Step-by-Step Timeline

The countdown starts from the timestamp of the last inbound user message. It is not affected by your replies. Each new message from the user discards the old timer and starts a new 24-hour countdown.

Here is an illustrative example of the whatsapp 24 hour window in action.

  • Step 1: Window Opens (Monday, 2:10 PM) A customer sends a message: "Hi, where is my order #123?" A 24-hour window opens immediately. It will expire on Tuesday at 2:10 PM.

  • Step 2: Business Replies (Monday, 2:15 PM) Your support agent or chatbot sends a free-form session message: "Thanks for reaching out! Let me check on that for you." This reply does not affect the timer. The window still expires on Tuesday at 2:10 PM.

  • Step 3: Window Resets (Monday, 4:30 PM) The customer sends another message: "Okay, thanks!" The previous timer is discarded. A new 24-hour window begins, timed from this new message. The window now expires on Tuesday at 4:30 PM.

  • Step 4: Window Expires (Tuesday, 4:30 PM) More than 24 hours pass without a new message from the customer. The customer service window is now closed.

  • Step 5: Re-engaging with a Template Message (Wednesday, 10:00 AM) Your system now has an update on the order. You cannot send a free-form message like "Good news, your order has shipped!" The platform requires a template for messages sent outside the window. Instead, you must use a pre-approved template message, such as: "Hi {{1}}, we have an update on your order {{2}}. It has now been shipped. You can track it here: {{3}}."

Session Messages vs. Template Messages: What Can You Send?

The state of the 24-hour window directly controls whether you can use a conversational session message or must use a structured template message. Sending a free-form reply is an option during the open window; using a template message is a requirement outside of it (Source).

A session message is any message that is not a template message.

Here is a direct comparison:

Attribute Session Message (Window Open) Template Message (Window Closed)
When to Use Responding to a user within 24 hours of their last message. Initiating a conversation or replying more than 24 hours after the last user message.
Content Free-form and conversational. Can include ordinary text and, subject to product rules, some media types. Structured and must adhere to a pre-approved format. Can include variables.
Approval Not required. You can type and send freely. Must be submitted to Meta for review and approval before use.
User Opt-In Not required for the reply itself, as the user initiated the conversation. Required. You must have prior consent from the user to send proactive messages.
Purpose Primarily for customer support and resolving inquiries. Primarily for transactional updates (utility), authentication, or marketing.

How Does the 24-Hour Window Affect Billing?

The 24-hour window is directly tied to Meta's conversation-based pricing model. A "conversation" is a 24-hour session of messaging. The type of conversation, and whether it's billable, often depends on who started it and the type of message used.

Replies sent within the customer service window are categorized as service conversations. According to Meta's current billing documentation, service conversations do not incur charges under its listed rules (Source). This structure incentivizes businesses to provide fast, responsive support.

In contrast, when you send a template message to a user outside the 24-hour window, you initiate a business-initiated conversation. These conversations are billable and are categorized based on the template's content (e.g., utility, authentication, or marketing).

It is important to always check the official Meta billing documentation for the most current rates and policies, as these can change.

What are the most common mistakes?

Developers and support teams often make a few common mistakes when implementing workflows around the 24-hour window. Avoiding them is key to building a reliable and compliant messaging system.

  • Mistake 1: Misunderstanding the Timer's Start Time. Many assume the 24-hour clock starts from the business's reply. The timer always starts from the timestamp of the user's inbound message.
  • Mistake 2: Forgetting That the Timer Resets. A system that only tracks the first user message will incorrectly close the window. Your logic must update the window's expiry time with every new message received from the user.
  • Mistake 3: No Escalation Path for Automation. Using a chatbot within the window is allowed, but you must provide a clear and prompt way for users to reach a human agent or another support channel (Source). Hiding this option violates policy. A proper WhatsApp AI chatbot architecture should account for this.
  • Mistake 4: Sending Proactive Templates Without Opt-In. The 24-hour window applies to customer service replies. For proactive business-initiated messages sent with a template, you must have separately collected user opt-in consent (Source).
  • Mistake 5: Confusing the Business App with the API. The free WhatsApp Business App and the WhatsApp Business Platform (API) are different products. The 24-hour rule is a technical constraint enforced by the API.

Troubleshooting: 'Message failed to send'

A "Message failed to send" error when attempting a free-form reply almost always relates to the 24-hour window. If your messages suddenly start failing for a specific user, follow this diagnostic checklist.

  1. Check the Last User Message Timestamp. This is the number one cause. Has it been more than 24 hours since the user last sent you a message? Check the exact timestamp, accounting for time zones. If it has, your free-form message will be rejected by the API.
  2. Verify Your Message Type. Confirm that you are trying to send a free-form session message and not an incorrectly formatted template message. If the window is closed, you must use an approved template.
  3. Check API Error Codes. The API response for a failed message will contain an error code and message. A common error indicates that the 24-hour service window has expired, confirming the cause.
  4. Confirm the User Hasn't Blocked You. If template messages also fail, the user may have blocked your business number. There is no way to override this.
  5. Review WhatsApp Business Policies. Ensure your message content does not violate any policies, even if the window is open (Source). The window does not grant permission to send prohibited content.

If the window has closed, the only solution is to reply using a pre-approved Message Template.

What to learn next

Sources and further reading