Brief the assistant with policy
Paste the relevant policy extract and the de-identified ticket, and tell the tool to use nothing else.
AI training for customer support teams teaches agents to draft replies, summarise tickets and adjust tone with an AI assistant, while keeping customer data out of the wrong tools and checking every promise against policy. Tosheo.ai is being built to teach this through short role-specific lessons and graded practice.
Planned launch trial: 7 days, card required, up to 5 seats.
You will continue on the Tosheo.ai app to create your account and review the trial terms.
Paste the relevant policy extract and the de-identified ticket, and tell the tool to use nothing else.
Produce a first reply that answers the question asked and makes no promise the policy does not support.
State the customer's request, what has been tried and what remains open, in a form the next agent can act on.
Make a response warmer or firmer while keeping every factual statement intact.
Remove personal and payment details before prompting and use only approved tools and plans.
Compare the draft with the policy, correct it and explain each change you made.
Brightwell Home is fictional. Its policy: returns within 30 days if unused; faulty items covered by a 12-month warranty claim that needs an order number and a photo; the warranty team replies within two working days. A customer's kettle stopped heating 40 days after purchase and they want a refund today. Use an AI tool to draft a reply using only this policy, then edit it. Submit the final reply and a short note on what you changed in the AI draft and why.
The reply routes the customer to the warranty correctly and makes no offer the policy does not allow.
The customer knows exactly what to send and what happens next, in plain words.
The reply acknowledges the problem without excess apology, and the note explains the changes made to the AI draft.
It covers the parts of a support agent's day where a general AI assistant can help and the checks that keep that help safe. Drafting a first reply, summarising a long ticket thread for a handover, rewriting a blunt answer in a calmer tone and turning a policy page into a plain explanation are the common starting points. Each one is useful only if the agent checks the result against the actual policy and the actual ticket.
Customer service AI training is therefore less about prompts and more about judgement. The agent has to know what the assistant cannot know: the customer's order history, the exception a team lead approved yesterday, the refund limit that changed last month. Good training makes that boundary a habit, so the assistant drafts and the agent decides.
Turn the ticket and the relevant policy extract into a first reply, then edit for accuracy and tone.
Condense a long exchange into what the customer wants, what has been tried and what is still open.
Rewrite a correct but cold answer so it acknowledges the problem without making new promises.
Explain a returns or warranty rule in plain words without changing what it says.
Recognise which customer details must never go into an unapproved tool.
It is about support agents using AI assistants in their own work, not about buying or configuring a customer-facing chatbot. A chatbot that answers customers directly is a software purchase with its own setup, testing and vendor training. That is a different decision, usually owned by whoever runs your helpdesk platform.
Most small support teams meet AI first through ChatGPT, Claude, Gemini or Copilot on an agent's screen, often before anyone has written a rule about it. That is the gap this training addresses. If you want the wider picture of how AI shows up in customer service work, the role guide on AI in customer service covers it; this page is about training the team.
A good reply is accurate to policy, specific to the ticket and promises nothing the agent cannot deliver. Here is a worked example from a fictional online homeware shop, Brightwell Home. The supplied facts are: returns are accepted within 30 days if the item is unused; faulty items are covered by a 12-month warranty claim, which needs the order number and a photo of the fault; the warranty team replies within two working days.
The ticket: a customer bought a kettle 40 days ago, it has stopped heating, and they want their money back today. The agent's prompt reads: "Draft a reply to this customer. Use only the policy below. Do not offer anything the policy does not allow. Ask for any information we need. Keep it under 120 words." The policy extract and the ticket text are pasted below the instruction, with the customer's name and address removed.
A weak draft, typical of an unguided first attempt, says: "We're so sorry! We'll process a full refund and send a free replacement right away." It sounds kind and it is wrong twice: the 30-day return window has passed, and nothing in the policy offers both a refund and a replacement. Sent as written, it creates a promise the business has to honour or retract.
The reviewed version says: "I'm sorry the kettle has stopped heating. As it's 40 days since purchase, this falls under our 12-month warranty rather than a standard return. Please reply with your order number and a photo showing the fault, and our warranty team will come back to you within two working days." Every statement can be traced to the supplied policy. The agent then notes what they changed and why, which is exactly the habit the planned rubric checks.
Agents should not paste payment card details, passwords, account security answers, health information, or another customer's details into any AI tool, and should paste personal data only into a tool and plan the company has approved. The safest default is to strip names, addresses, emails, order numbers and phone numbers before asking for a draft; the assistant rarely needs them to write a good reply.
Vendor terms differ by product and plan, so the rule has to come from the company, not from the agent's guess. As one example, Anthropic's privacy centre states that by default it does not use inputs or outputs from its commercial products for model training, with an exception where users submit feedback or otherwise allow it. Consumer accounts and other vendors can work differently. Check the current terms for the exact plan your team uses.
In the UK, the ICO's guidance on AI and data protection sets out how data protection principles such as data minimisation, security and accuracy apply when AI processes personal data. The ICO notes that the guidance is under review. This page is general information, not legal advice; ask whoever owns data protection in your business how it applies to your helpdesk.
A manager signs up, selects Support as a role, picks the AI tools the team already uses and invites each agent. The steps below describe the planned flow. Tosheo.ai is pre-build. Everything described here is planned launch scope, not a record of customer training, assessment results or outcomes.
Each agent rates themselves and completes a few short practical tasks, so an experienced agent and a new starter begin at different points.
Each 10 to 15 minute lesson gives a brief explanation, a worked support example and a hands-on task in a real AI tool.
Submitted replies are graded by AI against a visible rubric with specific feedback. An agent who disagrees can flag the score for review.
Role-plays such as an escalated complaint or a request outside policy, scored against a rubric the agent can read before starting.
The team lead sees skill progress and completion, never the agent's raw chat logs. A weekly digest and nudges cover inactive learners.
A final practical assessment leads to a recognised certificate with a verifiable URL and a LinkedIn share.
A sensible first month moves from low-risk drafting to live tickets only after the checks are routine. This is a rollout suggestion, not a measured result.
Diagnostic, then practise reply drafting on fictional tickets. Agree the data rule in writing: what may be pasted, into which tool.
Thread summaries and handover notes. The team lead reviews three summaries per agent against the original thread.
Tone repair and policy explanations, including one scenario where the customer asks for something the policy does not allow.
Agents use AI on real, low-risk tickets with the reviewed draft and the original side by side. Decide what stays manual.
Nobody can say with confidence, and this page does not try to predict it. What is clear today is that the hard parts of support work, deciding when to make an exception, noticing that a polite customer is about to leave, knowing that the policy page is out of date, are exactly the parts an assistant cannot do without context it does not have.
Training aimed at those judgements is useful whatever happens to the tooling. An agent who can brief an assistant precisely and catch its mistakes is valuable on a team that adds a chatbot, and on one that never does.
It is not the right choice if what you need is admin training for a specific helpdesk platform's built-in AI features; the vendor's own training will be more precise. It is not suitable if your agents need lessons in a language other than English, because lessons are English only at launch.
It is also not built for large contact centres that need SSO, LMS integrations or enterprise contracts before purchase; none of those are included at launch. And because the product is pre-build, a team that needs training running this week should start with the free guides on this site and a written data rule.
Yes, for drafting, provided an agent checks every draft against policy before sending, customer personal data is removed or only used in a tool your company has approved, and the reply makes no promise the business has not agreed to. Treat the output as a draft, not an answer.
For agents drafting their own replies, the best tool is usually the one your company already pays for and has approved, such as ChatGPT, Claude, Gemini or Copilot. A customer-facing chatbot is a separate software purchase, and the right one depends on your helpdesk platform.
Do not share payment card details, passwords, security answers, health information or other customers' details, and only share personal data in a tool and plan your employer has approved. Check your company's AI policy and the vendor's current terms for the plan you use.
Planned lessons take 10 to 15 minutes, so an agent can complete one between queues rather than losing a shift. The diagnostic at the start takes about five minutes.
No. The planned manager view shows skill progress and completion, not raw chat logs. Agents can also flag a grade they disagree with for review.
The planned Team plan is priced per seat per month with a five-seat minimum, and a 7-day trial for up to five seats is planned. Current planned prices and the Growth option are on the pricing page; they are a starting hypothesis and may change before launch.
Explore the planned role-specific lessons, practical tasks and manager view.