One invoice, or one per site
Head office can receive a single invoice with a per-site breakdown, or each location can be billed separately. The arrangement is agreed when the account is set up.
Buyer's guide for several sites
Buying one phone system for five, fifteen or fifty locations.
The hard part of a multi-site phone project is not the technology. It is the rollout: which site goes first, which numbers move when, who pays for what and who is allowed to change the greeting. This guide is about those decisions.
- A rollout plan, one site at a time
- Local numbers kept at every location
- One invoice, one console, site-level permissions
Example
Incoming call+1 (416) 555-0198
Main menu9–17
11 — Appointments
22 — Renewals
33 — Billing
After hours
Reception queue90 s → Callback offered
AI receptionist
Voicemail to email
A multi-location phone system puts every site on one cloud service with a local number per location, site-specific hours and greetings, a shared directory and one administration console. Buying one well means planning the rollout order, deciding which numbers port and when, agreeing how billing is split across sites and setting who can change what. 3CTel plans the rollout with you and moves sites in stages.
Planning the rollout
Inventory every site
Numbers, hours, headcount, who answers, current provider and contract end date. Sites on expiring contracts and sites with the most missed calls usually move first.
Choose a pilot
One typical site, not the head office. It proves the routing, the devices and the training with the least disruption, and what is learned is copied to the rest.
Build a standard site template
A greeting structure, hours, a ring group or queue, overflow and voicemail that every site starts from. Exceptions are added per site, not invented per site.
Schedule ports in waves
Numbers move in groups so the team supporting the change is never stretched across too many sites at once. Each wave has an agreed switch date.
Train by role, not by site
Front desk staff, managers and mobile staff each get a short walkthrough of what they use. A one-page guide per role travels with every wave.
Multi-location business
Every branch on one system, with its own number, hours and greeting.
Learn more: Multi-location businessNumber porting
How a port works, what you need to provide, what causes delays, and what 3CTel does at each step.
Learn more: Number portingMulti-Location Business
A local number per site, one system behind all of them.
Learn more: Multi-Location BusinessA number for every site
Customers call the branch, not the company. Each location keeps its existing local number, and a new location gets a number in its own area code. A toll-free number can sit in front of everything for advertising, routing callers to the nearest site by their area code or by a menu choice.
- Ported numbers keep ringing at their original site first, then overflow according to the site's rules.
- A new location's number is provisioned before opening day so it can appear on signage and listings early.
- Calls returned from a central team can show the local number of the branch the customer originally called.
- Texting is enabled per site number, so a reminder from the Regina branch comes from the Regina number.
- When a site closes or merges, its number is redirected rather than lost, and callers hear the new arrangement.
Business Phone Numbers
Local, toll-free and campaign numbers that all land in one system.
Learn more: Business Phone NumbersLocal vs toll-free numbers
Which number goes on the sign, which goes on the website, and why the answer is often both.
Learn more: Local vs toll-free numbersBusiness SMS
Text from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSCentralized billing and administration
One console
Every user, number, greeting and schedule for every site is visible in one place. Adding a location does not add a login.
Site-level permissions
A branch manager can change their own hours and greeting without seeing other sites. Head office keeps the template and the numbers.
Reporting across sites
Compare answered and missed calls by location, spot the branch that lets calls ring out, and see wait times per site without asking each manager.
Holidays in one place
Set the national holidays once and the provincial ones per site. A single change covers every location that shares the rule.
A standard that holds
Because sites start from a template, the caller experience is consistent even when the branch manager changes.
Franchises and independently owned locations
Franchise systems add a question the corporate multi-site does not have: who owns the number and who pays the bill. The pattern that works is a brand-level template and brand-level toll-free routing, with each franchisee's local number and users on their own billing arrangement inside the same system. The franchisor keeps the customer experience consistent; the franchisee keeps control of their own site and their own costs.
A franchisee who leaves the system can take their users out without disrupting the brand's routing, and a new franchisee starts from the template on day one.
Retail & E-commerce
Per-store hours, stock-check routing and pickup texts for stores and online orders.
Learn more: Retail & E-commerceAutomotive
Sales, service and parts routing with vehicle-ready texts and per-campaign numbers.
Learn more: AutomotiveEnterprise
Contact centre and back office on one platform, migrated in stages.
Learn more: EnterpriseQuestions from operators buying for several sites
Should we move every site at once or in stages?
In stages, almost always. A single cutover concentrates every problem into one day and stretches the team supporting it. A pilot site followed by waves of a few sites each lets the template improve between waves and keeps each switch date manageable. The whole rollout can still be quick; the point is that no single day carries all of it.
How do we handle a site with a different provider contract that has not expired?
Connect it last, or forward its number to the new system in the interim so callers get the standard experience while the contract runs down. Review the contract for early-termination terms and porting notice requirements. The rollout plan can list each site's earliest sensible move date so nothing is forced before it makes financial sense.
Can head office answer overflow for every branch?
Yes. Each site's rules can send unanswered calls to a central team after a set ring time, with the branch name shown to the person answering so they know which location the caller wanted. The central team transfers back by extension when the branch is free. This is one of the main reasons operators consolidate onto one system.
Call routing
Decide who answers, in what order, and what happens when they cannot.
Learn more: Call routingContact Centre
Queues, routing and supervision for teams that live on the phone.
Learn more: Contact CentreCall queue
Callers wait in order and are delivered one at a time to the next free agent.
Learn more: Call queueWhat to ask any provider
| Question | Why it matters |
|---|---|
| Can each site keep its local number and its own hours? | Callers expect the branch, and provincial holidays differ |
| Can a site administrator be restricted to their own location? | Branch managers need access without risk to other sites |
| How is billing split across sites or franchisees? | Cost allocation and franchise agreements depend on it |
| How are numbers ported in waves, and what is the switch process? | Rollout order and risk are decided here |
| Can a central team see and answer calls for any site? | Overflow and consistency across locations |
| What happens to a site's calls when its internet is down? | Continuity per site, not just for head office |
| Is the pricing quoted per site and in total before commitment? | No surprises when site fifteen is added |
Related pages.
Multi-location business
Every branch on one system, with its own number, hours and greeting.
Learn more: Multi-location businessMulti-Location Business
A local number per site, one system behind all of them.
Learn more: Multi-Location BusinessBusiness Phone
Reliable calling with routing your team will actually use.
Learn more: Business PhoneBusiness Phone Numbers
Local, toll-free and campaign numbers that all land in one system.
Learn more: Business Phone NumbersCloud phone system
No server in the closet. One portal for every user, site and rule.
Learn more: Cloud phone systemRetail & E-commerce
Per-store hours, stock-check routing and pickup texts for stores and online orders.
Learn more: Retail & E-commerceFrequently asked questions.
No practical limit either way. Two locations benefit from a shared directory and central hours; larger estates benefit most from the template and reporting.
Yes. Holidays are set per site, with a shared national set and provincial overrides.
Yes. Billing can be arranged per location while the routing and template stay under the brand's control.
No. A front counter might use a desk phone while a mobile team uses the app. The template covers routing; devices are chosen per site.
Yes. A new site is created from the template with a new local number, usually well before opening day so the number can be published.
Bring the list of sites.
Numbers, hours and headcount per location are enough for a specialist to propose a rollout order, a site template and a quote per site and in total.