WhatsApp is the highest-engagement channel most businesses will ever operate, and also the one with the strictest rules. Almost every problem teams hit in their first quarter on the platform comes down to a misunderstanding of two mechanics: when you are allowed to start a conversation, and what you are allowed to say when you do.
The 24-hour service window
When a customer messages you, a service window opens. Inside it you can reply freely with any message type. Once it closes, you can only re-open the conversation with a pre-approved template. This single rule explains most of the operational design of a WhatsApp support desk: staffing has to be dense enough to answer inside the window, and your automation needs to know which side of the window it is on before it composes a reply.
Choose the template category honestly
Templates are approved per category, and category determines both pricing and tolerance. Marketing templates are held to a much higher bar and are the first thing throttled when your quality rating drops.
- Utility: tied to a transaction the customer has already initiated, order confirmations, delivery updates, appointment reminders, payment receipts.
- Authentication: one-time passcodes and verification only. Keep these templates minimal and never add promotional copy.
- Marketing: anything promotional, including a re-engagement nudge dressed up as a service message. Attempting to route marketing through a utility template is the most common cause of category rejection and, later, of template pausing.
Why templates get rejected
Rejections are rarely arbitrary. In our experience the same five issues account for most of them: variable parameters placed next to each other with no separating text, a template whose body is entirely variables, promotional language in a utility category, missing context about who is messaging, and placeholder examples that do not resemble real data. Submit realistic sample values, reviewers judge the rendered message, not the raw string.
Protect your quality rating
Every number has a quality rating derived largely from block and report rates. It moves faster downwards than upwards. Three habits keep it healthy:
- Send utility messages only to customers with a genuine, recent transaction context.
- Make opting out one tap and honour it immediately across every template category.
- Watch per-template block rates rather than the account average, one bad template usually drags an otherwise healthy number down.
Design the fallback before you launch
Assume that at some point a template will be paused mid-campaign. Decide in advance what happens then: does the notification fall back to SMS, to email, or to nothing? Encoding that decision in your workflow means a template pause becomes a logged event rather than a silent gap in customer communication.
Operational checklist for launch week
- Register your display name and complete business verification before you build flows; approval timing is the usual schedule risk.
- Create templates in every language you support at the same time, variants get reviewed independently.
- Route inbound WhatsApp into the same queue as email and chat so agents see one customer history rather than a channel silo.
- Instrument window expiry: alert when a conversation is within two hours of closing and still unresolved.
Handled well, WhatsApp becomes the channel where response times are measured in seconds and resolution happens in a handful of messages. Handled carelessly, it becomes an expensive way to get blocked.