WhatsApp Business in 3CX: centralise customer requests in the phone system

In Morocco, a customer would rather write on WhatsApp than call or email. The problem for a company: those conversations live on the personal phone of a salesperson or technician, with no shared history, no follow-up, and they leave with that person when they change jobs. The short answer: connect the company’s WhatsApp Business number to your 3CX phone system. Each message then becomes an interaction handled like a call, in a queue, with a shared history, statistics and transfer between colleagues. Here is how it works, what to prepare and the mistakes to avoid.

What the integration does

The company’s WhatsApp number is connected to 3CX through WhatsApp Business Platform, Meta’s programming interface for businesses. Each incoming message lands in a queue, like a call, and is distributed to available agents according to the PBX rules: first free, round robin, skills. The agent replies from the 3CX app, on desktop or mobile, without using their personal WhatsApp.

Concretely:

• One number for the company, on a landline or mobile, independent of staff phones.
• Shared history: the whole team sees the conversation, a colleague picks up a case without making the customer repeat.
• Assignment and transfer between agents or departments, as for a call.
• Statistics: first-response time, conversations handled per agent, peak hours, in 3CX reports.
• Customer record: with CRM integration, Odoo, HubSpot or Microsoft 365, the record opens when the message arrives.
• One tool for calls, website chat and WhatsApp: agents no longer juggle three applications.

WhatsApp on a phone or WhatsApp in the phone system

Criterion	WhatsApp on an employee’s phone	WhatsApp Business integrated with 3CX
Number ownership	Tied to a person and a device	Company number, independent of devices
History	On one phone, lost when the employee leaves	Shared, visible to the authorised team
Distribution	Whoever has the phone answers, or nobody	Queue, business hours, overflow
Tracking	No indicators	Response times, volumes, waiting conversations
Confidentiality	Customer data on a personal device	Account-based access, removed instantly when an agent leaves
CRM link	Manual copy and paste	Customer record opened, conversation attached

The confidentiality point matters more than people think. Customer exchanges, sometimes with ID documents, invoices or photos, sit on a personal phone with no control at all. For a company subject to Morocco’s personal data protection law 09-08, centralising these conversations in a managed tool is common sense.

What to know before starting

• The number must be registered on WhatsApp Business Platform, through a verified Meta Business account. A number already used on the classic WhatsApp or WhatsApp Business app must be removed from it first, and its history is not transferred.
• Meta enforces a 24-hour window: the company can reply freely within 24 hours of the customer’s last message. Beyond that, an approved message template is required.
• Billing is Meta’s, not 3CX’s. It depends on the country and the message category: service replies, utility notifications, marketing, authentication. Replies within the 24-hour window are generally not charged; templates sent on the company’s initiative are. The rate card changes, so we check it on every project.
• Contact-centre features depend on the 3CX licence edition, Pro or Enterprise in most cases.
• Meta regulates usage: no bulk sending to contacts who have not opted in, or the number’s quality rating drops and the number may even be suspended.

Use cases that work

• After-sales service: photos of the fault, serial number, fast reply, ticket created in the CRM.
• Appointment booking for a clinic or practice, with template confirmation and reminder.
• B2B sales: quote requests land in a queue instead of getting lost across three phones.
• Order and delivery tracking, with utility notifications sent from the ERP.
• IT support, our own use: clients write to us on WhatsApp, the request becomes a tracked ticket.

Deployment in five steps

1. Prepare the Meta Business account: business verification, choice of number, display name compliant with Meta’s rules. This is the step whose lead time depends least on us.
2. Connect the number to 3CX and create the WhatsApp queue: agents, opening hours, overflow rules, out-of-hours message.
3. Write and submit message templates: acknowledgement, appointment confirmation, reminder, follow-up after 24 hours. Short, clear templates with no ambiguous commercial promise are approved more easily.
4. Link the CRM so the customer record opens and the conversation is attached to the right contact.
5. Train agents and set up reports: waiting conversations, first-response time, volumes per day and per agent.

For companies that do not yet have 3CX, WhatsApp is often the argument that tips the telephony project, as we explain in 3CX: why this phone system wins. If you are still weighing options, our comparison 3CX, Yeastar or Teams Phone helps you decide.

Common mistakes

1. Keeping the WhatsApp Business app on a phone in parallel: a number cannot be on both the app and the platform. You have to choose, and tell customers if the number changes.
2. Forgetting the 24-hour window: an agent who wants to follow up the next day finds they cannot write freely. Follow-up templates must be ready from day one.
3. Defining no business hours: a message received in the evening goes unanswered until the next day, without the customer knowing. An automatic out-of-hours message saying when they will be contacted avoids frustration.
4. Putting everyone in the queue: without skill rules, technical requests land with sales, and vice versa.
5. Sending promotional campaigns without consent: the number’s quality rating drops and Meta can restrict sending.
6. Never looking at the reports: first-response time is the indicator customers feel most, provided you track it.

Checklist before launching the project

• Meta Business account created in the company’s name, with at least two internal administrators.
• Number chosen, dedicated, removed from any existing WhatsApp app.
• 3CX licence edition checked for the queues and reports you need.
• List of agents, their skills and the queue’s hours.
• Templates written: acknowledgement, out of hours, confirmation, follow-up.
• CRM integration identified, with the field used to recognise the customer.
• Written internal rule: no customer request handled from a personal WhatsApp any more.
• Indicators reviewed every week, with a named owner.

How we do it

We start with a free audit of your telephony and current contact channels: who answers today, on which devices, with what follow-up. We then prepare the Meta Business account with you, connect the number to 3CX, write the message templates and link your CRM. The phone system and its queues are then covered by our 24/7 monitoring, with critical incidents handled in under 15 minutes. This integration is part of our IP telephony offer, as a 3CX partner. For the rest of the project, also read migrating to IP telephony; anonymised examples are in our case studies.

Want your WhatsApp requests to land in the same place as your calls? Request your free audit: we reply within 24 business hours.