Feature — Multiple phone systems
Phone systems come and go. The call history stays.
Callnsight connects to the phone system rather than living inside it, so one account can hold several at once — a PBX per site, or two vendors side by side — and every call they produce lands in the same listings and the same reports. And because the calls belong to the account rather than to the box that made them, replacing a phone system does not reset the archive: the new system starts adding to what is already there.
What one account across several systems gives you
- Every site in one listing
- Head office and three branches, or a phone system inherited with each acquisition — connect them to one account and their calls arrive in the same table. Filter by direction, extension, caller ID or date range across the lot, and export exactly the rows you filtered.
- One set of figures, not four exports
- Call volume, talk time and the abandoned rate are computed over everything the account has connected, bucketed in your own timezone. The number for the business is a number you read, not a spreadsheet you assemble from each PBX in turn.
- Vendor-agnostic by design
- A connection belongs to your account, not to a vendor, and every system writes into one data model. Vodia and Broadvoice are the two integrations that ship today, and they run side by side in one account — head office on one, a branch on the other, one archive out of both.
- History outlives the phone system
- Calls and recordings are held against your account, not against the connection that fetched them, and only your retention policy ages them out. Change vendor and you are not starting a new archive — you are continuing the one you already have.
How systems come and go
Two minutes, per system
Add the connection
An account admin adds each phone system on the PBX Connections page: name it, pick the provider, give it what it needs, and run a connection test before trusting it. Credentials are encrypted before they touch the database and are never shown back to you — and if a system is awkward to reach, say so and we will set it up with you.
From then on
Different mechanics, one destination
Vodia is polled through its API every 15 minutes and backfills the history the PBX still holds; Broadvoice pushes each completed call over a webhook as it ends. The difference stops at the connection — past it, every call is one account’s archive.
When one is replaced
Stop the old sync, keep the old calls
Switching a connection off stops it pulling anything new in; it does not remove what it already brought. Where the plan has room for both, run the outgoing and incoming systems side by side through the cutover and let the reports cover the pair.
Questions
- Can I connect more than one PBX to a single account?
- Yes. An account holds connections to several phone systems and syncs them all, with the calls from each landing in one set of listings and reports. How many is a plan limit rather than a meter: one on the Trial and Starter, three on Growth, ten on Business, and as many as you need on Enterprise.
- Can I mix PBX vendors in the same account?
- Yes. A connection is scoped to your account rather than to a vendor, and every integration writes into the same data model, so a Vodia system and a Broadvoice system report together as one estate. Those two are what ships today, and the integrations pages spell out how each one connects — if you run something else, tell us through the contact form, because what gets built next is decided by what people say they run.
- Do I keep my call history and recordings if I switch PBX vendors?
- Yes, for everything already synced. Calls and recordings are stored against your account rather than against the connection that fetched them, so retiring a phone system does not take its history with it — switching a connection off stops new calls arriving without removing the ones that already did, and what is there stays for as long as your retention policy says. If you keep recordings on your own S3 or SFTP, the audio was never on our disk to begin with: we never delete a byte from your storage.
- Can I run the old and the new PBX side by side while I migrate?
- If your plan has room for both, yes — and it is the cleanest cutover, with the two systems reporting into one account while you move. Connections are plan-gated rather than metered, so on a single-connection plan an overlap means moving up for the month you need it.
- Will Callnsight import the history from the PBX I am leaving?
- It imports whatever that system still holds on the day it is connected. A first Vodia sync backfills the history the PBX has kept; Broadvoice only pushes calls as they complete, so a Broadvoice archive starts on connection day. Either way it is an argument for connecting the old system before you retire it rather than after.
- Who sets a new connection up?
- An account admin can, from the PBX Connections page — add the system, choose the provider, and test the connection before trusting it, within whatever your plan allows. Nobody has to wait on us to bring a site online, and if a particular system is awkward to reach we will set it up with you.
See it on your own calls.
Start with a 30-day trial on one PBX, or tell us what you run and roughly how many people answer calls — we’ll tell you where you land.