--- title: "AI Trainer Examples: What to Build for Each Type" url: "https://help.outdoo.ai/en/article/ai-tutor-examples-what-to-build-for-each-type" language: "en" last_updated: "2026-10-23T02:20:07.649Z" --- # AI Trainer Examples: What to Build for Each Type Example AI Trainers for each trainer type, with what to upload, what to tell the trainer and what your team gets from it. Choosing a trainer type is easier with an example in front of you. This article gives you two worked examples for each type, one for a B2B team and one for a B2C team, with the resource to attach and the instructions to write. For what a trainer is, see [Intro to AI Trainer](https://help.outdoo.ai/en/article/intro-to-ai-tutor). For the mechanics of building one, see [Create and manage an AI Trainer](https://help.outdoo.ai/en/article/create-and-manage-an-ai-tutor). ## Picking the type The three types map to three different questions your team might be stuck on. | If the learner needs to... | Use | Example | | --- | --- | --- | | Understand something before they can use it | **Concept** | A qualification framework, a plan structure, a compliance rule | | Do something better | **Skill** | A discovery call, a negotiation, a difficult conversation | | Operate a specific system | **Tool** | Your CRM, your ticketing system, an AI assistant | If you are unsure between Concept and Skill, ask whether the learner would fail because they do not know the material or because they cannot yet perform. Not knowing is Concept. Not performing is Skill. ## Concept trainer examples A Concept trainer teaches understanding. It answers questions, corrects wrong answers, and asks the learner to explain the material back in their own words. ### B2B: understanding a qualification framework **Title.** Understanding MEDDIC qualification **Resource.** Your own qualification guide, or the framework document your team already coaches to. **Roleplay Instructions.** Ask the learner to explain each letter and to say what a weak answer looks like next to a strong one. Have the trainer pick a deal apart and ask which letter is missing. Why this works as a Concept trainer: the failure it prevents is a seller who fills in a qualification field without understanding what a real answer looks like. That is a knowledge gap, not a performance gap. ### B2C: understanding a plan or product structure **Title.** Understanding a health plan: deductible, copay and coinsurance **Resource.** Your plan summary or product documentation. **Roleplay Instructions.** Have the learner explain each term in one plain sentence, then walk the arithmetic in the order the plan applies it. Why this works: almost every escalated billing call comes down to two terms that sound alike and behave differently. A trainer can drill that distinction in ten minutes, and no amount of roleplay practice fixes it if the learner does not know the difference. ## Skill trainer examples A Skill trainer teaches applied practice. The trainer takes a part in the conversation, pushes back, and tells the learner what to do differently. ### B2B: running a discovery call **Title.** Running a discovery call with an enterprise prospect **Resource.** Your discovery guide, or a call framework document. **Roleplay Instructions.** Tell the learner what a good discovery call has to produce, then let the trainer play a committee buyer. Name the specific behaviours to hold them to, for example keeping their talk ratio down and asking how a purchase gets approved. ### B2C: handling a difficult conversation **Title.** De-escalating a billing complaint **Resource.** Your escalation policy plus your de-escalation guidance. **Roleplay Instructions.** Have the trainer play an annoyed customer. Ask the learner to acknowledge the surprise before explaining the charge, and to say plainly what they can and cannot do. A Skill trainer is not a replacement for a roleplay agent. The trainer teaches the play and explains why it works. The roleplay agent then tests whether it stuck under pressure, and a scorecard measures the result. Building both, in that order, is the pattern that works. ## Tool trainer examples A Tool trainer teaches a specific application. It can share its screen during the session, so it can point at what it is describing rather than describing it in the abstract. Tool is available on request. Click **Contact Support** on the Tool option in the editor to have it enabled for your workspace. ### B2B: your CRM **Title.** Salesforce: creating and modifying a lead **Resource.** A process document covering the fields your team must fill in, written against your own configuration. **Roleplay Instructions.** Walk the learner through creating a record, editing it and converting it. Be strict about the steps that are hard to undo. ### B2C: your ticketing system **Title.** Zendesk: creating and resolving a support ticket **Resource.** Your ticket handling guide. **Roleplay Instructions.** Focus on the mistakes with real consequences, for example the difference between a public reply and an internal note, and what each status means. ## Writing the resource The trainer answers from what you attach, so the resource decides the quality of the session. A few things that make a difference: - **Attach the source material, not a summary of it.** A trainer built on a two-line summary has two lines to teach from. - **Write it against your own configuration.** Page layouts, required fields and picklist values differ between organisations. A Tool trainer will confidently assert whatever your document says, so mark anything that is specific to your setup and check it before you roll the trainer out. - **Only document formats can be attached.** PDF, DOC, DOCX, PPT and PPTX. Convert anything else first. - **More than one resource is allowed.** Attaching a slide deck alongside a written explainer works well, because the deck carries the claims and the explainer carries the reasoning. ## Writing the instructions Roleplay Instructions is up to 500 characters and is shown to the learner just before the session starts. The instructions that work name the specific behaviour you want rather than describing the topic again. Less useful: "This session covers discovery calls." More useful: "Before you ask me for a meeting, ask how training happens today and who else would need to be in the room." Hope this article was helpful. For any queries, please write to support@outdoo.ai ## Related articles - [Intro to AI Trainer](https://help.outdoo.ai/en/article/intro-to-ai-tutor) - [Create and manage an AI Trainer](https://help.outdoo.ai/en/article/create-and-manage-an-ai-tutor) - [Managing Resources](https://help.outdoo.ai/en/article/managing-resources) - [Roleplay Resources](https://help.outdoo.ai/en/article/roleplay-resources)