The three problems with the usual “company” WhatsApp
- It lives on one phone. When that person is off, the conversation stops. When they leave the company, the conversation leaves with them.
- It is not on record anywhere. The case is split between email and a chat nobody else can see. “I told you and it is not on record” is literally true.
- It cannot be measured. Not response time, not volume, nothing.
The two ways to connect it
| Aspect | Official WhatsApp Business API (Meta) | Unofficial connection |
|---|---|---|
| Several agents at once | Yes | Limited |
| Templates approved by Meta | Yes | No |
| Cost | Meta’s rate per template message, by category and country | No Meta rate |
| Risk of being blocked | Low, if you follow its policy | Real |
| Setup | Business verification; it can take days | Immediate |
If you handle volume or the channel matters to your service, choose the official API. Unofficial connections work until Meta detects the pattern and blocks the number. And that number is usually the one all your customers have saved.
Meta’s rates and categories change: check the current ones before you estimate costs.
The 24-hour window
It is the rule most people do not know and the one that causes the most trouble.
- When a customer messages you, a 24-hour window opens in which you can reply freely.
- After 24 hours without another message from them, you can no longer send a free-form message. Only a template approved by Meta.
In practice: if a customer writes on Friday afternoon and you reply on Monday with a regular message, it will not be delivered. You need to reply inside the window or have templates ready.
Templates: what gets approved and what does not
Useful, specific messages get approved: appointment confirmation, technician on the way, ticket resolved or a reminder. Promotions dressed up as notifications get rejected, or classified as marketing and charged as such.
Review can take time, so prepare them before you need them. Have at least these four:
- Request received, with its reference number.
- Technician on the way, with the expected time.
- Job completed, with a link to the service report.
- Appointment reminder.
Five mistakes that end badly
- Using an employee’s personal number. When they leave, the channel leaves with them.
- Sending promotions to people who opened a support ticket. It is the fast track to being reported and blocked.
- Not stating your hours. If you answer Monday to Friday, 9 to 6, an automatic after-hours message prevents a lot of complaints.
- Settling on WhatsApp what should be in writing. A quote or a deadline commitment belongs in a document, even if the conversation happens on WhatsApp.
- Not bringing it together with everything else. WhatsApp integrated, but in a separate inbox, is just a tidier problem.
What works
- A company number, not a personal one, with several agents handling it.
- The conversation inside the ticket, next to email and calls.
- Quick replies for repetitive questions, written by the team itself.
- Proactive updates. “Your technician will arrive in 30 minutes” stops calls before they happen.
- Automated menus only to route, never to resolve. An eight-option menu is annoying; a three-option one that routes well goes unnoticed.
WhatsApp is worth setting up properly: a company number, the official API and the conversation inside your system. Anything else is the same problem in a more comfortable place.
Last updated: