Before the first ticket
Explain the customer promise
Begin with what customers believe they are buying: the product, the service and the expectations set by your website and marketing. A support team needs to understand that promise to recognise when something has gone wrong.
Describe your typical customers and the moments that matter in their journey. Keep it specific enough to guide a response, without relying on stereotypes or unnecessary personal data.
Define the work and the limits
List the channels, languages and opening hours in scope. Identify the contact reasons the team should handle independently and the ones it should escalate. Make the decision boundaries explicit for refunds, order changes, goodwill and account access.
For each escalation, name the receiving team and what information they need. “Ask operations” is not a usable handover if no one knows which queue or person owns it.
- What may an agent decide without approval?
- Which actions require a second check?
- Who owns exceptions and how are they reached?
- What should the customer hear while a decision is pending?
Show examples of your voice
A list of adjectives such as friendly, professional and empathetic is a starting point, not a training set. Share real examples of a good answer, an overly formal answer and an answer that was factually correct but unhelpful.
Explain what makes each example work or fail. Include a simple query and a difficult complaint. A brand voice needs to work when the customer is disappointed, not only when everything is going well.
Make knowledge easy to maintain
Identify the authoritative source for each policy and product fact. Record an owner and a review date where the information changes regularly. Make it clear which document takes priority if sources disagree.
Avoid giving a new team a large folder with no structure. A concise index, common scenarios and links to the current policy will usually be more useful than a pile of historic presentations.
Agree how launch will be judged
Set the checks that must pass before the team takes on the full workload. These might include access verification, sample response reviews, escalation exercises and successful handling of a defined pilot queue.
Agree the first review point and who attends. Early conversations should focus on specific examples and decisions, so coaching improves the work rather than becoming a general discussion about whether things feel better.