If you run a multi-location agency on 3CX and your CRM is the one your team logs into every day, you have a clear path to tie phone calls into customer records without changing your phone system. Connect Zero for 3CX is the bridge that sits between the two, streaming live call events into your CRM, attaching recordings to the matching contact, and firing workflow triggers on missed calls.
TL;DR: Multi-location agencies on 3CX get a flat-per-location CRM bridge that maps cleanly to the sub-account-per-location pattern. USD 39 per location per month. Each location installs the bridge independently or shares one 3CX system with extension mapping. Two-minute install per location.
Multi-location agencies face a structural mismatch between the phone system and the CRM. The CRM uses a sub-account-per-location pattern. The phone system is often a single 3CX install shared across locations. Without a bridge, the multi-location agency has to choose between losing call data per location or running multiple 3CX systems. Most agencies pick the first option and live with the per-location call data being incomplete.
What pulls multi-location agencies toward Connect Zero for 3CX is the flat-per-location pricing combined with the extension-mapping model. Each location is one Connect Zero install and one CRM sub-account. A single 3CX system can serve many locations because extensions map per location. Pricing is per location, not per agency, so a ten-location agency pays USD 390 base plus usage. Adding a new location is one install.
The habit that traps multi-location agencies is the central-call-log pattern. The phone system holds all calls in one log and the agency reconciles them to locations manually. The bridge replaces that habit by mapping calls to locations at the moment they happen via extension mapping. Reconciliation becomes automatic.
The anxiety with any new tool for a multi-location operator is rollout consistency. Connect Zero for 3CX installs from the CRM marketplace per location. Each location’s install is two minutes. There is no central rollout project because each location is independent. Agencies can roll out location by location at their own pace.
Multi-location agencies sit between the typical small-business pattern and the enterprise pattern. The CRM organises by sub-account-per-location, the phone system organises by extension, and the bridge between them has to map extensions to locations. Without a bridge, the agency runs one of two patterns. Option one runs separate 3CX systems per location, which doubles the PBX cost and forces operations to manage many phone systems. Option two runs a single 3CX system across all locations and accepts that per-location call data lives in spreadsheets reconciled at month-end. Most agencies pick option two, and the per-location reporting suffers as a result. Principals have no live view of which locations are answering calls and which are missing them. Capacity planning, location performance and inter-location workload transfer all run on stale data.
Connect Zero for 3CX uses the flat-per-location pricing model and the extension-mapping pattern to match the multi-location agency reality cleanly. Each location is one CRM sub-account, one Connect Zero install, and a slice of the shared 3CX extension list. The bridge writes calls to the right CRM sub-account based on which extension answered. Principals see per-location call volume in real time from the agency CRM dashboard. Missed-call rates compare across locations. Recordings attach per location. Workload transfer between locations becomes visible. New locations install the bridge in two minutes from the marketplace. The pricing scales linearly with location count rather than seat count.
Five steps, about two minutes from start to first call event in your CRM.
If your 3CX system is behind a VPN or restricted by IP, you allowlist the Connect Zero outbound IPs (documented in the setup guide) and the bridge connects without further configuration.
Yes. The bridge maps 3CX extensions to CRM users in CRM sub-accounts. Each sub-account is one Connect Zero install. The shared 3CX system delivers calls to the relevant extension, the bridge routes the call event to the matching CRM sub-account, and the CRM treats it as a per-location call.
Yes. Each location installs the bridge from the CRM marketplace independently. This is what makes per-location billing clean and per-location data clean. Each install takes about two minutes.
Yes. The agency CRM dashboard slices call activity by sub-account (which maps to location). Principals see per-location call volume, missed-call rate, average ring-time, and complaint patterns. Regional managers see the slice for their region.
USD 390 per month base (ten locations at USD 39 each) plus usage meters across the locations. Adding an eleventh location adds USD 39 per month base. There is no per-seat fee, so user count within each location does not affect the bill.
Three ways to start, in increasing depth.
Two related pages worth a read before you decide: the Aircall-to-CRM bundle comparison covers the cost shape if you are weighing a PBX replacement, and the JustCall-to-CRM bundle comparison does the same for the JustCall path. The Connect Zero pricing page lays out the meters with a worked monthly example, and the setup guide walks through the same five-step install in more detail.
For specific team sizes within each location, see the 1-5 users, 5-25 users, 25-100 users and 100+ users pages.
Last updated 2026-05-24 by the Connect Zero team. Adelaide, South Australia. Questions about your specific 3CX setup? Use the contact page or email hello@connectzero.com.au.
Summarize your business so the visitor can learn about your offerings from any page on your website.
