Do I need the official WhatsApp Business API to support customers there?
Yes, if you want to handle it with a team or with an automated system. The normal app and WhatsApp Business do not allow tools to be connected in any supported way, and the workarounds that manage it risk having Meta shut the number down. The official API is contracted through an authorised provider, who handles the verification.
Short answer
Yes, if you want to handle it with a team or with an automated system. The normal app and WhatsApp Business do not allow tools to be connected in any supported way, and the workarounds that manage it risk having Meta shut the number down. The official API is contracted through an authorised provider, who handles the verification.
In detail
What it involves in practice
Verifying the business with Meta, having a number not already tied to a normal WhatsApp account, and accepting two rules that shape how support works: the twenty-four-hour window for replying freely, and approved templates for writing outside it.
The twenty-four-hour window
It is the rule that surprises people most. Within twenty-four hours of the customer last message you can reply normally; outside it, only with a pre-approved template. That changes how support is designed: a case taking two days to resolve needs a template for the final update.
How long it takes
Verification depends on Meta rather than the provider. With the company paperwork in order it usually resolves in days; with anything incomplete it can stretch considerably, and it is the part of the calendar nobody controls.
If the number is already in the app
It has to be migrated, and during migration that number stops working in the app. It is worth planning outside working hours and warning the team, because it is a real interruption even if a short one.
Terms that come up here
Other questions in this thread
How long does it take to get an AI support agent running?
Answering from your documentation is a matter of hours, not weeks: what you already publish gets indexed and it starts replying. What takes time is the other half — connecting the reads against your API so it can check the account of whoever is asking — and that depends on your product team, not the vendor. One to two weeks is an honest estimate for having both.
What counts as a conversation when you pay per resolution?
A conversation is a whole thread with one customer, not each message: if they write five times about the same thing, it is still one. What varies between vendors is when that thread gets cut and what counts as resolved, and those two definitions decide your invoice far more than the unit price on the website.
What happens if I go over my plan conversation limit?
It depends on a decision the vendor makes and that is worth knowing before signing: either the agent stops answering, or it keeps answering and the excess gets billed. The first turns a volume spike into a customer service problem; the second, into an unexpected invoice. Neither is bad, but knowing which applies to you changes which plan you buy.
Where this question comes from
Messages in Intake →