Every site runs a different phone system
One location has an old PBX, another has cell phones, a third has a system nobody remembers buying — and none of them can transfer to each other.
Multiple sites
Keep a local number and local hours for each site, route overflow to a central team, and compare performance site by site — across provinces and time zones, from one admin portal.
One location has an old PBX, another has cell phones, a third has a system nobody remembers buying — and none of them can transfer to each other.
A single set of business hours cannot serve a Halifax branch and a Vancouver branch. Calls arrive at closed sites and hit dead-end voicemail.
When one location is short-staffed, its calls simply go unanswered, even though another site is quiet at that exact moment.
There is no shared view of volume, answer rate or abandons per site, so nobody knows which location actually needs another person.
The pattern that works is local at the front, shared behind: each site keeps its own number and greeting, and a central team catches what the site cannot.
Each site publishes a number in its own area code — ported from the existing provider or newly provisioned — so it stays local to its market.
Each location has its own schedule in its own time zone, its own holiday list for provincial holidays, and its own recorded greeting.
The same options in the same order at every site, so a customer who calls two locations hears one company, and staff transfers stay predictable.
Calls that go unanswered at a site after a set ring time move to a central team or to a sister site, instead of falling into voicemail.
Each location gets its own numbers, and head office gets the comparison — volume, answer rate, abandons and peak intervals by site.
Illustrative routing for a company with branches in the Atlantic, Eastern and Pacific time zones and a central support desk.
| When | Then |
|---|---|
| Caller dials the Halifax number during Atlantic hours | Halifax greeting → Halifax ring group → central desk after 30 seconds |
| Caller dials the Halifax number at 8:30 a.m. Pacific | Halifax is already open → answered locally without central involvement |
| Caller dials the Vancouver number before Pacific opening | Early-hours greeting → central desk, which is already staffed in the east |
| A site is closed for a provincial holiday | That site’s holiday greeting → central desk or AI receptionist for bookings |
| Any site unanswered after two overflow hops | Voicemail to email routed to the site manager plus the regional manager |
| Caller asks for a different branch | Extension transfer between sites, no re-dialling and no external call |
Illustrative example — not live data
The design question is always the same: what stays local to a site, and what is shared across the company. Getting that boundary right is most of the work.
AI agents
The AI Receptionist answers each location’s number with that site’s hours, address, parking and holiday exceptions, and answers the head-office number by asking which location the caller wants and transferring directly. A store closing early updates its schedule once; the greeting and the AI answer change together.
The AI chat and messaging agent takes web chat and SMS from every site through one inbox, works out which location the customer means from the number texted or the postal code, and books into that site’s connected calendar. A local manager sees only their own conversations; head office sees all of them.
After each call or message, an AI workflow logs the summary against the correct location in your CRM, opens a ticket with the site code attached, and schedules callbacks to the local team. Head office sets approval modes centrally, and the audit trail shows what ran at which site.
AI communication optimization compares missed calls and hold times across locations by hour, recommends where a second handset should ring or where overflow should go to a neighbouring site, and flags any site whose conversation intelligence shows a rise in complaint or cancellation keywords for a regional manager to review.
Reliable calling with routing your team will actually use.
Learn more: Business PhoneLocal, toll-free and campaign numbers that all land in one system.
Learn more: Business Phone NumbersSee what your phone traffic is actually doing — and staff for it.
Learn more: Call AnalyticsQueues, routing and supervision for teams that live on the phone.
Learn more: Contact CentreAnswers, understands and books — in English and French.
Learn more: AI ReceptionistMulti-site integrations are scoped during planning, since systems often differ between locations.
We document each location’s numbers, hours, staff and existing equipment, then agree what is local and what is shared.
Each site’s numbers are ported or provisioned on its own schedule; existing lines keep working until each site’s switch date.
One location goes live first as the template, then the remaining sites follow in an agreed sequence rather than all at once.
Each location manager is trained on the changes they own — greetings, hours and staff — before their site cuts over.
Yes, and it usually should. Local numbers are ported from each site’s current provider, and new local numbers can be provisioned in any Canadian area code we can supply.
Business hours and holiday schedules are set per site in that site’s time zone. A branch in Newfoundland and a branch in Alberta each open and close on their own clock.
Yes. All sites share one extension plan, so transferring to another branch is an internal extension transfer rather than an outside call.
Yes. Site-level admin roles let a manager update their location’s greeting, hours and users without any ability to change another site’s configuration.
Emergency calling is configured with the registered service address for each location and each device. Addresses must be updated when a site moves or a device is relocated.
Yes. Call volume, answer rate, abandons and peak intervals are reported per site, with a company roll-up so head office can compare locations on identical measures.
Tell us your locations, hours and volumes, and we’ll quote a design that keeps each site local and the company connected.