Why a single WhatsApp phone stops working
A WhatsApp Business App number effectively belongs to one device, so the business has one queue and one operator. When volume grows, customers wait, nobody can see who already replied, and the same question gets answered twice.
Moving to the WhatsApp Business Platform turns the number into a shared resource. Many agents can work the same number, and the platform keeps one conversation thread per customer rather than one per device.
The four decisions to make before you configure anything
- 1
Who owns an unassigned conversation?
Either a round-robin queue or a shared pool that anyone can claim. Pick one. A shared pool with no rule is how conversations get answered twice.
- 2
When does a conversation leave an agent?
Define reassignment and escalation triggers — time since last reply, topic, or an explicit request. Without a trigger, conversations stay with whoever happened to open them.
- 3
What counts as resolved?
A closed state that everyone uses. Otherwise the inbox fills with conversations nobody is sure are finished, and reporting becomes meaningless.
- 4
What is written down rather than messaged?
Internal notes. Agents need somewhere to record context that the customer must not see but the next agent must — that separation is the main operational gain of a real inbox over a phone.
Design around the 24-hour window, not against it
You can reply freely for 24 hours after the customer’s last message. After that, reaching them again requires an approved template. Inbox rules should treat the window as a deadline: any conversation approaching the end of the window should be answered while a free reply is still possible.
- Every inbound customer message restarts the 24 hours.
- Inside the window, agents can send normal replies, media and documents.
- Outside the window, only pre-approved templates can be sent — which cost money and read differently to a customer.
- Support metrics should surface conversations about to leave the window, not just unanswered ones.
This is why "reply before the window closes" belongs in the team’s process, not only in the software. The cost of missing it is a paid template that feels less like a conversation.
Where automation should sit
Automation should handle the first minute and the routing, not the whole conversation. An instant acknowledgement plus a route to the right queue removes the silence that makes customers message again on another channel.
- Acknowledge immediately so the customer knows the message arrived.
- Ask one qualifying question at most before routing.
- Hand to a human when the customer asks for one, or when confidence is low.
- Log every automated decision so a human can see what the customer was already told.
Common questions
Platform rules and pricing on this page are Meta’s and can change. Meta updates WhatsApp pricing only on the first day of a quarter and gives advance notice, but always confirm current rates against Meta’s own documentation before committing a budget. This page was reviewed on 26 September 2026.
Related reading
API vs Business App
The WhatsApp Business App is a free phone-based app for a single operator with no API, while the WhatsApp Business Platform (often called the WhatsApp Business API) is a paid, multi-agent, programmable service built for teams, automation and broadcast at scale.
Why BNex
BNex is a WhatsApp Business Platform suite that combines a shared team inbox, broadcast campaigns, workflow automation and a prepaid wallet in one product, built on Meta’s official Cloud API rather than an unofficial automation workaround.