WhatsApp’s 24-hour window: what it is and how not to lose customers
What the WhatsApp Business API 24-hour window is, what you can write inside and outside it, and how to use templates and AI so leads do not go cold.
The WhatsApp 24-hour window is the API rule: when a customer writes to you, you have one day to reply in free text. If that time passes and you want to speak, you need an approved template.
It is not a software quirk. It is Meta’s policy so companies do not chase people at any hour with open messages. Understanding it avoids the “it won’t let me send” at 18:00 on a lead who wrote yesterday.
How it opens and closes
- The customer writes to you (or taps a CTA that generates a message). The clock starts.
- You reply as many times as you want inside those 24 hours.
- If the customer writes again, the clock resets.
- If they do not write and 24 hours pass, the service session ends. Templates only.
The window is not “24 hours from when I sent the campaign”. The campaign (a marketing template) opens a paid conversation and, if the customer replies, then service mode starts.
More channel context in what WhatsApp Business API is.
What you can send in each state
| State | Free text | Images / PDFs | Template | Notes |
|---|---|---|---|---|
| Customer wrote < 24 h | Yes | Yes | Not needed | Service mode |
| You sent a template, they have not replied | No | No | Yes (another) | Do not poke every 10 min |
| > 24 h with no message from them | No | No | Yes | Re-engagement or utility |
AI agents follow the same rules. A bot that “continues the conversation” three days later without a template is not clever: it is breaking the API.
Why leads go “cold”
Typical case: the lead writes Friday at 21:00. Nobody replies. Monday at 10:00 the salesperson opens the chat and cannot send “still there?”. The window died on Saturday.
Fixes:
- AI or on-call Friday night (first response in seconds).
- Follow-up template for Monday: “Hi {{1}}, on Friday you asked about {{2}}. Shall I pick it up?”.
- Do not leave the inbox on a phone that is off. Shared inbox.
The cost of not having a re-engagement template is, literally, not being able to talk.
Utility vs marketing when you reopen
If you reopen to confirm an appointment they asked for, aim at utility. If you reopen for an offer, it is marketing: more expensive and more sensitive to blocks.
Do not dress the promo up as an “important notice”. Meta reads the body. So does the customer.
Window and campaigns
A WhatsApp Marketing campaign uses a template. Anyone who replies enters 24 hours. There your team (or the AI) must be awake. Sending 3,000 messages at 19:00 on a Friday with no coverage is giving away reads and losing the session by morning.
Design it backwards: coverage first, then the send.
Operating practices that work
- Show in the panel how much window is left (ManyContacts treats this as part of the inbox).
- A “closing in 2 hours” queue for one last free-text touch.
- A library of 3 re-engagement templates, not improvising on Monday.
- Ban copying the chat to a personal WhatsApp “because it sends from there”. That is the silo again.
How this relates to Meta’s price
Inside the window, service replies usually sit on the conversation already open (exact billing rules you see at the partner; they change by category and country). Outside, each template can open another paid conversation. Re-engaging a silent contact 8 times is expensive and ugly.
Once or twice. Then tag and stop.
Edge cases that confuse the team
The customer reacts with an emoji. Depending on the reaction type, it sometimes does not reopen the window. Do not assume it: if you cannot write, use a template.
A WhatsApp voice call. That is not a text session message. The salesperson thinks they “spoke” and the panel is still closed.
The customer writes on Instagram and you reply on WhatsApp. They are different windows. Unify in the inbox, but do not assume one session.
Groups. The business API is not a family group. Do not design the process as if it were the app.
How to explain it to the team in a minute
“If the customer wrote today, talk normally. If their last message is from yesterday or earlier, do not invent: use the follow-up template. If there is no template, there is no message. Do not copy the chat to a personal phone.”
That sentence saves more support tickets than any wiki.
Next step
Review last week’s chats that stayed on read and no longer let you write. That is your template backlog. Create the account or book a demo and we have re-engagement ready before next Friday.