3CX: why this phone system is winning in SMBs

In many Moroccan SMBs, the phone system is an old PABX in a cupboard: handsets are tied to the office, missed calls are followed up by nobody, and customers end up calling salespeople on their personal mobiles. The day the company opens a branch, hires field staff or moves to partial remote work, the system can no longer keep up. Replacing it is both a technical and a commercial decision: it is your customers’ front door.

As a 3CX partner, we deploy this phone system at ten-person firms as well as groups with several hundred extensions. Here, plainly, is what explains its success, what makes a project vary, and the cases where we recommend something else.

A licence that does not punish growth

Most phone systems are paid per user. 3CX is licensed by number of simultaneous calls (SC), internal and external combined, as an annual subscription per system. A 60-person company that never has more than 16 calls at once pays a 16 SC licence, however many extensions are created. For large teams with modest call volumes, the difference over three years is considerable.

How to size simultaneous calls

The right number is measured, not guessed. We start from three sources:

• Call history from the carrier or the old PABX, to spot the real peaks (often early morning or during a sales campaign).
• Internal usage: a call between two colleagues counts too, as does a conference call.
• Growth expected over the year: new hires, a new branch, a customer service launch.

Undersizing leads to rejected calls at peak times; oversizing means paying for capacity that is never used. Since the licence is reviewed every year, it is easy to adjust.

The extension follows the person

iOS, Android, Windows, Mac and browser apps give every employee their business number on every device. A salesperson answers from the car, a technician from the client site, an assistant from home, all with the same number and the same call queues.

For management, it is also a matter of control: when an employee leaves, their number and call history stay in the phone system, not on their personal phone. Customers keep calling the company, not an individual.

Business integration out of the box

3CX connects natively to Microsoft 365, Odoo, HubSpot, Zoho and most CRMs. The customer’s record opens when they call, every call is logged, and one click on a number in the CRM places the call. These are the details that save minutes every day.

Beyond voice, 3CX brings team messaging, website live chat and WhatsApp into the same interface. Customer service handles calls and messages from a single screen, with the same routing rules. We cover this in our comparison of 3CX, Yeastar and Teams Phone, useful if you are still weighing several platforms.

Hosted or on premises, your choice

3CX can be hosted by us, in your cloud, or on a small machine in your server room. We recommend hosting for almost all SMBs: no machine to maintain, high availability, managed updates.

Criterion	Hosted 3CX	On-premises 3CX
Hardware to maintain	None	A server or virtual machine to monitor
Updates and backups	Handled by the host	Your responsibility or your provider’s
Continuity if the office loses its connection	Mobiles and remote workers keep working	The system can no longer be reached from outside
Local control of data	Depends on the chosen host	Full
Best suited to	Most SMBs, multi-site companies, mobile teams	Strong internal constraints, infrastructure already redundant

Continuity is often the deciding point: with a hosted system, a fibre cut at the office does not stop staff from answering on their mobiles.

What makes budget and effort vary

Two 3CX projects for SMBs of the same size can be very different. The items that weigh most:

• The number of simultaneous calls and the feature level chosen for the licence (recording, reporting, integrations).
• Physical handsets: an employee on a softphone needs no extra hardware, while a desk phone or DECT handset does.
• The state of the network: if the switch does not handle VLANs or the firewall cannot prioritise voice, it must be upgraded first.
• The SIP trunk and number porting, which depend on the carrier and porting lead times.
• Integrations: connecting the CRM or Odoo requires configuration and testing.
• The number of sites and how complex the call handling scenarios are (opening hours, public holidays, voice menus, queues per department).

Is 3CX right for your situation?

The table below summarises how we read a situation during a first conversation. It does not replace a call flow audit, but it quickly rules out the wrong options.

Your situation	Our reading
Many employees, few calls at the same time	3CX is a strong fit: the licence does not depend on the number of extensions
Mobile teams, remote work, field technicians	3CX is a good fit, preferably hosted, with the mobile apps
Several branches to connect under one phone system	3CX is a good fit, provided the network and voice priority between sites are done properly
Customer service handling calls, chat and WhatsApp	3CX is a good fit thanks to the unified interface and queues
Company already heavily invested in Microsoft Teams	Compare with Teams Phone or a 3CX integration inside Teams
Call centre with complex scripting, several hundred agents	Other specialised platforms may be a better fit

In most cases, the question is not whether 3CX will work, but how to integrate it cleanly with your network, your carrier and your business tools.

What you should know

• The network makes the quality. Voice VLAN, QoS on the firewall and, for multi-site companies, an SD-WAN that pins voice to a stable link. Without that, no IP phone system will keep its promises. The most frequent causes of choppy calls are listed in our 10 mistakes that ruin call quality.
• The SIP trunk matters as much as the PBX. A reliable carrier and a 4G backup gateway make the difference the day the fibre is cut.
• Very specific needs (call centres with complex scripting, several hundred agents) may justify other platforms. We say so when that is the case.

A six-step deployment method

A complete 3CX project for an SMB deploys in two to four weeks. The duration depends mostly on number porting and the state of the network, rarely on the phone system itself.

1. Call flow audit: who answers what, at what time, with what overflow. This is the moment to simplify what has piled up over the years.
2. Sizing the licence, choosing the hosting and the handsets (softphone, desk phone, DECT).
3. Network preparation: voice VLAN, QoS, firewall rules, backup link.
4. SIP trunk and porting: order from the carrier and schedule the porting of existing numbers.
5. Configuration and pilot: queues, voice menus, CRM integration, testing with a small group of users.
6. Cutover and training: switch numbers on a quiet day, short training per profile (reception, sales, managers), then adjustments during the first week.

For details on moving from an old PABX to IP telephony, see our guide on migrating to IP telephony.

Checklist before choosing 3CX

• Have you measured your peak simultaneous calls, including internal ones?
• Do you know who needs a physical handset and who can work on a softphone?
• Does your network have a voice VLAN and QoS configured on the firewall?
• Do you have a backup Internet link for voice?
• Does your carrier offer a SIP trunk and porting of your current numbers?
• Which tools must connect to the phone system: Microsoft 365, Odoo, a CRM, WhatsApp?
• Are your call handling scenarios (hours, holidays, overflow) written down somewhere?

Our approach

Audit of your call flows, licence sizing, handset selection, number porting, training and support included. We also tell you when 3CX is not the right answer. Details on our IP telephony page; for a first conversation about your situation, contact us.