A new seller jumps into their first cold call. The opener lands β the buyer stays on the line. Then the call turns. A tough objection shows up, the rep misses it, and the conversation ends early. Later, a manager sends a few notes. The rep does their best to apply them on the next call β hoping it sticks.
Thatβs the real problem role play is meant to solve: practice the moments that break on real calls, then use feedback to make the next attempt better.
In this guide, youβll get three sales role play scenarios with sample scripts and interactive examples β plus a strategy playbook for making role play translate to real calls.
Scenarios and scripts
Sales role play works best when the practice feels like the real call.
Below are three ready-to-use scenarios you can copy, run in a team session, or adapt to your product and buyers: cold call, objection handling, and deal advancement.
Each includes a short setup, a sample script, and a feedback focus. Youβll also see an interactive example for each scenario. Treat these as patterns you can model β the structure reflects best practices you can customize by swapping in your product, buyers, and objections.
π‘Tip:Β Want to adapt these scenarios to your product and buyers? Use the AI script generator to draft a role play script.
Scenario 1: Cold Call (click to expand)
ποΈ What This Scenario Helps Reps Practice
- Earning permission fast
- Proving relevance in one sentence
- Asking one strong diagnostic question
- Securing a clear next step
π Scenario Context
Youβre an SDR calling a mid-market buyer whoβs busy and skeptical. They didnβt request this call.
Your job isnβt to pitch β itβs to earn enough interest for a next step.
- Seller: SDR / BDR
- Buyer: Director-level
- Call type: First-touch cold call
- Goal: Book a follow-up or send something with a scheduled follow-up
π§βπΌ Seller Instructions
In 30 seconds, you must:
- Ask for permission
- State relevance in one sentence
- Ask one diagnostic question
- Propose a next step with two time options
Constraints:
- No feature dump
- Donβt close with βCan I send you an email?β
- If they say βsend me something,β clarify what and book the follow-up
π Buyer Prompts
Use 2β3 per run:
- βIβm about to jump β what is this?β
- βWe already have something for that.β
- βJust send me something.β
- βNot a priority this quarter.β
- βHow did you get my number?β
- βWhat makes you different?β
ποΈ Conversation Structure
- Permission
- Relevance
- Diagnostic question
- Value hypothesis
- Next step
π¬ Example Lines
Permission + relevance:
- βHi [Name] β [Rep] from [Company]. Did I catch you at a bad time?β
- βTotally cold call β can I take 20 seconds, then you can tell me no?β
- βWe help [role] at [company type] improve [outcome]. Quick question β how are you handling [problem] today?β
If they say βSend me somethingβ:
- βHappy to β whatβs more relevant right now: [Option A] or [Option B]?β
- βSo I donβt send fluff β what are you trying to improve most: [A] or [B]?β
- βIβll send a short overview tailored to that. If itβs relevant, should we hold 15 minutes on [Day] or [Day]?β
If they say βWe already have somethingβ:
- βIs it working the way you want β or is there a gap?β
- βWhat would you change about it if you could?β
π Feedback Focus
Score yes/no plus notes:
- Permission + brevity
- Relevance tied to an outcome
- Real diagnostic question and reaction to the answer
- Clear next step with time options
π₯ Practice This Scenario with a Video Agent
Scenario 2: Objection handling (click to expand)
ποΈ What This Scenario Helps Reps Practice
- Earning permission fast
- Proving relevance in one sentence
- Asking one strong diagnostic question
- Securing a clear next step
π Scenario Context
The buyer pushes back early. The goal isnβt to βovercomeβ objections with clever lines β
itβs to clarify whatβs behind the objection and earn agreement on what happens next.
- Seller: AE or SDR
- Buyer: Practical, time-poor
- Call type: Discovery or follow-up
- Goal: Define criteria for moving forward and book the next step
π§βπΌ Seller Instructions
In 2β4 minutes, you must:
- Acknowledge the objection
- Ask two clarifying questions
- Reframe around outcomes and criteria
- Propose a next step tied to the objection
Constraints:
- No long monologues
- Donβt argue or βpitch harderβ
- Donβt switch into a feature dump
- Donβt end with vague follow-up
π Buyer Prompts
Use 2β3 per run:
- βWe already have something for that.β
- βThis isnβt a priority.β
- βToo expensive.β
- βWe donβt have bandwidth.β
- βWeβre just researching.β
- βWe need approval.β
ποΈ Conversation Structure
- Acknowledge
- Clarify
- Diagnose impact
- Define criteria
- Next step
π¬ Example Lines
If they say βWe already have somethingβ:
- βMakes sense β is it working well, or is there a gap youβre trying to close?β
- βWhat would you change about it if you could?β
- βIf we could improve [metric] without disrupting the current setup, worth a quick comparison?β
If they say βNot a priorityβ:
- βTotally fair β what is a priority right now?β
- βWhat would need to happen for this to move up?β
- βIs it solved, or just crowded out by other work?β
If they say βToo expensiveβ:
- βCompared to what β another option, the current setup, or doing nothing?β
- βIs the concern budget, risk, or proving value?β
- βIf we can tie this to a measurable outcome, would a short evaluation step be worth it?β
π Feedback Focus
Score yes/no plus notes:
- Acknowledged without debating
- Clarified the real objection
- Kept control of the conversation structure
- Proposed a next step that matches the objection
π₯ Practice This Scenario with a Video Agent
Scenario 3: Deal advancement (click to expand)
ποΈ What This Scenario Helps Reps Practice
- Turning interest into commitment
- Clarifying decision process and stakeholders
- Defining proof and success criteria
- Building a mutual plan with a scheduled next step
π Scenario Context
The buyer sounds positive but vague: βLooks good,β βWeβll review,β βSend me something.β
The repβs job is to create clarity: who decides, what they need to see, and what happens next.
- Seller: AE
- Buyer: Interested but non-committal
- Call type: Post-demo or late-stage checkpoint
- Goal: Confirm process, align stakeholders, and book the next meeting with a clear purpose
π§βπΌ Seller Instructions
In 3β5 minutes, you must:
- Confirm who needs to be involved
- Clarify what a βyesβ depends on
- Define success criteria
- Schedule the next step with attendees and agenda
Constraints:
- Donβt accept βweβll get back to youβ as the end state
- Avoid βchecking inβ language
- Donβt send a proposal without booking a review
π Buyer Prompts
Use 2β3 per run:
- βThis looks good β weβll review and get back to you.β
- βCan you just send a proposal?β
- βSecurity needs to weigh in.β
- βBudget might be tricky.β
- βWeβre comparing options.β
- βTiming is uncertain.β
ποΈ Conversation Structure
- Align
- Stakeholders
- Dependencies
- Success criteria
- Mutual plan
π¬ Example Lines
If they say βWeβll review and get back to youβ:
- βMakes sense β who else needs to be comfortable saying yes?β
- βWhat would you need to see to feel confident moving forward?β
- βCan I suggest a next step? Letβs schedule 30 minutes with [stakeholder] to align success criteria and clear any risks.β
If they say βSend a proposalβ:
- βHappy to β is this for budgeting, or are we close to a decision?β
- βWho needs to see it, and what do they care about most?β
- βIf I send it, can we hold 20 minutes on [Day] to review it together and decide next steps?β
If they say βWeβre comparing optionsβ:
- βWhat are the top criteria youβre comparing on?β
- βWhereβs the biggest uncertainty β results, risk, effort, or cost?β
- βIf we can validate [criterion] quickly, would a short pilot be worth it?β
π Feedback Focus
Score yes/no plus notes:
- Clarified stakeholders and process
- Defined success criteria and proof
- Proposed a mutual plan with a purpose
- Secured a scheduled next step
π₯ Practice This Scenario with a Video Agent
The role play playbook
Role play doesnβt fail because teams donβt try it. It breaks because the practice doesnβt transfer to the real conversation.
If youβre using the scenarios above in a team session, start here. These are the most common pitfalls that make role play feel useful in the room but disappear on live calls.
Pitfall 1: The scenario isnβt realistic
If the buyer context is vague, reps can βwinβ by improvising in ways theyβd never get away with on a real call.
Fix: Make the scenario specific. Define the buyer role, the trigger, the constraints, and the objections you actually hear. Use the sellerβs working language.
Pitfall 2: The practice is too broad
When one run tries to cover discovery, value, objections, and closing, feedback gets diluted and the rep leaves unsure what to change.
Fix: Design each role play around one capability. One run, one skill, one win condition.
Pitfall 3: Feedback is too general, and thereβs no retry
βSlow downβ and βask better questionsβ are well-intentioned, but they donβt tell a rep what to do differently on the next attempt.
Fix: Anchor feedback to one observable behavior and run an immediate second attempt. Improvement shows up on the retry.
What changes when role play works
When role play is built for transfer, it stops being a one-off training activity and becomes reinforcement. Three outcomes tend to follow:
- Execution becomes more consistent: sellers rehearse the moments that usually break under pressure.
- Feedback becomes actionable: coaching becomes specific, behavioral, and easy to apply.
- Readiness becomes easier to assess: you get observable evidence of capability, not just confidence.
Those outcomes come from focused scenarios, clear standards, and a quick second attempt after feedback.
Anatomy of an effective sales role play
Role play improves execution when the scenario feels real and the practice is focused enough to produce clear feedback.
A transferable role play has just enough structure:
- Context: buyer role, industry, deal stage, constraints
- Trigger: why this conversation is happening now
- Objective: the single capability being practiced
- Constraints: time pressure, stakeholders, objections
- Win condition: what good looks like in observable terms
- Retry loop: a second attempt after feedback
That last piece matters more than most teams expect. Feedback earns its value when it creates a cleaner second attempt.
π Common sales role play scenarios
Cold calls / first outreach
Earn permission, establish relevance quickly, and set a clear next step.
Objection handling
Handle price, timing, competition, and internal buy-in objections without defaulting to concession.
Deal advancement
Align on the decision process, confirm stakeholders, and secure mutual commitments and next steps.
These scenarios only work when they feel like real selling β same context, same
constraints, same kinds of turns that happen on live calls. Effectiveness comes
from designing for learning transfer, not recitation.
[Source]
Building rubrics for consistent evaluation
Scenarios give you the structure for practice. Rubrics make that practice comparable, defining what good looks like in observable terms, so feedback stays consistent across teams and regions.
A rubric is only as useful as the competencies underneath it. In this context, competencies are the capability areas you expect sellers to demonstrate (for example: diagnostic discovery, value articulation, objection navigation, deal advancement).
We recommend following these steps to build a rubric:
- βStart with an internal skill map: Choose 3β6 competencies that match how your organization defines selling capability.β
- Write a one-line definition for each competency: Keep it behavioral and job-specific, not aspirational.β
- Assign one observable behavior per competency: This is the scoring anchor. One behavior keeps evaluation clean and feedback usable.β
- Score what you can see: Feedback should be focused on performance, not personality (e.g., smiling too much). β
π‘Tip: Keep rubrics consistent across regions. Localize the scenario context to match the market and the sellerβs working language.
Example competencies
You can adapt the wording to match your internal taxonomy. The important part is the pattern: competency β definition β observable behavior.
π Example competency rubric (one observable behavior each)
| Competency |
Definition |
Observable behavior |
| Diagnostic discovery |
Identifies the buyerβs situation and confirms the problem worth solving. |
Asks one diagnostic question that changes the direction of the conversation. |
| Value articulation |
Connects the offering to a stakeholder outcome in the buyerβs context. |
States value in the buyerβs terms (outcome + impact), not product features. |
| Objection navigation |
Responds to resistance in a way that clarifies, addresses, and advances the deal. |
Asks a clarifying question before responding to the objection. |
| Deal advancement |
Moves the opportunity forward with mutual clarity on next steps and decision path. |
Confirms a specific next step with purpose, attendees, and timing. |
Scaling feedback with AIΒ coaching
Rubrics keep feedback consistent. Timing makes it useful.
AI coaching strengthens the practice loop by delivering feedback as practice happens, so sellers can adjust and retry while the scenario is still fresh.
To keep feedback usable, anchor it to one observable behavior and one concrete adjustment. AI feedback works best when it functions like a strong facilitator: it points to the moment that mattered, names the behavior, and prompts a cleaner retry.
A simple feedback structure:
- Name the moment
- Name the behavior
- Name the adjustment
- Retry immediately
π‘Emerging research suggests AI can strengthen skill development when itβs used to support practice and feedback
Embedding role play into your enablement strategy
Role play scales when it runs like a system: realistic scenarios, stable standards, and a repeatable loop where feedback leads to a better second attempt.
That system needs clear ownership:
- Enablement: scenario library, rubric, and what good looks like
- Managers: reinforcement in 1:1s and deal reviews
- Leadership: readiness decisions and investment priorities
AI coaching fits inside this model as the delivery layer for practice and feedback at scale.
π‘Tip: Considering AI coaching for role play? Use this checklist to evaluate quality and fit.
β
What to look for in AI coaching
-
Scenario fidelity:
Scenarios reflect real selling moments and can be adapted by role, segment, and region without changing the standard.
-
Feedback quality:
Feedback anchors to one observable behavior in the rubric, points to the moment that mattered, and makes the next attempt clearer.
-
Standards control:
Enablement controls competencies and rubrics, and criteria map to your internal skills framework.
-
Global scalability:
Standards stay consistent while scenarios localize to market context and the sellerβs working language.
-
Evidence that supports decisions:
Outputs support readiness and coaching focus without overpromising precision.
-
Enterprise governance:
Meets expectations for privacy, compliance, retention, access controls, and multilingual support.
-
Fit with your enablement stack:
Integrates where needed (for example: LMS, CRM, reporting workflows).