Most teams move through the same WhatsApp evolution: personal number, then Business App, then Cloud API. Many stall in the middle. Usually because they have not nailed down three things: when the upgrade becomes mandatory, how to protect quality rating after it, and how the 24-hour window and template approvals actually behave.
When the Business App is still fine
Under ~30 conversations a day, a team of 1-2, and no outbound broadcast needs — the Business App covers it. Free, with auto-replies, labels, and a product catalog. Plenty to run a small store.
The real wall: the Business App binds one phone number to one active device. Two agents cannot both be in the inbox at once. The web companion helps, but you are still single-number-single-device.
When Cloud API becomes mandatory
Any one of these three signals means it is time:
- Concurrent agents. Two or more humans need to work the same number.
- Reach outside the session window. If no inbound for 24 hours, the Business App cannot initiate. Only Cloud API can re-open a conversation via templates.
- More than ~50 daily conversations. Manual tagging and assignment start dropping tickets.
Cloud API is Meta's own. No hosting overhead, per-conversation billing (the new per-message model finished rolling out in 2026), and usually cheaper than going through a third-party BSP.
Quality rating, and why it can quietly wreck you
Meta scores every business number: Green, Yellow, Red. Blocks, user reports, and slow response rates drag the score down. At Red, templates barely deliver and your messaging limits get cut.
Three rules to keep rating healthy:
- Do not blast templates at people who have not engaged with you. Cold outbound is the fastest way to kill a number.
- Keep template copy out of aggressive marketing territory. "Last 3 hours! Buy now!" patterns get flagged by Meta's classifier.
- Reply inside the 24-hour window. Ignoring inbound erodes the score over time.
How the 24-hour window actually works
The moment a user messages you, you have 24 hours to send anything back freely — marketing, attachments, whatever. After 24 hours, only pre-approved template messages are allowed. If the user sends another message, the window resets from that point.
What this means in practice: customer asks at 11pm, you reply at 10am the next day — fine. Reply the day after that — you are in template territory, and template messages feel different to the receiver. Conversion drops noticeably.
The truth about template approval
Templates come in three categories: Marketing, Utility, Authentication. Review time ranges from one minute to 48 hours. The three most common rejection reasons:
- Variables with no clear use-case justification in the submission.
- Marketing tone submitted under a Utility category.
- Copy that nudges the user to click or reply in a manipulative way.
Practical tip: submit two or three variants at once. One usually clears. Do not wait until the morning of a campaign.
The one-sentence version
Cloud API is not a fancier personal number — it is a different operating model. Before you upgrade, understand quality rating, the 24-hour window, and template review. Those three things matter more than which BSP you pick.