Roleplay has a reputation problem. Many reps remember it as an awkward hour where someone plays a prospect badly, everyone laughs nervously, and nothing changes on Monday. It does not have to be that way.
A good roleplay exercise is short, has one clear goal, and ends with a specific thing to try next. This article gives you nine such exercises. Each has a setup, rules and a debrief question. You can run them in a team meeting, in pairs, or on your own.
What makes a roleplay exercise worth running
Before the list, a few principles that separate useful roleplays from theatre.
- One skill per exercise. If you practise opening, discovery, objections and closing in one go, you cannot tell what improved.
- A realistic customer. The "customer" should behave like real ones: slightly distracted, unwilling to help you, not impressed by your product name. A role-player who is too friendly teaches nothing.
- Short rounds. Three to five minutes is enough. Long roleplays drift.
- Repetition. The second attempt, after one change, is where learning shows. Plan for it.
- Low stakes. People only try new wording when a mistake costs nothing.
How to run any exercise
Use the same simple format each time so people know what to expect.
- Setup (1 minute). State the scenario, who the customer is and the single skill being practised.
- Round one (3 minutes). The seller speaks; the customer responds naturally.
- Pause (1 minute). The seller names one thing they would change. Only one.
- Round two (3 minutes). Same scenario, with that change.
- Debrief (2 minutes). What was different the second time?
That is ten minutes in total, so it fits into the start of a weekly team meeting without taking over the agenda.
The nine exercises
1. The ten-second opener
Skill: opening a cold or warm call. Setup: the customer answers with "Hello?" and has no idea who you are. Rules: the seller has ten seconds to say who they are, why they are calling and ask one question. The customer ends the call if the opening sounds like a script. Debrief: which words did you use that a person would not say in conversation?
2. "It's too expensive"
Skill: handling a price objection without discounting. Setup: the customer likes the product but says the price is too high. Rules: the seller may not mention a discount in round one. They must ask what the customer is comparing the price with, then restate the value in the customer's words. Debrief: what did you learn about the objection that you did not know before you asked? (Price is rarely the whole objection.) There is a deeper walkthrough in this guide to answering "too expensive".
3. "I need to think about it"
Skill: finding the real concern behind a stall. Setup: the call has gone well, and then the customer says they need to think. Rules: the seller replies with a calm acknowledgement and one open question, such as "Of course. What would you like to think through?", and then stays quiet. Debrief: how long was the silence, and what did the customer say into it?
4. "Just send me an email"
Skill: keeping control of the next step. Setup: early in the call, the customer tries to brush you off with this line. Rules: the seller agrees to send something but must first ask one question that makes the email more useful, and agree a time to follow up. Debrief: did the customer commit to anything, or just let you go politely?
5. The silent customer
Skill: discovery with a customer who gives short answers. Setup: the customer answers every question with a few words and volunteers nothing. Rules: the seller may only ask open questions and must follow up on the customer's last answer instead of moving to the next prepared question. Debrief: which follow-up question unlocked the most information?
6. The first discovery call
Skill: structuring a first conversation around needs. Setup: a customer who has agreed to a 15-minute call and has an unspoken problem. Rules: the seller cannot mention a product feature until they can describe the customer's situation back to them in one sentence and the customer agrees it is accurate. Debrief: how many questions passed before you could summarise accurately? If you want a fuller guide, see the guide to preparing for a discovery call.
7. "We already have a supplier"
Skill: competing with an incumbent without attacking them. Setup: the customer is satisfied enough with their current provider. Rules: no criticism of the incumbent is allowed. The seller must ask what the customer would change about the current setup if they could change one thing, and listen to the whole answer. Debrief: what did the answer tell you about the next step?
8. The upset customer
Skill: staying calm and constructive when the other person is frustrated. Setup: the customer opens the call angry about a late delivery or an unexpected charge. Rules: the seller must acknowledge the feeling, confirm the facts, and propose one concrete action. No defensive explanations in the first thirty seconds. Debrief: at which sentence did the customer's tone change, if it did? This is also a core exercise for customer-service teams.
9. Asking for the next step
Skill: closing a call with a clear, agreed action. Setup: the conversation has gone reasonably well and is drifting to an end. Rules: the seller must propose a specific next step with a date, and the customer is allowed to push back once. Debrief: was the next step specific enough that someone could put it in a calendar?
How to debrief without making it awkward
The debrief is where the learning is, and also where roleplays often go wrong. Three habits help.
Let the seller go first. Ask them what they would change before anyone else comments. People are usually harder on themselves than a colleague would be, and they own the lesson more when they find it.
Point to moments, not impressions. "You sounded nervous" is not actionable. "When the customer said the price was high, your next sentence started with 'but'" is. Specific moments give people something to try.
Keep it to one change. Resist the temptation to list five improvements. One change, then run it again.
If you use a tool that produces a written report after each practice call, the same principle applies. DIRI AI's report, for example, highlights key moments in the call with timestamps and suggests one thing to try next, rather than a long list. You can look at the structure on the sample call page.
Running roleplays with remote teams
Remote teams lose the easy habit of grabbing a colleague for five minutes. Some ways to keep roleplay going:
- Pair people up on a rota. Rotate partners weekly so nobody practises only with their friend.
- Share one scenario per week. Everyone prepares the same situation, which gives the team a shared vocabulary for debrief. The objection of the week page can be a starting point.
- Make solo practice an option. Some people freeze when colleagues are watching. A private voice practice with an AI customer lets them rehearse first, then bring what they learned to the group. Team leads see team-level summaries rather than individual rankings; the team pilot page explains how that works.
- Never use practice results to rank people. Practice only works if mistakes are safe. DIRI AI's own scoring page states that scores are meant for training, not for decisions about people; see how we score.
Related: Sales role-play exercises for teams, Call Centre QA Scorecard Template (Sales + Service), Sales role-play interview. Free tool: Sales Call Checklist.
Make it a habit
One roleplay in a quarterly workshop will not change much. Ten minutes a week, with one skill and a repeat attempt, will. Pick two exercises from this list, run them this week, and write down what each person wants to try on their next real call.
If you would like to practise alone between team sessions, DIRI AI has a free plan: 3 voice calls a month of up to five minutes each, with a report afterwards and no card needed. Start free and try the price-objection exercise against an AI customer today. For more scenarios and wording to rehearse, browse the objection catalogue or the sales training use cases.