Two weeks into the job, a new starter is on a call and also inside the CRM, trying to work out which of two similar status fields the account manager meant. She picks one. Six months later a report is wrong and nobody can say when it started. The training covered the CRM. It covered it in a slide deck, in week one, away from a keyboard.
Tool is the AI Tutor type for the systems your team works in. The tutor can share its screen during the session, so it can point at the field rather than describe it.
Why this matters
Application training is usually delivered in the wrong medium and at the wrong time. A recorded walkthrough teaches the happy path, in order, with no customer waiting. Real system work is none of those things: it happens under time pressure, mid conversation, at the moment the learner has to decide between two options that look alike.
That decision is where the damage is. Most bad CRM data is not carelessness, it is somebody guessing between two plausible fields. A tutor that can show the screen and be asked "which one of these do I use, and what happens if I pick wrong" answers the question in the form it actually arrives in.
This is the same idea as workflow training in Outdoo, where a learner performs a process in the real system while a roleplay is running. A Tool tutor is the step before that: understanding the system well enough to be dropped into it.
What is gated, and why
Tool is available on request rather than by default. The Tool option in the editor carries a Contact Support button, which books time with us to switch it on for your workspace. We gate it because a Tool tutor asserts whatever its resource document says, and a document written against a different configuration of Salesforce or Zendesk will confidently teach a field your team does not have. That conversation is worth ten minutes up front.
Voice Mode is available by default. Chat and video modes are enabled on request in the same way.
How it works
Open Roleplay, then AI Tutor, then Create AI Tutor, and set Type to Tool. Attach a process document written against your own configuration under Resources, and use Roleplay Instructions, up to 500 characters, to name the steps that are hard to undo.
The instructions matter more here than anywhere else, because the interesting parts of a system are the irreversible ones. Converting a lead sets the account and contact names permanently. A public reply on a support ticket emails the customer and an internal note does not. Those are the sentences worth putting in front of a learner before the session starts.
When a session ends it stays on the page, prepares the transcript, and asks for a rating. The session is then saved to Roleplay History with its recording and transcript, so a manager can see where someone hesitated.
What this unlocks
A revenue operations lead who has just changed the lead lifecycle can build a tutor on the new definitions and require it before anyone touches the pipeline again, which is cheaper than correcting the data afterwards.
A support manager onboarding an outsourced team can teach the ticketing system without booking a trainer in another timezone, and can see from the transcripts which part of the status model nobody understood.
An IT trainer rolling out an AI assistant can teach what may and may not be pasted into it, which is the part of that rollout most likely to become an incident.
The bigger picture
Software training is treated as a project with an end date, and then blamed for data quality problems two quarters later.
Most of what gets called carelessness in a CRM is not carelessness. It is somebody who was shown the system once, in week one, choosing between two fields that look alike while a customer waits. That is training debt, and it compounds quietly. By the time it surfaces as a report nobody trusts, the cost of fixing the records is far higher than the cost of teaching the distinction would have been, and the person who made the original guess has usually moved on.
The reason it keeps happening is that the training is harder to change than the software. A new field ships in a Tuesday release; the walkthrough explaining it needs a recording session, a reviewer and a slot in someone's month. When the document is the training, that gap closes, and a system that changes monthly can finally be taught at the same speed.
See it in Action
Tell us what you're working on, whether that's sales calls, support tickets, or leadership coaching, and we'll show you how it fits.
Talk to Sales
