WhatsApp is the channel many customers prefer for talking to a company, and more and more contact centers are adding it alongside voice. But "adding WhatsApp" to an operation with dozens of agents is not installing the app on a phone. This guide sums up what you should know before you start.
WhatsApp, WhatsApp Business and the WhatsApp Business API
- WhatsApp is the personal app. It is no use to a company: one number, one phone, no shared history.
- WhatsApp Business (app) is free and aimed at small businesses: one number, a handful of devices, quick replies and a catalogue. It does not integrate with a contact center.
- WhatsApp Business API (also called the Cloud API or WhatsApp Business Platform) is Meta's official way for software such as OCM to send and receive messages on behalf of the company. It allows as many agents as you like to serve the same number, with conversations distributed by queue and skills, just like calls.
For a contact center the only serious option is the API. "Connectors" that emulate a phone running WhatsApp Web breach Meta's terms and end with the number being blocked.
Concepts that change how you work
Customer-initiated and business-initiated conversations
If the customer writes first, the company can reply freely during a 24-hour window from their last message. If the company wants to start the contact (an appointment confirmation, a delivery notice, a campaign), it has to use a template approved by Meta in advance.
Templates
These are messages with a fixed structure and variables ("Hi {{1}}, your appointment is on {{2}} at {{3}}"). They are approved within hours, classified as marketing, utility or authentication, and each category has a different price. A good CTI manages them from its own panel and puts them one click away from the agent.
Cost per conversation
Meta does not charge per message but per open conversation (24-hour window), and the price depends on the customer's country and the category. Service conversations started by the customer are treated more favourably than marketing ones. Keep that in mind when designing bulk outbound campaigns.
Number quality
Meta rates each number according to the blocks and reports it receives. A low-quality number has its daily template volume limited. The rule is simple: only write to people who have given consent, with content they expect.
What you need to get started
- A verified Meta Business account (company name, documentation and website).
- A phone number not already registered on WhatsApp, or release the one you use in the app. It can be a landline or a mobile; landlines receive the code by call.
- Software connected to the API that receives messages via webhook and distributes them among agents. In OCM the onboarding (Embedded Signup) is done from our portal, without touching Meta's developer console.
- A catalogue of templates for outbound use cases: confirmations, reminders, surveys, notices.
How it fits into the agent's queue
What matters is not receiving the message but what happens next. In a well-built contact center:
- Every inbound conversation becomes an interaction that joins the same queue as calls, with its own priority and skills.
- An agent can handle several conversations at once (usually between 3 and 5) while not on a call, and the system enforces that limit.
- The agent sees the customer's full history, whether it came through WhatsApp, phone or email.
- Each conversation is closed with an outcome, just like a call, so it shows up in reports and quality audits.
- The supervisor sees open conversations and first-response times, and can reassign.
Common mistakes
- Using the company's WhatsApp number that already lives on a mobile and losing it by migrating without a plan.
- Launching marketing campaigns to databases without explicit consent and burning the number's quality in a week.
- Treating WhatsApp as a separate channel, with another tool and another team, and losing the unified view of the customer.
- Not measuring: without dispositions and reports, WhatsApp becomes a black hole of conversations never closed.
In short
WhatsApp Business API is a powerful, cost-effective channel when it is properly integrated into the contact center: same queue, same agents, same reports. At OCM we have integrated it natively with Meta's official API, with guided onboarding, templates managed from the panel and several numbers per account. If you are considering adding it, tell us about your case.
Want to see it applied to your operation?
We will show you OCM configured with your campaigns and channels.