Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Customer Experience, Retention & Loyalty › Service and Support

Running Customer Service Across Several Sites

How a business with several sites keeps one service standard: what the centre sets, what a site decides, one contact record, shared remedies, fair comparison.
Guideintermediate18 min readUpdated

Why several sites change the job

With one site, the owner can stand close to the counter. A complaint at the till, a call about opening hours and a comment about the car park can reach the same person without anyone having to pass them on. A new site adds a place where customers meet the business with nobody from the centre present, such as a phone in a back room or a local review page.

Customers may not see that structure. A customer may book at one site and collect at another, ring the nearest site about a problem that began elsewhere, or set an answer given at their counter beside the one a relative was given at a different branch. The reasoning that the guide on centralised and local marketing control applies to marketing holds for service as well: the centre keeps what must be identical for the brand to mean one thing, and the sites keep what only someone standing in the place can get right.

The recovery work does not change because there are more sites. The recovery sequence, the written remedy, the single log, the tone guide and the reason list are all as necessary as before. What changes is that each of them now needs an answer to a question the single-site business has no reason to ask: does this belong to the centre, to the site, or to both? This guide answers that question for each, and then covers the routines that keep the answers in force. It does not cover franchise agreements or who is legally responsible when sites are run by separate operators, which are questions for the business's advisers; it does not cover regulated sectors, which have their own complaint rules; and it sets no staffing numbers or rotas, because no source this site cites gives any.

What the centre sets and what a site decides

Write each service decision as a row in a RACI matrix, as the guide on working with an outsourced customer service team does for a partner. Each row needs exactly one accountable role.

The test for the line is simple. If the customer's trust depends on the decision being the same everywhere, it belongs to the centre. If it depends on being right for this place today, it belongs to the site.

DecisionThe centre setsA site decidesReason for the split
Response standardHow quickly each channel is answered, how the promise is worded and the approval of each site's hours in the master recordThe hours it actually staffs, proposed for the master recordA promise that differs by site is several promises, but hours are a fact about a place
Tone and repliesThe tone guide, the shared reply library, owners and review datesThe local details inside a reply, such as who is on duty, with address and hours filled from the master recordCustomers hear one voice, and local facts come from the master record
What counts as a complaintThe definition, the fields and the single logTaking the complaint and logging it within the time the procedure setsCounts can be compared only if every site counts the same thing
Reasons for contactThe shared list, with a definition for each reason and a log of changesChoosing a reason at the end of each contactReasons can be compared only if the list is shared
RemediesThe remedy table, the goodwill allowance and the approval levelsUsing the table and the allowance without askingThe same failure should get the same remedy at every site
Serious casesThe route up, the named people and their cover, and the cases that go up whatever the amountSending the case up promptly with its historyThese cases go up whatever the amount, and the route is the same from any site
Campaign and policy changesThe brief, the end date and what staff may offerReading it before opening and passing on the questions customers askSites should not learn a change from customers
Local answersThe place they are recorded and reviewedThe answer: stock, waits, events, who is inOnly the site knows, so only the site can keep it current
Measures and reviewDefinitions, scorecard, sampling and reviewersReading its own results and acting on themA site's own conversations are scored by someone outside the site
Public replies to local reviewsThe reply guideline and the escalation listReplying in a local voice within the guidelineThe reply is read later by prospective customers of the brand

A single record for contacts that start at a site

Every contact, from every door, belongs in the same record under the same reasons. A site's contacts arrive by the site phone, at the counter, in a shared inbox and on the local review page, and the sites differ in how much of that reaches a system. The phone and the counter reach a system when someone writes the contact down, so the central picture can make a site that records little look calmer than it is. Build the reason list once for the group, put it where every site records, and, as general practice, agree that a contact is recorded at the site where it was handled and counted centrally under the same contact reasons.

As general practice, record the customer, not only the site. A customer who used one site on Monday and another on Friday should not have to explain Monday to the second. The guide on reducing customer effort names repeating themselves as one of the costs the business moves onto its customers, and several sites multiply the places where it can happen. The second site should be able to see what the first was told, what was promised and what is due.

As general practice, when a contact moves between sites, or from a site to the centre, a short handover note travels with it: who the customer is, what they asked, what was said or promised, what happens next and by when. One person owns the case at a time, and, as general practice, the site where it began keeps it until the centre says in writing that it has taken it. The customer is told who has it now and when they will hear, as the recovery guide asks for any escalation. A conversation that each of two sites assumes the other owns is one way a promise gets missed.

Keep the facts customers use to reach each site in one place. The master record in the guide on location pages and listings at scale holds each site's phone number, hours and status with an owner for every field, and the contact page should show each site's route with the hours it is answered, copied from that record. Hours and reply times published this way make up the response standard that customers actually see, and each site keeps to what it has published. When a site changes its hours for a holiday, the opening hours change procedure updates every public copy, so that a customer is less likely to find a site closed that a listing said was open.

The record holds personal data, and a record that every site can search holds more of it than any one site needs. Record only what handling a contact and learning from it need, give each site access by role to its own customers and to the shared history that bears on them, and hold entries for the period the business has set, which is the way the site's data guides read the GDPR. Whoever owns data protection sets the rules, and nothing here is legal advice.

Complaints, remedies and who may decide

The complaints procedure applies as one document across all sites. A complaint is defined the same way at every site, taken and logged within the time the procedure sets, and answered against the same acknowledgement and response promises. The procedure names who investigates and who decides, and with several sites it should say which of those people sit at the site and which at the centre. A complaint about the site manager, or about how the site handled a previous complaint, is decided above that manager.

Remedies are one place where a difference between sites shows. The case for written remedies in the remedy table tutorial is that customers with the same failure are offered the same thing, and that has to hold across sites too. One site that offers a free repair for a fault, a second that offers a partial refund and a third that refuses are making three different promises. The remedy table and allowance are therefore one document for the group. Site staff use the remedy table and the goodwill allowance without asking anyone, because a customer waiting at a counter for approval from another building has been given no remedy at all. Above the allowance, the approver at the centre or in the area is reached by the route the remedy table tutorial sets out, cover for absences included.

The remedy a customer is offered should not depend on which site served them. The service recovery and complaints guide reads the business guidance that the Competition and Markets Authority has published as general direction: customers have remedies when what they received falls short of what they were promised, and a business must not mislead them about those rights. The remedy table tutorial keeps that obligation apart from goodwill. The allowance sits in the goodwill part. Rights vary by country and sector, as the recovery guide notes, so whether a particular failure is an obligation is a question for the business's advisers, and the tutorial asks for the rights column to be reviewed by a person qualified in the sector and country.

Some cases go up whatever the site and whatever the amount: safety issues, legal threats, repeat failures and customers in difficult circumstances. The recovery guide names disputes over large sums as a further reason to go up. The guide on supporting customers in vulnerable circumstances asks for named people who may adapt the process, and with several sites those people need to be reachable from every site by the same escalation route, not found by whoever happens to know them.

The complaint itself, and the public reply to a review that carries it, are separate pieces of work. The reply follows the reply guideline of the guide to managing reviews at each location in the site's own voice. The complaint is logged centrally like any other, so that a pattern across sites is visible to the people who can remove its cause.

Voice and answers that travel between sites

One tone guide covers every site. The tone guidelines tutorial decides the choices once, by situation, so that an agent at any site writes the same kind of apology and refusal. Local character belongs in local facts: the name of the person on duty, the detail about the neighbourhood, the thing only this site can offer. It does not belong in a different register for a different site.

Keep one library of saved replies for the group, following the saved replies tutorial: one reply per question, each carrying its owner and a date for review, and marked gaps where an agent must write something. At a group of sites those gaps are the local facts. Do not let each site keep a copy and edit it. Where a reply needs a site's address, hours or phone number, fill it from the master record or, as general practice, from a short site card kept with the library, not from memory.

As general practice, give each site a sheet of local answers that its manager owns: what the site can and cannot do, current waits, local events, who to ask. Put a review date on it, and make the manager the one accountable role for its accuracy. Questions the centre cannot answer about a particular site should go to the site's sheet, not to a guess, and a customer who reaches the centre with such a question should be passed to the site with a note rather than sent away to ring again.

A change to a policy, an offer or a remedy reaches every site at the same time and by the same route, as a brief, early enough for agents to read it before the first customer asks. The campaign briefing tutorial shows what the brief holds: the exact terms, the claims, the likely questions and what staff may offer. A site that learns of a change from a customer answers from the old version until it hears otherwise, and a second site may answer differently. A new member of staff at any site starts from the same pack: the tone guide, the shared replies, the remedy table and the escalation route.

Reading service by site without a league table

Define each measure once for the group, as the customer service metrics guide asks, and read it by repeat contacts and by reason as well as by site. Then compare each site with its own history before comparing it with any other. Read a site's movement against its own past range before comparing its average with the group's average.

Counts per site can be small. A reason with a handful of contacts at one site jumps around from one reading to the next, and a ranking of sites by a rate on those counts is a ranking of noise. The guide on reading small numbers covers the remedies: show the counts behind every rate, report a range rather than a point, pool weeks while volumes are low and be wary of league tables. A control chart draws each site's normal range from its own history, so that a movement outside it is flagged and a movement inside it is left alone.

Sites also differ in what they serve. A site in a transport hub, one in a residential street and one with a large car park may meet different customers, and their contact reasons can differ because of the place, not because of the service. As general practice, compare like with like, and read a difference in reasons as information about the place before reading it as a verdict on the people.

Be careful what a site is asked to hit. Goodhart's law warns that a figure people are rewarded for hitting soon describes the effort to hit it rather than the service. A target for fewer logged complaints rewards the site that records the fewest, and the site with the longest log may simply be the one that writes complaints down. Pair every measure that could become a target with the measure that would expose it, and, as general practice, check each site's recording by asking its staff about a sample of its counter and phone contacts and comparing the sample with its log at a set interval. A log that is shorter than that sample suggests it should be points to under-recording, however calm it looks.

Reviewing conversations across sites

Review conversations from every site on one scorecard, following the quality review tutorial. Draw the random sample so that each site appears in it, add the complaints and escalations from every site, and report them separately from the random sample, as the tutorial advises. As general practice, where one site's conversations are reviewed by someone at that site, the review stays with the side being judged, so have a reviewer from outside the site score them.

Calibrate reviewers on conversations taken from several sites, so that a score does not depend on which building the reviewer came from. Then read the findings for their reach. A problem found at one site is a local matter for coaching or for the manager's routine. A problem found at several sites is better read as one fault than as several lapses: it points to the shared document, the unclear remedy row or the missing brief, and it belongs to the centre's owner of that document.

When a site wants to differ, and when a site falls behind

A site may need to do something differently: a local arrangement, an unusual customer base, a building that cannot take the standard layout. As general practice, ask for the variation in writing, with the reason, an owner and an end date, and keep the granted variations on one list the centre owns. A variation that changes what customers are promised, such as a remedy or how quickly a channel is answered, is not local, because customers can see the difference. A variation about a local fact, such as an extra hour on a Saturday, goes into the master record, where the location pages guide has regular hours approved centrally, and onto the same list. Look at the list whenever the shared documents are reviewed: a variation that helped customers is a candidate for the whole group, and the centre should be as willing to learn from a site as to instruct it.

When a site falls behind, read the cause before the people. Take the cause to a point a team can change with the five whys: is it a vacancy, a stock fault that is generating contacts, a manager who has not seen the latest brief, a phone that is not being answered? The centre then helps with the cause, by cover, a rerouted line or a fix to the shared document, instead of sending the site a score. Management by exception suits the decision about when the centre steps in: agree the limits in advance, such as a site outside its own range for a stretch the business sets, or any serious case, so that the centre does not hover over a site that is within its range and does not stay away from one that is not.

When a site closes or moves, its customers, open cases and promises have to be handed over, not just its listing. The moving or closing a location tutorial covers telling customers and protecting the phone number and the reviews; the service side adds the open complaints, the outstanding remedies and who now answers the customers the site used to know.

A group of nail bars sets one standard (illustrative)

Illustrative example — not a real result

Hegreix Nail Bars writes one standard for four sites

Hegreix Nail Bars, an invented group of four nail bars, takes about 1,100 bookings a week. A central team of 3 answers the group's shared inbox and listings, and each bar's manager handles complaints on the day. For the last quarter the complaints log holds 38 entries, 26 of them from the oldest bar. The owner's first reading is that the oldest bar has a service problem.

A check changes that reading. The central team asks each bar's staff about 40 recent counter and phone contacts and checks them against the log, and finds 23 complaints with no entry at the other three bars and 4 at the oldest. The oldest bar writes its complaints down far more than the others do. The same check shows that a chipped finish raised within the same week ended in a free redo at one bar, half the price back at another and a refusal at a third, and a customer who uses two bars has noticed.

The group makes six changes. It adopts one reason list and one log, and a rule that a complaint is logged at the bar on the day it is made. It writes a remedy table with a free redo within 7 days for a chipped finish and a £15 allowance that any member of staff can use without asking, with approval above that from the area manager within 1 working day and a named cover. It builds one library of 22 saved replies, each with an owner, and a site card for each bar holding its address, hours and phone number from the master record. It gives each manager a sheet of local answers with a review date. It scores 12 conversations per bar each week on one 6-line card, by a reviewer from outside that bar, and the reviewers calibrate together on 6 conversations drawn from all the bars. And it reports by bar and by reason, with counts beside every rate and each bar against its own history, and sets no target for fewer logged complaints.

By the end of the next quarter the log holds 65 entries, 30 of them from the oldest bar and between 11 and 12 from each of the others. The owner reads the rise as recording, not as worse service. On the reason "booking changed", repeat contacts fall from 9 of 50 to 5 of 46 once the confirmation reply is corrected, which the owner treats as a pointer, not as proof, because the counts are small. One bar asks in writing to keep a late Saturday slot; it is entered in the master record, approved centrally and put on the variations list with an end date.

Common mistakes

  • Letting each site keep its own replies and remedies. Copies drift apart, and the same failure then gets a different answer at each site.
  • Ranking sites by a complaint rate. On small counts the ranking measures noise and recording habits, not service.
  • Setting a site target for fewer logged complaints. It rewards hiding them, and the honest site looks worst.
  • Counting only what reaches the help desk. The site phone and the counter are where contacts can disappear, and a quiet log can mean a site that records little.
  • Sending every decision to the centre. A customer waiting at a counter for approval has been given no remedy, and staff who are refused stop asking.
  • Leaving the approver out of the cover plan. The route above the allowance closes on the days the one person who holds it is away.
  • Hours and numbers that differ between the door, the page and the listing. Customers turn up or ring and find a promise that was not kept.
  • Reviewers who score their own site. The review then sits with the side being judged, which is what measurement is meant to avoid.
  • Granting a variation with no reason, owner or end date. It can become a second standard that nobody removes.
  • A policy change that reaches the sites last. Staff learn it from customers, and each site then answers it differently.

For the single-site guides this one builds on, start from the service and support hub.

Frequently asked questions

Should each site write its own replies and set its own remedies?

No. Tone, saved replies and the remedy table belong to the centre so that the same failure gets the same answer at every site. What a site writes is the local fact, such as what is on the shelf and who is on duty, while its address and hours come from the master record. Sites can propose changes to the shared documents, and the owner at the centre decides.

Who decides a refund or a goodwill gesture at a site?

Site staff, up to the written allowance, without asking anyone. Above it, a named approver at the centre or in the area decides through a route that has a promised answer time and cover for absences. A safety issue, a legal threat or a customer in difficult circumstances goes up whatever the amount, as the remedy table tutorial sets out for any business, and a complaint about the site manager is decided above that manager.

How should service be compared between sites?

Each site against its own history first, by contact reason and with the counts behind every rate shown. A ranking of sites by a complaint rate reflects how many contacts each site has and how well each one records them, so it can mislead about service. Read unusual movement against the site's own range, and check that every site logs what it hears before anyone reads a difference as a difference in service.

Terms used on this page

Frameworks

Sources

  1. Regulation (EU) 2016/679 (GDPR) — EUR-Lex
  2. Competition and Markets Authority — GOV.UK

Related