WhatsApp Business API for Support: What It Can and Can't Do
The 24-hour service window, template approval, per-conversation pricing and what WhatsApp simply will not let you do — before you rebuild support around it.
Three different WhatsApp products
Confusion usually starts here. The consumer app has no automation. The WhatsApp Business app is a free single-device tool for small businesses with quick replies and labels but no real integration. The WhatsApp Business Platform — the API — is the only option for multi-agent support, CRM integration and automation.
The API has no interface of its own. You either build one or use a provider's inbox, and you route through Meta Cloud API or a business solution provider.
What it does genuinely well
For support at volume in markets where WhatsApp is the default channel — the Gulf, Pakistan, much of Europe and Latin America — it outperforms email on response and resolution rates.
- Many agents on one business number, with routing, queues and assignment
- Full conversation history synced into your CRM against the customer record
- Rich messages: interactive buttons, list pickers, documents, images, location
- Proactive notifications — order, shipping, appointment, payment and renewal updates
- Chatbot or AI triage on the front line, with clean handover to a human
- Verified business profile with a display name and the green tick once approved
The 24-hour service window
This single rule shapes every design. Once a customer messages you, you can reply freely with any content for 24 hours. After that window closes, you cannot send free-form messages — only pre-approved template messages.
Practically: overnight follow-ups, day-three check-ins and reactivation nudges all have to be templates. Build your support flows around the window rather than discovering it after launch.
Templates, opt-in and quality limits
Any business-initiated message needs an approved template with fixed structure and variable placeholders. Approval typically takes minutes to a day, and marketing-flavoured wording gets rejected more often than transactional wording.
- Documented opt-in is required before you message anyone — keep the timestamp and source
- Messaging limits start low and scale with quality and volume history
- A quality rating driven by blocks and reports; poor ratings throttle or restrict your number
- Marketing template pacing limits per user, independent of your own send schedule
- One number cannot be used in the Business app and the API simultaneously
What it cannot do
Set expectations with stakeholders on these before committing:
- No cold outreach — every conversation needs prior opt-in
- No free-form messaging outside the 24-hour window
- No group messaging or broadcast-list behaviour through the API
- No editing or unsending a delivered message
- No reading a customer's history from before they contacted you
- Per-conversation pricing that varies by country and category, so volume has a real cost
Designing support around it properly
Treat WhatsApp as one channel in a unified inbox, not a parallel support system. Identity matching matters most: a customer who phones, emails and messages must resolve to one record, or agents answer blind and your metrics lie.
Then automate the top intents — order status, booking confirmation, document upload, payment link — and route everything else to a human within a stated SLA. Measure first-response time, resolution rate, deflection and cost per conversation so the channel is accountable like any other.
Where EzTechify fits
We implement WhatsApp Business API alongside voice, email and web chat as a single contact-centre stack wired into your CRM — including template libraries, AI triage, escalation rules and reporting — for teams in Saudi Arabia, the UAE, Pakistan, the UK and Europe.