🏒 Multi-site

One tenant, every site, every user.

Run 2 branches or 20 from a single admin. Each site keeps its local CLI and DIDs. Centralised dial plans, hot-desking between sites, presence and chat across the whole organisation.

Sound familiar?

When “simple” multiplies by every branch.

🧩

A separate system per site

Each branch on its own bill, its own admin, nothing talking to anything else.

πŸ”€

No clean way to transfer

No 4-digit dial, no presence-aware transfer between offices — just a re-dial and a guess.

🌐

One site drops, calls vanish

An internet outage at a branch and that office goes dark until it comes back.

Built for multi-site teams

Built so head office can sleep through the rollout.

When you have multiple sites, simple things become complicated. We’ve done the hard parts so you don’t have to architect them.

🌐

Centralised admin

One pane of glass for all sites, users, queues, DIDs.

πŸ”€

Inter-site routing

4-digit dial between sites, presence-aware transfer, follow-me.

πŸͺͺ

Hot-desking

Log into any handset at any branch β€” your DID, your speed-dials, your settings.

πŸ“‹

Role-based admin

Branch managers get their site only. Head office gets everything.

πŸ›Ÿ

Per-site failover

Site internet down? Calls auto-route to mobile or sister site.

πŸ”Œ

REST API + webhooks

Hook into your existing dispatch, CRM or BI tooling.

Real example

Bespoke quote β€” let’s scope it together.

Above 20 users we don’t do off-the-shelf pricing. There are too many variables: how many sites, how many DIDs, do you need recording, are you migrating from a legacy PBX, what’s your existing M365 estate.

Send us a current setup diagram (or just a current bill) and we’ll come back inside 48 hours with a fixed-fee migration scope, monthly per-user rate, and a cutover timeline.

We’ve done multi-site rollouts in healthcare, retail, real estate and professional services. There’s rarely a curveball we haven’t seen.

Migration of 67 users across 4 sites with zero downtime. The IppyComms team did weekend cutovers so the office was never disrupted.
PS
Pat S.
CIO Β· regional services group
Recommended stack

Suggested plan & kit.

πŸ’°

Custom plan

Volume-priced per-user. Often below our Business tier at scale.

🟦

Teams calling option

Direct Routing for all users if you’re Microsoft-first.

πŸ›Ÿ

White-glove migration

We do the project plan, runbook, weekend cutovers and post-go-live support.

How we switch you over

A rollout head office can sleep through.

Discovery + scope

Send a bill or a setup diagram; we return a fixed-fee scope within 48 hours.

We port every site

Each branch keeps its local CLI and DIDs — moved across with zero downtime.

Central config + failover

Inter-site dialling, hot-desking, role-based admin and per-site failover, then you test.

Weekend cutover + support

White-glove cutovers out of hours, then post-go-live support from Ipswich.

Why switch

Why multi-site teams switch to us.

🌐

One pane of glass

Run 2 branches or 20 from a single admin — users, queues and DIDs in one place.

πŸ›Ÿ

Built-in failover

Site internet down? Calls auto-route to mobile or a sister site, automatically.

πŸ’²

Volume-priced

Above 20 users we volume-price per user — often below our standard Business tier.

FAQ

Questions multi-site teams ask us.

How is multi-site pricing worked out?

Above 20 users we volume-price per user — often below our standard Business tier. Send a current bill or a setup diagram and we’ll come back within 48 hours with a fixed-fee migration scope and monthly rate.

Can each branch keep its own local number?

Yes. Every site keeps its local CLI and DIDs while you run the whole organisation from a single admin.

What happens if one site loses internet?

Per-site failover automatically reroutes that branch’s calls to mobiles or a sister site, so the chain keeps answering.

Can branch managers administer only their own site?

Yes — role-based admin gives branch managers their site only, while head office sees everything from one pane of glass.

Do you handle migrating us off a legacy PBX?

Yes. We run a white-glove migration: project plan, runbook, weekend cutovers and post-go-live support, with zero-downtime rollouts.

Can it integrate with our CRM, dispatch or BI tools?

Yes — a REST API and webhooks let you hook IppyComms into your existing dispatch, CRM or reporting stack.

Let’s scope it together.

Drop us a line with your site count and approx user count. We’ll book a 30-min discovery call and come back with a fixed-fee scope.