How to hand over
customer support
Support is the only handover where a mistake reaches a customer under your name. That is not a reason to keep it — it is a reason to build the answer library before the first ticket.
Support is usually the loudest pain in a growing business, which makes it the instinctive first thing to delegate. It is also the one place where an inexperienced answer is visible to the outside world, in writing, sometimes permanently in a review.
The businesses that delegate support successfully all do the same thing first, and it is not hiring carefully. They write the answers down — the twenty most common questions, the exact wording, the policy in plain language, the thresholds, and what gets escalated.
That document is the handover. With it, support is straightforward and fast. Without it, you get either an escalation queue that saves you nothing or invented answers that cost you reviews.
Who this is for
✓Worth your time if
- Tickets are answered in the evening, after everything else
- Response times are measured in days
- The same twenty questions arrive every week
- Reviews mention slow replies
✕Probably not if
- Your product requires deep technical diagnosis on every ticket
- You have no written policies on returns, refunds or delivery
- You are unwilling to review the first week of responses
- You want someone to own the brand voice from day one
What support actually covers
Ordered by how safely each part travels. The library comes before all of it.
Email, chat and social messages answered inside a service level you set, to your macro library and tone.
Chased with the courier or your system and answered with facts rather than an apology and a guess.
Processed to your written policy, labels issued, refunds prepared for approval where above your threshold, and the reason captured.
Every review answered — the routine ones from your templates, anything serious routed to you.
Documentation assembled and submitted inside the window, which most businesses never do.
New questions added as answers, so the library gets better instead of stale and the same question is never answered two ways.
Recognising the ticket that is not routine and routing it immediately rather than attempting it.
Volume, first response time, top reasons and return causes weekly — because support data is product and operations data.
What stays with you
Answering to policy travels. Setting policy, and anything that could escalate beyond a normal complaint, does not.
- Policy changesThey apply your returns, delivery and goodwill policy. Changing it is yours.
- Refunds above thresholdSet a value; above it, refunds come to you for approval. Below it, let them resolve without asking.
- Safety, injury and legal complaintsProduct safety, injury, discrimination or legal threats are escalated immediately and never answered from a template.
- Public statementsAnything beyond routine review response goes to you.
- Angry escalation to the ownerWhen a customer asks for the owner, they get the owner. That should be a written rule.
The order to set it up
Four of these five steps happen before a single ticket is answered.
Export your last hundred tickets and count the questions
You will find roughly twenty questions account for most of the volume. This takes an hour and it tells you exactly what the library needs to contain.
Write the answers, in your voice
The actual wording, not a summary. This is the artefact that makes the handover work, and it is worth having even if you never hire — because right now those answers are inconsistent.
Set thresholds and escalation rules in writing
Refund value threshold, what gets escalated immediately, what to do when they are unsure. Make escalating the expected answer rather than a failure.
Week one: they draft, you send
Every response reviewed before it goes out. Slow, and it is the fastest way to transfer tone. The corrections are the training.
Week two onward: they send, you spot-check
Move to reviewing a sample plus everything flagged. Keep the weekly report — first response time and top reasons are the numbers that matter.
No answer library, so every reply is invented
This is the whole of it. Without a written library the person has two options on any question they have not seen: escalate, or work it out. Escalating everything means you have hired someone to forward you email. Working it out means a plausible, well-meaning, slightly wrong answer goes to a customer under your brand — about delivery times, about your returns policy, about whether something is covered. You find out in a review, or when a customer holds you to an answer you would not have given. The fix costs an afternoon and it is not about the hire at all: your existing staff are also guessing, just less visibly. Write the twenty answers down first.