Contact center

Running a Contact Center Across Several Sites: A Guide

Run phone support across several offices or regions: shared standards, routing between sites, time zones, staffing, reporting and one voice for callers.

Call editorial team · Published · 6 min read

Many organisations end up with more than one place that answers the phone: two offices after a merger, regional teams close to customers, a night team on the other side of the world. Each site makes sense alone. Together they can feel like several companies: different greetings, different rules, different answers to the same question. Callers do not care which building picks up. They want the same quality every time.

A world map on a screen showing several office locations linked by lines
Illustrative image

This guide covers how to organise standards, routing, staffing and reporting across sites. For the remote side of this, see Running a Remote Contact Center and Running Hybrid Office and Home Support Teams.

Why organisations run several sites

Common reasons for more than one site

  • Local knowledgeCallers prefer someone who knows the area, language or market.
  • CoverageA team in another time zone can extend hours without night shifts.
  • ResilienceIf one site is affected by an outage or weather, another can take calls.
  • Growth and mergersAcquired teams arrive with their own phones and habits.
  • TalentHiring where the right people live rather than where the head office sits.

Each reason shapes the design. A site kept for local knowledge needs room to be local. A site added for resilience needs to be interchangeable. Know which kind you have before you decide how similar the sites should be.

Standardise what the caller notices

Make a short list of things that must be the same everywhere and a list that may differ. A good rule is to standardise anything the caller or the customer record can see.

Same everywhere or local

Same everywhereMay differ by site
Caller experienceGreeting style, hold messages, menu logic, how to reach a personLanguage, local opening hours, regional options
AnswersPolicies, prices and product informationLocal services, addresses and holidays
QualityScorecard, coaching approach, targetsLocal examples and emphasis
DataCustomer record, call notes, tags and outcomesLocal teams and queue names
ToolsThe same system, roles and settingsSite-specific shifts and breaks

Put the standards in one place and give one person the job of keeping them consistent. Documenting Support Processes Agents Actually Use explains how to write them so they are used. Quality management needs to be shared too: see Running QA Calibration Sessions for ways to keep reviewers aligned across locations.

Design routing between sites

The core design question is where a call goes. Several patterns are common. Pick the simplest one that works, and write it down.

PatternHow it worksSuited to
Local firstCalls go to the site that serves the caller's area; others take overflowRegional businesses with local knowledge
Follow the sunCalls go to whichever site is openWide time-zone coverage
Skill-basedCalls go to the site with the right language or expertiseSpecialised or multilingual support
Single queueAll sites draw from one shared queueSites with equal skills and a need for even workloads
Primary and backupOne site answers, another takes over during outagesResilience for a single main site

Routing by region or caller language relies on clear data. Language Selection Menus in IVR and IVR Routing for Businesses with Many Departments discuss the menu side. Whatever you design, test each route, including after-hours and holiday behaviour at each site; regional holidays are an easy thing to forget.

Who decides what

Multi-site operations stall when nobody knows who can make a call. Decide which choices are central and which are local. Central: the standards, the tools, the reporting definitions and the routing design. Local: rotas within the rules, local campaigns, and how the team is led day to day. Write this on one page and review it yearly. Without it, every question about a greeting or a holiday becomes a negotiation between sites, and decisions are made by whoever shouts loudest or acts first.

Give each site a lead who is accountable for results and also sits on a small cross-site group that meets regularly. That group owns the shared standards and approves changes, so that a new greeting or a new menu option rolls out everywhere on the same day instead of site by site over months.

Time zones, holidays and opening hours

When sites sit in different time zones, a rule that says "open at nine" means something different in each. Store hours with the time zone of the site, and show callers the opening hours in terms they understand. Keep a calendar of holidays for each site and region, and review it before each year starts. A site closed for a local holiday should not lose calls: have its queue route to another site or offer a callback and voicemail. Routing Calls by Business Hours, Holidays and Closures describes how to set this up.

Staffing across sites

Treat the sites as one pool where you can and as separate pools where you must. Forecast the whole demand, then decide how to split it. Pooling smooths peaks: a busy hour at one site can be absorbed by another, which means fewer people overall for the same service. It works only if skills match, so invest in cross-training. See Forecasting Call Volume for Small Teams and Workforce Management for Contact Centers.

One customer record, whichever site answers

A caller who rings a second site should not have to start over. Make sure every site writes to and reads from the same customer record, with the same fields and tags. Agree what to log after each call and where. If sites use different systems, build or buy a clear connection and test it with real cases. One Customer, One History Across Channels describes what a single view needs.

Report by site and in total

Use identical definitions for all sites: what counts as answered, abandoned, resolved and how handle time is measured. Show results side by side to find what works and share it, but be careful about league tables. Sites differ in call mix, language and customer base, so a ranking can mislead. Look at trends over time at each site first, then at the gaps between them. Share good practice in both directions. What Contact Center Supervisors Should Monitor and Contact Center KPIs Explained offer starting points.

Multi-site health check

  • Are greetings, menus and key answers consistent across sites?
  • Do all sites use the same definitions in reports?
  • Has every route, including overflow and closures, been tested recently?
  • Do regional holidays and time zones appear in the hours settings?
  • Can any site see the full history of a customer?
  • Do the sites meet regularly to share what they learn?

Build one team

Sites can drift into rivalry or suspicion. Prevent it with regular joint meetings, shared goals and visible respect for each site's strengths. Rotate who hosts the meeting. Share a common chat channel. When something goes wrong at one site, treat it as a system problem and ask what to change in the shared process. When something goes right, tell everyone.

Running several sites in Call

In Call, queues have their own hours and routing, and each phone line can have business hours with a time zone. Holidays and closures can be set in advance. If you belong to more than one workspace, you can switch between them from the sidebar. Supervisors can watch queues, and roles control what each person sees. See Setting Up Call Queues: Members, Priority and Overflow, Business Hours, Holidays and Closures in Call and Switching Between Workspaces in Call.

Frequently asked questions

Should every site use the same phone system?

Ideally yes. A shared system makes routing, reporting and the customer record much simpler. If that is not possible, define clear connections and test them.

How do we choose which site answers a call?

Start from the caller's need: region, language or skill, then add overflow rules. Keep the design simple and document it.

What happens if one site goes offline?

Plan a backup route: another site takes the queue, or callers hear a message with a callback option. Test the plan before you need it.

How do we keep quality consistent?

Use one scorecard, hold joint calibration sessions and review calls from every site in the same way.

Is it fair to compare sites?

Only with care. Compare trends and use the same definitions, but account for differences in call mix, language and customer base.

Manage several teams and queues in one place with Call

In the demo console you can try incoming calls in a simulation.

Related guides