Two sites or twenty

Stop running a separate phone system at every branch.

Each location keeps a local number and its own hours. Behind that, there is one directory, one set of rules and one place to change them. A call to the wrong branch is a transfer, not a dead end.

  • Local numbers for every site
  • Site-specific hours and holiday greetings
  • Transfer any call to any location by extension

A multi-location phone system puts every branch on one cloud service instead of a separate system per site. Each location keeps a local number, its own greeting and its own business hours, while staff share one directory and transfer calls between sites by extension. 3CTel configures site-level rules, overflow between branches and central administration so one person can manage every location from one console.

What changes when every site is on one system

Typical differences reported in planning conversations; your current setup may vary.
Today, with a system per siteOn one system
Each branch has its own number and its own voicemail; the head office cannot see eitherEach branch keeps its local number; every voicemail box and call log is visible in one console
Transferring a caller to another branch means giving them a new number to dialAny staff member transfers a live call to any extension at any location
Holiday hours are changed by phoning each branch and hoping someone does itHoliday calendars are set once per site, or once for all sites, from one screen
A busy branch lets calls ring out while a quiet one sits idleOverflow rules send unanswered calls from a busy site to another site or a central team
A new location means a new contract, a new install and a new set of rulesA new location is a new site record: number, hours, greeting and users

Site-specific where it matters, shared where it helps

The mistake in most multi-site rollouts is choosing between total central control and total local independence. Neither is what a branch manager or a head office actually wants.

The pattern that works is a small set of settings that live at the site level, and everything else shared. A caller to the Calgary branch should hear Calgary's hours and reach Calgary's staff first. But the Calgary staff should be able to look up anyone in Halifax by name and transfer a call there in one step.

Per site: number, greeting, hours

Each location has its own local number, its own recorded greeting and its own opening hours, including the branch that closes early on Saturdays.

Shared: the directory

Every user at every site is in one directory. Name, extension, location and presence. Transfers are by name or extension, never by dialling another branch's public number.

Shared: routing logic

The rules that decide what happens when a site is busy or closed are written once and applied to the sites that need them, with exceptions where a location is different.

Central: administration

One administrator sees every site. Adding a user, changing a greeting or setting holiday hours does not require a visit or a call to the branch.

Transfers and overflow between locations

  • Warm transfer to another branch: the receiving person is announced the caller before the call is handed over, even if they are two provinces away.
  • Overflow by site: if the Ottawa front desk does not answer within a set ring time, the call moves to a second site or a central team rather than voicemail.
  • Shared queues: a single 'orders' or 'support' queue can be staffed by people at several locations, with calls going to whoever has been free longest.
  • Local presentation: calls returned from a shared team can show the local number of the branch the customer originally dialled.
  • Site-level voicemail: a message left for a branch goes to that branch's email, with a transcript, and is visible centrally too.

Questions from operators with several sites

Can each location keep its own phone number?

Yes. Each branch's existing local number is ported to the shared system and continues to reach that branch first. Where a location needs a new number, a local number in that city's area code is provisioned. A single toll-free number can sit in front of all sites and route by the caller's choice or by the caller's area code.

How do different opening hours per site work?

Each site has its own schedule. A call to a branch that is closed hears that branch's closed greeting and follows that branch's after-hours path, while a branch that is still open keeps ringing normally. Holiday calendars can be set for all sites at once and then overridden for the location with a different provincial holiday.

Who manages the system when there is no IT person at the branches?

Typically one administrator at the head office, or an office manager, with 3CTel making changes on request. All sites appear in one console, so the same person who sets Vancouver's greeting sets Winnipeg's. Branch managers can be given access limited to their own site if that suits how the business runs.

AI agents across every location

Multi-site operators use AI to give every location the same quality of answer without staffing every desk. The AI Receptionist answers each site’s number with that site’s hours and address, the chat and messaging agent routes web and text enquiries to the right location’s calendar, and AI workflows tag every CRM task with the site code. Rules are set centrally and reviewed with a specialist for each rollout wave.

Site-aware AI Receptionist

One AI Receptionist carries every location’s schedule, holiday exceptions and directions, answers the head-office number by asking which site the caller wants, and transfers directly with the reason captured.

Bookings routed to the right site

Web chat and SMS from any location land in one inbox; the AI agent works out the site from the number texted or the postal code and books into that site’s connected calendar.

Compare sites, then approve changes

AI communication optimization compares missed calls and hold times across locations by hour and recommends where overflow should route or a second handset should ring. A regional manager approves each change.

Rolling out one site at a time

Emergency calling is configured with the registered service address for each site and each device, confirmed with you during rollout.

  1. Map every site

    Numbers, hours, who answers, where calls should overflow. This is captured per location with a 3CTel specialist before anything is configured.

  2. Build and test the first site on a temporary number

    The pilot branch's greeting, hours and routing are configured and tested before its number is moved. What is learned there is applied to the rest.

  3. Port site numbers in waves

    Each location's number is ported on its own confirmed date. Nothing at a branch changes until its port completes, so sites are never half-migrated.

  4. Hand over the console

    Your administrator is shown how to change hours, greetings and users across sites, and 3CTel remains available for changes you would rather not make yourself.

Frequently asked questions.

No. Each site uses whatever internet connection it has. Sites are on one cloud service, so the connection at one location has no effect on the others.

Bring every location onto one system.

Tell us how many sites you run, where they are and how calls should move between them. We will map a rollout and quote it.

Call 3CTelBuild My System