What changes when someone else answers your customers
A customer who writes in or calls does not see an organisation chart. They see one business, and whatever the person answering says, promises or gets wrong is something that business said, promised or got wrong. Handing first-line support to an outside team changes who types the reply, not whose name is on it or whose customer leaves when the answer is poor.
The site starts from caution. The comparison of in-house teams and agencies, written for marketing work, puts continuous work that depends on knowing the business on the in-house side, because the effort of briefing outsiders on that kind of work can outweigh whatever extra skill they bring. The social media strategy hub goes further for one channel: where an agency or a freelancer helps, the brand holds on to the owner role and the inbox, since its voice and its exchanges with customers are difficult to pass to outsiders and quick to be harmed. Customer service is continuous and runs on knowledge of products, policies and past cases. This guide takes that caution as its starting point and makes no case that outsourcing is the better choice. Its question is narrower: once a business uses an outside team, how does it keep the service its customers receive?
Four things change. Knowledge that lived in agents' heads has to be written down, because the outside team will not overhear it. Authority that was used informally, such as a manager nodding through a refund, has to be defined. Customer data has to be scoped, because a second organisation now holds access to it. And the measures that judge the service have to be read by someone other than the partner. Every gap the business leaves is filled by the partner's best guess, and every guess reaches a customer. Since the comparison and the other agency pages describe marketing agencies, this guide applies their principles to service by analogy and says so where it does.
What to keep in-house and what to hand over
The comparison's rule for any hybrid is to keep the brain of the work inside the business: strategy, the brand, customer data and the measures that judge performance, with measurement held by the side whose work is not being judged. For service, the brain is the set of promises the business makes to customers and the means of checking they are kept. What travels is the answering: questions with a documented answer, in the channels and hours agreed, given in the business's own words.
Write the split down as ownership. A RACI matrix works here as for any shared piece of work: one row for each decision, such as answering a delivery question, approving a refund above the allowance, changing a saved reply or closing a complaint, with the roles in the business and at the partner across the top. The framework's central rule matters above all at the join between two organisations: each row carries exactly one accountable role. A row with none is a question nobody answers, and a row with one on each side is an argument the customer waits through.
| Area | Stays with the business | Can go to the outside team | Why the line sits there |
|---|---|---|---|
| Service standards and policies | Setting and changing them | Working to them | The side judged against a promise should not write it |
| Tone guide and saved replies | Writing, owning and approving changes | Using them and proposing changes | One voice and one current source of facts |
| First-line answers | Questions with no documented answer yet | Agreed questions, channels and hours | A written answer travels; judgement about an unusual case does not yet |
| Remedies | The table, the allowance and approvals above it | Standard remedies and the allowance as written | It is the business's money and its precedent |
| Complaints | Investigation and the decision | Recognising, logging and passing on | The procedure names who decides |
| Customers in difficult circumstances | Named people who can adapt the process | Recognising the signs, making the adaptations agents are allowed and passing cases on promptly | These cases need authority as well as care |
| The social inbox | The business's own community owner | Only cases handed over in private | A public reply is the brand speaking in front of everyone |
| Reason list and quality review | Definitions, scoring and calibration | Tagging contacts and joining calibration | Measurement sits with the side not being judged |
| Customer data and accounts | Ownership and access decisions | The access the work needs, by role | The business answers for the data |
The table is a starting split, not a rule. A business with a long-standing partner may hand over more, and one new to the arrangement may keep more back. What should not move is the reasoning in the last column.
Choosing a partner on how it will treat your customers
The agency selection and briefing guide is written for marketing agencies, and nothing on this site evaluates outsourcing firms, their prices or where they operate. What follows borrows that guide's approach by analogy and points it at the one question a service partner has to answer well: how will it treat the business's customers?
Begin, as that guide does, by writing down the work: the channels and questions, the hours, what stays in-house, the documents the partner would work from and how its work would be judged. That note is the brief every candidate receives. Then test what matters. Give each candidate the same real past contacts, with anything that identifies the customer removed, together with the tone guide and the saved replies, and ask for the replies they would send. Score them on the business's own quality scorecard against criteria agreed before anyone reads the answers, with someone from the support team among the scorers.
Meet the people who would answer customers, not only the people selling the service, as the agency guide advises for the team that will do the work. Ask how a new agent learns a client's products and policies, how a changed saved reply reaches every agent, and how the partner reports on quality. A partner that talks only about speed is describing the measures it controls; one that asks for the business's scorecard, reason list and escalation route is describing the arrangement this guide builds. The scope deserves the care the agency guide gives it: the services, what is out of scope, what the business itself must supply and the measures the work is judged by. The contract, its pricing, its data processing terms and any employment questions belong with the business's legal and data protection advisers, and this guide states no clause.
The pack the outside team works from
The outside team should work from the business's own documents, not from a rewritten version of them. A partner that turns a tone guide into scripts of its own creates a second set of documents that stops matching the first the day anything changes. Hand over the originals, give the partner read access where they live, and keep each one's owner inside the business.
The pack starts with the voice. The tone guidelines tutorial builds a support tone guide from real replies, starting from the Brand VoiceThe consistent personality a brand expresses in its words across channels, with tone adjusting to the situation and the audience. and setting the tone for each recurring situation, from bad news to an angry customer. It is the document to hand over first, because the partner's agents have never heard the business speak. The saved replies tutorial gives every Saved ReplyA pre-written answer a support agent inserts and then edits for the customer in front of them, keeping facts and tone consistent across the team. an owner and a review date and ties the library to policy and product changes, which is what keeps an outside team's answers current. The channels and self-service guide supplies the standard for each channel, a promise written per channel that the business can keep. Campaigns put an outside team on the spot, so put the partner on the list for every brief the campaign briefing tutorial writes, at the same moment as the business's own staff. An outside agent who learns about a sale from a customer is guessing at its terms.
Write the commitments between the two sides as a SLAA published promise between teams, or with a supplier, about what each type of request needs and how quickly it will be handled, agreed rather than imposed. that runs both ways. The partner commits to answering to the business's standards. The business commits to keeping the pack current, telling the partner about changes and campaigns before customers meet them, and answering escalations as fast as its route promises. Set the levels from the business's own records and agree them with the partner, because a level one side imposes is a level the other side plans around rather than meets.
| Document | Owner in the business | What the outside team does with it | How changes reach the outside team |
|---|---|---|---|
| Tone guidelines | Support lead | Writes every reply in it | The updated original, with examples of what changed |
| Saved replies | Each reply's named owner | Uses and completes them; flags any that no longer fit | Changed before the policy or product change goes live |
| Remedy table and allowance | Owner of remedies | Offers the standard remedy and the allowance | A dated new version, never a spoken change |
| Complaints procedure | Complaints owner | Recognises, logs and passes on complaints | The updated procedure, with the log itself unchanged |
| Campaign briefs | Campaign owner | Answers campaign questions from the brief | Every brief, at the same time as in-house staff |
| Reason list | Owner of the list | Tags every contact with it | A new version with the date it takes effect |
Authority, remedies and escalation
An outside agent with no authority makes customers wait, and one with unlimited authority spends the business's money by their own lights. The remedies and goodwill tutorial settles this for the business's own staff with a remedy table for common failures, a goodwill allowance agents can spend at their own discretion, levels of approval for anything larger and a quick route to whoever approves. The same table serves an outside team. Decide whether the partner's agents hold the same allowance, a narrower one or none, write the answer into the pack, and keep the rights column and the goodwill column apart as the tutorial does, so no agent presents something a customer is entitled to as a favour. The partner works from the current, dated version of the remedy tableThe written list of standard remedies for common failures, keeping rights apart from goodwill, with an allowance staff use unasked and approval levels above., and each change reaches it as a new version rather than a spoken instruction.
Everything above the allowance travels along an Escalation RouteA short written route naming who front-line staff contact, how and how fast, when a problem is beyond what they can decide alone. that crosses from one organisation to the other: what sends a case up, the named person in the business who receives it, how the partner reaches them, how quickly they promise to answer and who covers when they are away. Staff it for every hour the partner's channels are open. A route that closes when the business's office does leaves the partner's evening agents to make the customer wait until morning or to decide something they were never allowed to decide.
Complaints stay in one place. The tutorial on writing a complaints procedure feeds every channel into one log and names who investigates and who decides each type of complaint. The partner logs complaints in the business's log, and the decision stays with the business. When a complaint is about the way the partner itself handled a customer, the procedure's principle applies with extra force: whoever caused the problem can supply the facts but does not decide the outcome.
Customers in difficult circumstances need people with authority. The guide to supporting customers in vulnerable circumstances asks for a named and quick route to people who can adapt the process, staffed whenever the channels are open, and for a need to be recorded only with the customer's agreement. Give the partner's agents the signs, the adaptations they may make themselves and the route, and make passing a case on easy and free of any penalty.
Public conversations stay with the business. The community management guide has the community manager acknowledge a complaint in public and hand it to customer service to resolve in private, and logs a complaint made on social in the same place as any other. Where the outside team is that customer service, agree the handover in both directions and leave the public reply with the business's own community owner.
Customer data and access
The partner's agents will see Personal DataAny information relating to an identified or identifiable living person, such as a name, email address, location data or an online identifier.: names, addresses, orders and sometimes notes about what a customer needs. The site's data guides, the vulnerable circumstances guide among them, record that data minimisation is one of the GDPR's principles: the personal data a team uses should be no more than its purpose requires. For an outside team, that means access to the records its agreed questions require and nothing more: an agent answering delivery and warranty questions needs order and warranty records, not marketing lists, exports or notes from complaints they will never handle.
The tutorial on reviewing access to marketing tools sets tests that suit a support system as well as any marketing tool: every person signs in as themselves rather than through a shared login, each holds only the access their work needs, administrator rights sit with few people, and someone inside the business holds administrator access. It also lists agencies and freelancers keeping access after their work ended among the ways access drifts. Partner agents join and leave on the partner's timetable, so agree how the partner reports every leaver and include its accounts in every access review. Keep the accounts in the business's name where it can, as the agency pages advise for marketing accounts.
The partner's legal role in handling the data, the data processing terms in the contract, any transfer of data to other countries and employment matters go to whoever owns data protection in the business and to qualified advisers.
Judging the work with measures the business keeps
Goodhart's law is the warning to read before any report from a partner: once a measure becomes a target, with fees or reviews hanging on it, effort goes wherever the number moves for the least cost, and the number stops tracking the outcome it was chosen for. An outside team judged on reply speed alone can meet any speed standard with quick replies that solve nothing.
The guide to customer service metrics pairs each service measure with a second one that shows when the first is being gamed: time to first reply is read with repeat contactsA customer contacting the business again about the same problem, the clearest sign that the first answer did not end the customer's work., split by reason, and time to resolution with contacts that were reopened. It also keeps the definitions away from whoever is judged by the numbers. For time to first replyThe time from a customer's first message to the first reply from a person; read beside repeat contacts, as a quick reply that solves nothing still scores well., that means the business, not the partner, sets the clock rules, including what counts as a reply and whether pending statuses pause it. Read beside the comparison's rule that measurement belongs with the side not being judged, that settles who reports on the partner: the business, from its own records, on definitions it sets. The partner's own reports are useful for running its team and for starting a conversation; they are not the verdict.
Quality needs reading as well as counting. The quality review tutorial has reviewers read chosen conversations in full and score them on a short card built from the business's own standards, adds every complaint and escalation, and has reviewers score the same conversations separately to check they agree. Use one scorecard for in-house and partner conversations alike, with reviewers from the business, and bring the partner's team leads into that calibration. When a pattern appears, send it to the owner of its cause, which may be a document the business wrote rather than anything the partner's agents did.
The partner tags contacts with the business's own list. The contact reason tutorial checks a list by having a second person tag a sample of contacts without seeing the first tag and comparing the two. Let that second person come from the business, and treat the agreement as a test of the list's definitions rather than as a score for the partner's agents.
Reviews, feedback and changing the arrangement
Review the arrangement on a rhythm both sides know, not only at renewal. The agency guide's two-way scorecard, in which the agency also scores the client on its briefs, feedback, approvals and access to information, suits a service partner well. Let the partner score the business on how current the pack was, how early it heard about changes and campaigns, and how fast escalations were answered, because some faults that look like partner errors begin with a stale saved reply or a late brief.
The partner's agents hear customers first, so agree how they report a question with no documented answer or a policy customers keep misreading: through the reason list, to a named contact, with a record of what changed as a result. Change the split one kind of work at a time, moving a new type of question to the partner only once its answer is written down and has held up in the business's own quality review, and record each change in the scope and the RACI.
Plan for the end from the start. An arrangement built on the business's own documents makes it easier for knowledge to come back, because the pack stays when the partner goes. The agency offboarding checklist, written for marketing agencies, applies by analogy: it begins on the day notice is given, collects what the business needs before access ends, removes users and rotates shared passwords near the end, and closes with a handover note. For a service partner, add the open cases, complaints in progress and customers waiting for a call back.
A dehumidifier maker hands over its first-line support (illustrative)
Zanfuroth Dehumidifiers hands its first-line support to an outside team
Zanfuroth Dehumidifiers, an invented maker of home dehumidifiers that sells online, has 7 support staff answering about 2,400 email and phone contacts a month. It hands first-line email and phone support to an outside team and keeps 3 of its own staff as the second line. Complaints, refunds above a £60 allowance and customers in difficult circumstances stay with them, and so do the social inbox, the reason list and the weekly quality review.
The partner receives the business's own tone guide, its 46 saved replies with their owners and review dates, the remedy table and an escalation route to a named team lead, with cover, staffed from 8am to 8pm to match the partner's phone hours. Partner agents sign in with their own accounts and see only order and warranty records. Each week a Zanfuroth reviewer scores 40 partner conversations and 15 in-house ones on the same 6-line scorecard.
At the first quarterly review the partner's report shows 97% of emails answered within the 8-hour standard. The business's report sets reply times beside repeat contacts: on the reason "Filter and cleaning", 21% of customers got in touch again within 7 days, against 9% before the handover. The quality review has traced the cause to one of the business's own saved replies, which links to the cleaning article for an older model. It has also found 13 returns refused in error, because the partner had read the returns rule for opened units as excluding any unit taken out of its box.
Both fixes go into the business's own documents: the saved reply is rewritten by its owner, and the returns rule is restated in the remedy table with an example. The partner scores Zanfuroth in turn and marks it down for announcing a winter promotion 2 days before it started. A month later repeat contacts on filters are down to 10%, and the next campaign brief reaches the partner 3 weeks ahead.
Common mistakes
- Handing over the social inbox with the phones. A public reply is the brand speaking in front of everyone; keep it with the business's own community owner.
- Letting the partner rewrite the documents. Two versions of the tone guide and the replies drift apart, and customers get whichever one an agent opened.
- Briefing once at the start. Policies, products and campaigns change, and a partner that hears late answers from the old version.
- Authority nobody wrote down. Agents with no allowance make customers wait; agents with an unwritten one give inconsistently.
- An escalation route that closes before the phones do. Evening agents are left to make customers wait or to decide alone.
- Judging the partner on its own speed figures. Fast replies that solve nothing come back as repeat contacts, which a speed report does not show.
- Separate scorecards for in-house and outside agents. Two standards cannot be compared, and the business loses sight of the one its customers are actually getting.
- No plan for the end. Documents, open cases and access nobody listed are lost, or left open, on the last day.
The service and support hub places this arrangement beside the channels, standards and recovery work the outside team carries out on the business's behalf.
