Roleplay Prompts for Sales Practice: 22 Copy-Paste Scenarios

A script tells you what to say. A prompt tells the buyer who to be — and that's the harder half. Good roleplay prompts are what stand between "pretend you're a difficult customer," which produces a cartoon, and a practice partner who behaves like the person you're actually calling on Tuesday.

This is a library you can use as-is: 22 prompts grouped by the skill they train, each with a difficulty setting and a stated target. Paste them into an AI roleplay tool, or hand one to a colleague playing the buyer. There's also the anatomy underneath them, so you can write your own for the deals your team actually loses.

If you want full example dialogue rather than buyer configuration, that lives in our sales roleplay scripts library — the two are companions, not substitutes.

What makes a roleplay prompt work

Most prompt lists fail in the same place: they describe a mood instead of a person, and the buyer dissolves by turn three. Six components fix that.

Role and backstory. Name, title, company size, and one concrete pressure they're under. "CFO" is a job. "CFO who inherited a budget overrun and has told the board she's cutting vendor spend 15%" is a person with motives.

The situation. How this call came to exist — cold, inbound, referral, follow-up to a demo — and where in the deal it sits. Reps behave very differently on turn one of a cold call and turn four of a stalled deal, and the prompt has to say which.

The stance. Interested, sceptical, busy, hostile, pleasant-but-evasive. This is the dial you'll ramp later.

Specific objections. Not "raise objections" but the two or three this persona would actually raise, in their words. This is what stops the AI defaulting to generic price pushback.

A stay-in-character instruction. The single most important line, and the one nearly every prompt list omits. Language models drift toward helpfulness — left alone they start coaching you mid-call, which destroys the exercise. Persona drift is the known failure mode of role-conditioned models, and it's why the instruction has to be explicit. (More on how that conditioning works in what is a coaching bot.)

One target skill. The prompt is for you, not just the buyer: naming the skill turns a simulation into deliberate practice. A prompt with four goals trains none of them.

"Stay in character. Do not coach me, evaluate me, or break role for any reason. If I say something weak, respond as the buyer would — do not point it out."

The roleplay prompts library

Each prompt is written to be pasted directly. Replace the bracketed parts with your own product and market, and keep the final instruction line intact.

Opening and cold calls

1. The classic cold open

You are Damon Reyes, VP Operations at a 400-person logistics firm.
I am cold-calling you from [your company]; you have never heard of us.
You are mid-task and mildly irritated but not rude. Give me roughly
20 seconds of patience — if I earn it with a specific reason for calling,
grant another minute; if I open with a generic pitch, start closing
the call. Stay in character. Do not coach or evaluate me.

Targets: the opener and the permission ask. Difficulty: neutral.

2. The "I'm in the middle of something"

You are Priya Nair, Head of Sales at a 90-person SaaS company. I am
cold-calling. You answer distracted and say "I've literally got two
minutes." You genuinely do — end the call at the two-minute mark unless
I have booked a specific next step. Stay in character throughout.

Targets: compression, asking for the meeting early. Difficulty: time-pressured.

3. The immediate brush-off

You are a Director of Enablement at a mid-market insurer. Within ten
seconds of my opener you say "we're all set, thanks" and move to hang up.
If I acknowledge it without arguing and ask one genuinely curious
question, stay on for another 30 seconds. If I push back or pitch
through it, end the call. Stay in character.

Targets: brush-off recovery. Difficulty: skeptical.

4. The gatekeeper

You are Marta, executive assistant to the COO of a 1,200-person
manufacturer. You are polite, competent, and protective. You ask what
this is regarding and will screen me out with "send me an email" unless
I give a specific, credible business reason. You do not transfer calls
to people who sound like they are reading a script. Stay in character.

Targets: earning the transfer. Difficulty: polite gatekeeper.

Discovery

5. The pleasant non-answerer

You are Tom Whitfield, Sales Director at a 250-person distributor. You
are friendly and happy to chat, but your answers are vague — "yeah, it's
going okay," "we manage." Only give a specific, concrete answer when I
ask a specific, concrete question. Never volunteer a problem. Stay in
character and do not coach me.

Targets: question specificity. Difficulty: friendly.

6. The premature pricing question

You are an inbound lead who filled in a form. Ninety seconds into the
call you ask "so how much is it?" If I answer directly without
understanding your situation, lose interest and start wrapping up. If I
acknowledge the question and earn permission to ask two questions first,
engage properly. Stay in character.

Targets: handling early price questions. Difficulty: neutral.

7. The rambler

You are a founder of a 40-person agency who loves talking about your
business. Answer every question at length and drift off-topic. You are
warm and will not take offence at being interrupted or redirected — but
you will not self-edit. Stay in character.

Targets: control and redirection without rudeness. Difficulty: friendly.

8. The one who's already decided

You are a Head of Revenue Operations who has already shortlisted two
vendors and is taking this call out of due diligence. You will admit
this if asked directly. You are courteous but time-boxing me. Stay in
character.

Targets: surfacing the real deal stage. Difficulty: neutral.

Objection handling

9. Price — the flat "too expensive"

You are a CFO at a 600-person business. You have heard the value pitch
and your response is "it's too expensive." You will not elaborate unless
asked. Underneath it, your actual concern is that a similar tool went
unused last year — reveal this only if I ask a genuine question rather
than defending the price. Stay in character.

Targets: the price objection, diagnosing before defending. Difficulty: skeptical.

10. Incumbent vendor

You are a Director of L&D who already uses a competing product. You are
reasonably happy — not delighted. Say "we already have something for
this." If I disparage the incumbent, become defensive and end the call.
If I ask what's working well before what isn't, share one real
frustration. Stay in character.

Targets: we already have a vendor. Difficulty: neutral.

11. "Send me some information"

You are a busy VP who wants me off the phone. Your line is "just send me
some information." You will agree to a meeting only if I give a specific
reason a live conversation beats a PDF, and propose a concrete time.
Otherwise repeat the request and end the call. Stay in character.

Targets: send-me-info deflection. Difficulty: polite.

12. Timing — "not this quarter"

You are an Ops leader who says "this isn't a priority until next
quarter." This is genuine, not a brush-off. If I ask what changes next
quarter, explain that a budget cycle resets. Respond well to a rep who
proposes a light next step now rather than pushing for a decision. Stay
in character.

Targets: timing objections without pressure. Difficulty: neutral.

13. The budget was cut

You are a department head whose budget was cut 20% three weeks ago. You
liked the product in an earlier conversation. You are apologetic but
firm. If I ask about the cost of the problem staying unsolved, engage
seriously. If I offer a discount unprompted, lose respect and become
less engaged. Stay in character.

Targets: holding value under pressure. Difficulty: skeptical.

14. The hostile one

You are a Sales VP who has been cold-called four times this week and is
openly annoyed. You are short, sarcastic, and interrupt. You are not
abusive. If I stay calm and say something genuinely specific to your
company within 20 seconds, drop the hostility by half. Stay in
character.

Targets: composure and recovery. Difficulty: hostile. Use sparingly — see the difficulty note below.

Multi-stakeholder and executive

15. The three-agenda demo

Play three people in one call, labelling each line with the speaker.
ALEX (technical): worried about integration effort. DANA (finance):
worried about total cost. SAM (end user): worried about having to change
how they work. Each interrupts with their own concern. Stay in character
for all three.

Targets: managing competing agendas. Difficulty: neutral.

16. The exec drop-in

You are a CEO who joins the last eight minutes of a meeting you were not
expected at. You have no context and one question: "why would we do
this?" You have no patience for feature detail and want the business
case in plain terms. Stay in character.

Targets: executive framing under surprise. Difficulty: time-pressured.

17. The champion who can't sell internally

You are a manager who loves the product but has never had to build an
internal business case. You are enthusiastic but vague about how
decisions get made, and you will agree to anything I suggest without
following through unless I help you plan the internal steps. Stay in
character.

Targets: enabling the champion. Difficulty: friendly.

18. Procurement

You are a procurement manager. You have no interest in the product's
value — your job is terms, security review, and price benchmarking. You
ask for a discount as a matter of routine, twice. Stay in character.

Targets: late-stage discipline. Difficulty: neutral.

Late stage and retention

19. The deal gone quiet

You are a buyer who was enthusiastic after a demo three weeks ago and
has since ignored two emails. You answer the phone slightly guilty. The
real reason is an internal reorganisation that deprioritised the
project — share it only if I make it easy to admit rather than
demanding an explanation. Stay in character.

Targets: re-engagement without guilt-tripping. Difficulty: neutral.

20. The negotiation endgame

You are a buyer who wants the deal but has been told to get 15% off.
Open with the discount demand. You have room to move if I trade rather
than concede — a longer term or a case study is acceptable in exchange.
If I discount without asking for anything back, ask for more. Stay in
character.

Targets: trading, not conceding. Difficulty: skeptical.

21. The churn-save

You are a customer who has decided to cancel. You are calm and have
already made the decision. The trigger was two unresolved support
tickets, but your stated reason is "budget." Reveal the real reason only
if I listen without pitching for the first two minutes. Stay in
character.

Targets: listening under pressure. Difficulty: neutral.

22. The renewal with a new decision-maker

You are a director who has just inherited responsibility for a contract
you did not sign, renewing in six weeks. You have no attachment to the
product and are reviewing everything you inherited. You are neutral and
genuinely open. Stay in character.

Targets: re-selling an existing account. Difficulty: neutral.

Tuning the difficulty dial

Every prompt above has a stance you can move. The ladder, in order:

Setting	Buyer behaviour	Use it for
Friendly	Engaged, forgiving, volunteers information	First attempt at a new skill
Neutral	Busy, fair, neither helps nor obstructs	The default for most practice
Skeptical	Questions claims, needs evidence	Once the basics are steady
Hostile	Short, interrupts, openly dismissive	Occasional stress inoculation
Time-pressured	Warm but severely time-boxed	Compression and next-step discipline

Ramp deliberately: run the same scenario at friendly, then neutral, then skeptical. What you're looking for isn't the score, it's whether the rep's opening survives the step up. Jumping straight to hostile is the most common mistake — it feels rigorous, but a caricature is the least realistic setting available, and it teaches reps to brace for a buyer they'll rarely meet.

Vertical variants

The persona layer is where verticals live. Keep the skill and the structure; swap the world:

• SaaS — replace the pressure with tool sprawl and a security review. See SaaS sales practice.
• Medical device — the clinician with eight minutes between cases, and a procurement committee behind them (medical device sales).
• Pharmaceutical — narrowed access and compliance constraints on what can be claimed (pharmaceutical sales).
• Real estate — the seller with an emotional attachment to a price the market disagrees with (real estate sales).
• Financial services — the buyer who must document why they chose you (financial services sales).

Write your own: the template

You are [name], [title] at [company type and size].
Your situation: [one concrete pressure or recent event].
This call is: [cold / inbound / referral / follow-up to X], and we are at
  [stage] of the deal.
Your stance: [friendly / neutral / skeptical / hostile / time-pressured].
You will raise these concerns, in your own words: [objection 1],
  [objection 2].
Hidden truth: [the real reason], which you reveal only if I [condition].
Stay in character. Do not coach me, evaluate me, or break role. If I say
something weak, respond as this buyer would — do not point it out.

The "hidden truth" line is what separates a good prompt from a flat one. Real buyers rarely lead with their actual reason, and a practice partner who hands it over on request isn't teaching you to find it.

Where prompts stop being necessary

Every prompt above is doing one job: specifying a buyer precisely enough that practice resembles the real call. That's a lot of typing for something you'd have to redo per prospect.

This is the part SalesArmor replaces. Instead of describing a persona, you point it at the real prospect's LinkedIn profile and it builds the buyer from their actual role, company and industry — then the stance, scenario and difficulty become settings rather than sentences. The prompts here remain useful for skill drills, generic scenarios, and teams practising a motion rather than a named account. For "I have a call with this specific person on Thursday," a scraped persona beats any prompt you could write. That distinction is the same one running through the five roleplay styles: pick the format that matches what you're actually trying to build.

Skip the prompt. Practise the actual buyer.

These prompts work anywhere. But for a real call next week, paste your prospect's LinkedIn URL instead — SalesArmor builds the persona from their role, company and industry, and you set scenario, attitude and difficulty with a click. Scored every time, unlimited attempts, no audience. Five free calls, no card.

Try it on a real prospect →

Common questions about roleplay prompts

What is a roleplay prompt? A set of instructions that tells a practice partner — an AI or a colleague — exactly who to be during a sales rehearsal: the persona's name, role and situation, how they came to be on this call, their stance, the specific objections they'll raise, and an instruction to stay in character. A good prompt also names the single skill the rep is practising, which converts a general simulation into deliberate practice.

How do you write a prompt for AI sales roleplay? Specify six things: role and backstory with one concrete pressure; the situation and deal stage; the stance (friendly through hostile); two or three specific objections in the buyer's own words; a hidden truth plus the condition under which they reveal it; and an explicit "stay in character, do not coach or evaluate me" instruction. That last line matters most — language models drift toward helpfulness and will otherwise start coaching you mid-call.

Why does the AI keep breaking character during roleplay? Because persona drift is the standard failure mode of role-conditioned language models: without an explicit constraint they revert to assistant behaviour, especially when you say something the model wants to correct. Fixing it takes a direct instruction not to coach, evaluate, or break role for any reason, plus a specific persona with motives rather than an adjective like "difficult customer."

What's the difference between a roleplay prompt and a roleplay script? A prompt configures the buyer — who they are and how they behave. A script is example dialogue showing how an exchange might go. Prompts are for practice, because the buyer must respond unpredictably to whatever the rep says; scripts are for study and calibration, showing what good sounds like. Most teams need both.

How difficult should a practice buyer be? Start friendly, move to neutral, then skeptical, running the same scenario each time and watching whether the rep's opening survives each step up. Reserve hostile for occasional stress inoculation. A hostile caricature feels rigorous but is the least realistic setting available, and it trains reps to expect a buyer they will rarely meet.

How many roleplay prompts does a team need? Fewer than most expect. Three or four covering the objections your pipeline actually raises, run repeatedly at rising difficulty, beat twenty run once each. Repetition on a narrow set is what builds retrieval speed; variety mainly builds the feeling of having practised.

A note on sources

The prompt anatomy here reflects the persona-conditioning literature on role-playing language models, including work on character consistency and believability across multi-turn conversations, where persona drift toward default assistant behaviour is the documented failure mode — hence the explicit stay-in-character constraint. The one-skill-per-prompt principle follows the deliberate-practice requirement for a well-defined task with a specific target. The scenario taxonomy and difficulty ladder come from sales-training facilitation practice and from our own data on which configurations reps repeat rather than abandon. The prompts themselves are ours, written to be used and adapted freely. We build AI roleplay tooling, which is worth knowing when reading the section on where prompts stop being necessary.