Building a roleplay agent used to mean filling out a form field by field: buyer title, industry, objections, tone, scenario stage. Now it can mean typing two sentences, or picking a template and hitting create.
Why this matters
Not every training need justifies a from-scratch build. A manager who needs a "skeptical CFO pushing back on price" agent for tomorrow's team meeting does not want to configure a dozen fields.
And a new enablement hire building their first cold call scenario does not want to guess what a good roleplay agent should even contain. Speed and a sensible starting point matter as much as depth here, especially for teams running roleplay practice weekly across multiple scenarios.
How it works
With prompt-based creation, a manager writes a short description of the buyer and situation, for example a mid-market IT director evaluating three vendors and worried about implementation time, and Outdoo generates a complete roleplay agent from that prompt: persona, likely objections, tone, and scenario framing, ready to use or refine. The manager still picks the call type the agent should run, cold call, discovery, qualification, demo, pricing, or negotiation, so the same buyer description can be pointed at whichever stage of the cycle needs practice.
With template-based creation, the manager instead starts from a ready-made template built for a common scenario: cold calls, discovery calls, demos, negotiation, objection handling, and other standard stages of a sales cycle.
The template arrives pre-populated with a sensible persona and structure, which can be edited before use or used as-is. Templates also carry an optional mid-call starting context, so a manager can drop a rep straight into the moment that matters, the pricing objection, the stall after the demo, rather than rehearsing the opening small talk every single time.
Both methods sit alongside Outdoo's other creation paths, building from an existing call or from a file, so a team picks the input that matches what they have on hand: a paragraph of intent, a known scenario type, or a real transcript.
What this unlocks
An enablement manager building out a full onboarding curriculum can generate ten scenario variants in the time it used to take to configure one, using templates for the standard stages and prompts for anything specific to their market. A frontline sales manager who wants to drill a rep on a specific pushback before a call tomorrow can type it in and have an agent ready in minutes rather than filing a request with the enablement team.
A customer success lead prepping the team for renewal season can start from the negotiation template, swap in a persona weighing a competitor's lower price, and have a renewal-pushback scenario ready before the next team meeting instead of building one from a blank page.
Details on each method are in Create a roleplay agent from a prompt and Create a roleplay agent using templates.
Launched in v2.9, August 2025. The choice of how to start a roleplay agent should depend on what a manager already knows about the buyer, not on how much time they have to build a form.
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