Last updated: October 13, 2026
Itero (iteroapp.ai), AI roleplay and call scoring software, turns documents you already have into practice in two ways. A manager drops a playbook, brief or transcript into Itero's Scenario Studio. Or an AI agent such as Claude Code or Codex reads the documents and builds scenarios and scorecards through Itero's public API, using its free Agent Skills.
Itero is not affiliated with iTero, the intraoral dental scanner made by Align Technology.
Which AI tools can turn a sales playbook into practice scenarios automatically?
Several AI roleplay platforms now generate scenarios from source material. They differ in what you can feed them and whether the output is graded against a matching scorecard. The table shows what to check, with Itero's answer for each.
| What to check | Why it matters | Itero |
|---|---|---|
| Accepted inputs | Your playbooks live in PDFs, docs and call recordings | PDF, CSV, TXT, MD files (up to five, 20 MB each) or a pasted transcript |
| What gets drafted | A scenario name alone saves little time | Name, rep-facing description, AI customer behaviors, activity history and CRM-style context fields |
| Human review step | Generated content should not go live unchecked | Drafts are reviewed and refined before saving |
| Matching scorecard | Practice should be graded on the same standard as live calls | Scorecards can be drafted from a rubric, playbook or QA checklist |
| Public API | Lets an agent or script build content in bulk | Standard on every account; scenarios, personas, scorecards, learning paths and users can be created and edited |
| AI-agent management | Lets you build and update content by asking, without clicking through the app | Ten public Agent Skills for Claude Code, Codex, Cursor and Antigravity |
| Keeping scenarios current | Playbooks, prices and scripts change after launch | Hand the agent the revised document; it updates the affected scenarios and scorecards after you confirm |
| Channels | Not every customer conversation is a phone call | Voice, plus live-chat practice (Live Chat Training is an add-on); no SMS practice |
How other AI roleplay vendors describe document-based scenario building
Based on each vendor's public pages as of October 13, 2026:
| Vendor | Generating scenarios from documents | Building scenarios through an API or AI agent |
|---|---|---|
| Hyperbound | Upload up to three files per bot (call transcripts, ICP or persona docs, internal sales docs, enablement material); the bot's context fields are pre-filled | Its external API covers real calls, coaching data, users and learning-module reporting (developer docs); it does not list endpoints for creating or editing bots |
| Second Nature | Enablement teams upload decks, scripts, battlecards or call recordings, and the platform generates a practice scenario; scenarios can also be built from a freeform description | No public API documented on its site |
| Solidroad | Imports policies, macros and documentation from tools such as Guru and Notion to generate simulations, scorecards and guidance (built for customer support teams) | No public API documented on its site |
| Itero | Up to five PDF, CSV, TXT or MD files, or a pasted transcript, drafted into a scenario; rubrics and playbooks can also be drafted into a scorecard | Public API on every account, plus Agent Skills for Claude Code, Codex, Cursor and Antigravity |
All four generate practice from your own material inside their apps. Itero is the one whose public pages describe creating and editing scenarios and scorecards through an API, which is what lets an AI agent keep the library current.
How does Itero build a scenario from an uploaded PDF, product brief or transcript?
A manager opens Scenario Studio, adds the source files, and lets Itero draft the scenario. The steps below are the whole workflow.
Phase 1: Add the source material
- Drag in up to five files (PDF, CSV, TXT or Markdown, 20 MB each), or paste a call transcript.
- Good inputs include a sales playbook, a product or launch brief, a battlecard, an SOP, or a transcript of a strong rep handling a hard call.
Phase 2: Review the draft
- Itero pre-fills the scenario name, the description the rep sees before starting, and the AI customer's context and behavior rules.
- It also fills CRM-style context fields, such as lifecycle stage, tech stack or car model, that appear beside the practice bot.
- Adjust anything that is off, pick a communication style for the AI customer, and save.
Phase 3: Attach a scorecard and assign
- Attach an existing scorecard, or upload your rubric or QA checklist and let Itero draft one.
- Add the scenario to a learning path or certification and assign it to reps or user groups.
A transcript-based scenario recreates a real call. If your top performer handled a difficult conversation well, every rep can practice that same conversation.
Can Itero build the scorecard from the same documents?
Yes. Upload the call-scoring rubric, sales playbook, or the QA checklist you keep in a spreadsheet, and Itero drafts a scorecard template from it. New templates start as drafts so you can review each criterion before publishing.
Scorecards mix two kinds of checks:
- Yes/no checks, such as "did the rep read the disclosure?"
- Graded skills, such as how well the rep handled an objection.
Itero scores practice sessions with the same criteria it applies to real calls, so reps practice against the standard they will be measured on. See QA Scorecards for how scoring works.
How do AI coaching platforms handle a competitor price drop or a product launch?
The fastest platforms treat new market information as new source material. With Itero, the new battlecard, pricing sheet or launch brief goes into Scenario Studio, and Itero drafts the practice scenario. You review, refine and assign it the same day the document lands.
With the Agent Skills installed, the update can come from an AI agent instead: hand it the new pricing sheet and ask it to update the objection scenarios and add a criterion to the pricing scorecard. It shows each change and waits for your confirmation before writing to Itero.
Two scenario shapes suit fast-moving situations:
- Objection-handling drill: the AI customer raises one objection, such as "your competitor just cut their price," the rep responds, and the scenario ends.
- Focus scenario: a slice of a call, such as the pricing conversation, so reps drill one moment without running a whole call.
Someone on your team still supplies the new document. Itero then makes it practicable within the day, and certifications let you require reps to pass the new scenario before they take the updated message to customers. New Product Training covers launch rollouts in more detail.
Can Claude, Codex or another AI agent build scenarios from our documents?
Yes. Every Itero account includes a public API key, with no enterprise tier. Itero publishes ten free Agent Skills at github.com/Itero-AI/skills that teach Claude Code, OpenAI Codex, Cursor or Google Antigravity how to create and manage Itero content. You ask in plain English; the agent reads your documents, drafts the personas, scenarios and scorecard, and creates them in Itero as drafts after you confirm each request.
This route suits two jobs. The first is building a large library at once, for example a set of transcripts turned into scenarios. The second is upkeep: when the playbook changes, the agent updates the affected scenarios and criteria instead of someone rebuilding them by hand. One difference to know: the document-reading step in Scenario Studio runs inside Itero, while on the agent route the agent reads the documents itself and sends finished content through the API. See API & AI Agents.
