One roleplay agent can be built from a call that actually took place, objections and all. Another can be built from the script a team is supposed to follow on a call that has not happened yet. Outdoo treats both as legitimate raw material, not just one.
Why this matters
A roleplay persona invented from a manager's imagination reflects a guess, not reality, and reps tend to notice the difference. But "real" source material comes in two forms depending on what a team actually has on hand.
Sometimes it is a recording of what a prospect genuinely said and how they genuinely pushed back. Other times there is no recording to draw from at all, because the product just launched, the messaging just changed, or the team is entering a vertical it has never sold into, and the only real material that exists is the approved script, playbook, or talk track written for that moment. Treating only recorded calls as legitimate leaves the second kind of material sitting unused.
How it works
The first path starts from an actual call. Upload an audio or video recording directly, or connect a conversation intelligence tool such as Gong. If more than one person is on the recording, a manager identifies which participant should become the AI buyer, so a call between a rep, a buyer, and a technical evaluator does not blur into one confused persona.
Outdoo extracts persona traits, emotional tone, conversation style, objections, and behavioral patterns from the transcript, then turns them into a configurable agent the manager reviews before setting call type, scorecard, and coaching instructions.
The second path starts from a document instead of a recording. During agent creation, a manager attaches a written call script, sales playbook, or talk-track file, either uploaded fresh or selected from the Resources library, and the agent grounds its responses, objections, and product knowledge in that content rather than a generic template. This path covers material never spoken aloud on any real call: an approved discovery script for a product that shipped last week, a compliance-reviewed talk track, a battlecard for a competitor the team has not faced yet.
The two paths are complementary rather than competing. A rep preparing for a renewal on an established account can practice against an agent built from an actual call that went sideways, while the same rep, preparing to pitch a product that launched two weeks ago, practices against an agent built from the approved script, since no real call exists yet to extract one from.
What this unlocks
A team launching a new product line can get reps rehearsing the approved positioning before a single real customer call happens, by building the agent straight from the talk-track document product marketing signed off on. A sales manager who just listened to a renewal call nearly fall apart over a pricing objection can turn that recording into a training scenario the same afternoon.
In regulated industries like financial services or insurance, a compliance team can upload the exact approved disclosure script so new hires rehearse the required language word for word, while a separate agent built from a real recorded call shows how clients actually respond to that disclosure in practice, so reps prepare for both the letter of the requirement and the reality of hearing it delivered.
Full setup steps are in Create a roleplay agent from existing calls and Create a roleplay agent from a file or resource.
A script tells a rep what the company wants said. A recorded call shows what actually happens once someone says it. Practicing against only one of those is practicing against half the truth.
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