Skip to main content

Workplace Roleplay Scenarios

Workplace Roleplay Scenarios

A workplace roleplay scenario needs three things to be usable: a specific situation, a brief for each of the two roles, and a goal that tells you when the conversation has succeeded. The 50 scenarios below include all three. They cover sales roleplay, customer service roleplay, difficult conversations between colleagues, management and feedback, meetings and interviews, and each is marked beginner, intermediate or advanced.

Last updated:

How to choose a roleplay scenario

A roleplay is worth the time when it is close to a conversation someone will really have, and hard enough that the first attempt goes imperfectly.

  1. Start from a real conversation coming up

    Ask each person which conversation in the next month they would least like to have. Pick the nearest scenario and change the details (product, numbers, job titles) to match.

  2. Give the other role something to want

    A roleplay partner who simply agrees teaches nothing. Every scenario here gives the second role a motive or a line to push back with. Ask whoever plays it to resist at least twice before conceding.

  3. Raise the difficulty one step at a time

    Begin with a beginner scenario so people get used to speaking in role. Move to intermediate once the opening lines come easily. Advanced scenarios involve high emotion or no good outcome, and work best after trust has been built in the group.

  4. Keep each round short and run it twice

    Four to six minutes of roleplay, two minutes of feedback, then the same scenario again. The second attempt is where the improvement shows.

Example

Worked example: adapting a scenario for your team

  1. Your support team keeps struggling with customers who ask for a manager straight away.
  2. Choose "I want to speak to your manager" from the customer service section.
  3. Replace the double charge with your most common complaint, and the 24-hour callback with your real escalation time.
  4. Brief the person playing the customer privately: "A previous agent hung up on you." The agent does not know this.
  5. Run it for five minutes, discuss which sentence changed the customer's tone, swap roles and run it again.

50 workplace roleplay scenarios

Filter by team and by difficulty. Each card gives the setup, a brief for each role and the goal for the person practicing, who plays the first role listed.

Filter the list

For
Difficulty
Category

Showing 50 of 50

Sales roleplay scenarios

Ten situations from first contact to a lost deal. Run each one twice and swap roles, because playing the buyer shows you what your own pitch sounds like.

  • Cold call that reaches the assistant

    Sales teamsBeginner

    Setup: A sales rep phones a logistics company to reach the operations director. The director's assistant answers and has been told to screen sales calls.

    Sales rep:
    You have one sentence to explain why the call is worth passing on, and you must stay polite if refused.
    Executive assistant:
    You are friendly but protective, and you ask "What is this regarding?" and "Is she expecting your call?"

    Goal: Get either a transfer, a named time to call back or the director's preferred contact route, without misleading the assistant.

  • The prospect who says "just send me the pricing"

    Sales teamsIntermediate

    Setup: Five minutes into a discovery call, a marketing manager cuts in and asks for a price list by email so they can end the call.

    Account executive:
    You need to learn the prospect's team size and current tool before any quote makes sense.
    Marketing manager:
    You are short on time, have sat through bad demos before and do not want to be "sold to".

    Goal: Earn two more minutes by asking one question the prospect finds worth answering, then agree a concrete next step.

  • "Your competitor is 20 percent cheaper"

    Sales teamsIntermediate

    Setup: A buyer who liked the demo comes back with a competing quote that is 20 percent lower and asks you to match it.

    Account executive:
    You cannot discount more than 5 percent, and you believe your onboarding support is the real difference.
    Purchasing manager:
    You like the product but must justify the higher price to your finance director in one paragraph.

    Goal: Find out what the cheaper quote leaves out and give the buyer a sentence they can repeat to finance, without attacking the competitor.

  • Demo for a skeptical technical buyer

    Sales teamsAdvanced

    Setup: The business sponsor loved the product. Now their head of IT joins a call and has thirty minutes to find reasons it will not work.

    Solutions consultant:
    You know the product well but there are two integrations it does not support yet.
    Head of IT:
    You ask pointed questions about security, data export and what happens when the service is down.

    Goal: Answer honestly, including "it does not do that today", and leave with a list of the three checks IT needs before approving.

  • Renewal with a customer who barely used the product

    Sales teamsIntermediate

    Setup: The annual renewal is due in six weeks. Usage data shows only 4 of the customer's 30 licenses were active last quarter.

    Customer success manager:
    You want the renewal but know that renewing all 30 seats unchanged will lead to a cancellation next year.
    Operations lead:
    You have forgotten why the team bought the tool and are leaning toward letting it lapse.

    Goal: Uncover why adoption stalled and agree a smaller, realistic plan that the customer is willing to renew.

  • Offering an upgrade to a happy customer

    Sales teamsBeginner

    Setup: A long-standing customer mentions during a routine check-in that their team has doubled and reports are taking longer to produce.

    Account manager:
    The higher plan includes the automated reporting they are describing, at a noticeably higher price.
    Finance team lead:
    You are satisfied with the current plan and wary of anything that sounds like an upsell.

    Goal: Connect the upgrade to the problem the customer raised themselves, and let them ask for the price before you give it.

  • The champion who went quiet

    Sales teamsIntermediate

    Setup: Your main contact was enthusiastic, asked for a proposal, then stopped replying three weeks ago. They finally pick up the phone.

    Account executive:
    You need to find out what changed without making the contact feel chased or guilty.
    Product manager:
    Your budget was frozen and you are embarrassed that you did not say so.

    Goal: Make it easy for the contact to tell you the truth, then agree whether to pause, reshape the proposal or close the file.

  • Negotiating a discount with procurement

    Sales teamsAdvanced

    Setup: The business side has chosen your product. Procurement now takes over and opens by asking for 25 percent off and 90-day payment terms.

    Sales director:
    You can offer a multi-year price lock or a modest discount for annual prepayment, but not both.
    Procurement lead:
    Your bonus depends on documented savings, and you have a deadline at the end of the month.

    Goal: Trade concessions instead of giving them away: every movement on price is matched by something the buyer gives in return.

  • Turning away a lead that is not a fit

    Sales teamsBeginner

    Setup: A sole trader fills in the contact form for software that is built and priced for companies with fifty or more staff.

    Sales development rep:
    You have to be honest that the product will be too much for them, and you want them to leave with a good impression.
    Freelance designer:
    You are excited, have already watched the product video and do not understand why you would be turned away.

    Goal: Decline clearly within the first two minutes and point the person toward the kind of tool that would suit them.

  • Asking for feedback after losing a deal

    Sales teamsIntermediate

    Setup: After a four-month evaluation, the prospect emails to say they chose another vendor. They agree to a ten-minute call.

    Account executive:
    You want to learn what decided it, and you must not reopen the pitch.
    Head of operations:
    You feel slightly guilty and will give vague answers unless asked specific questions.

    Goal: Leave with two specific reasons for the loss and the prospect's agreement to be contacted again in a year.

Customer service roleplay scenarios

Ten calls and counter conversations where the policy and the customer's wishes do not line up. The skill being practiced is staying useful while saying something unwelcome.

  • Refund request outside the return window

    Support teamsBeginner

    Setup: A customer wants to return headphones bought 45 days ago. The policy allows 30 days and the item has been used.

    Support agent:
    You cannot give a refund, but you can offer a repair under warranty or a store credit of half the price.
    Customer:
    You were traveling for work and think the 30-day rule is unreasonable.

    Goal: State the limit once, clearly, then spend the rest of the conversation on what you are able to do.

  • Third call about the same fault

    Support teamsIntermediate

    Setup: A customer's internet has dropped out every evening for two weeks. This is their third call, and two earlier agents promised a fix.

    Support agent:
    You can see the earlier notes and can book an engineer visit, with the earliest slot three days away.
    Customer:
    You work from home, have repeated your story twice already and expect to be let down again.

    Goal: Show that you have read the history so the customer does not repeat it, and commit only to steps you personally control.

  • Parcel arrived damaged

    Support teamsBeginner

    Setup: A customer receives a ceramic lamp in pieces. It was a birthday present and the birthday is in two days.

    Support agent:
    A replacement takes four working days; you can offer a refund now or an express replacement at no charge if stock allows.
    Customer:
    You are more upset about the missed birthday than about the money.

    Goal: Acknowledge the deadline before the logistics, then give the customer a clear choice between two options.

  • "I want to speak to your manager"

    Support teamsIntermediate

    Setup: Thirty seconds into a call about a double charge, the customer demands a supervisor before you have asked a single question.

    Support agent:
    You have the authority to fix a double charge yourself, and a supervisor callback takes 24 hours.
    Customer:
    A previous agent hung up on you, and you now assume front-line staff cannot help.

    Goal: Offer the escalation honestly, and also show that you can solve the problem in this call if the customer allows it.

  • Explaining a price increase

    Support teamsIntermediate

    Setup: A subscriber of four years calls after seeing that their monthly fee has gone up by 15 percent.

    Support agent:
    You cannot reverse the increase, but you may offer a cheaper plan with fewer features or a one-time loyalty credit.
    Long-term customer:
    You feel that loyalty has been punished and you mention switching to a competitor.

    Goal: Explain the change without reading out a script or sounding defensive, and make sure the customer knows every option open to them.

  • Guiding a non-technical customer through a setup

    Support teamsBeginner

    Setup: A customer has bought a wireless printer and cannot connect it. They describe themselves as "hopeless with computers".

    Support agent:
    You need to talk them through six steps over the phone without being able to see their screen.
    Customer:
    You are apologetic and anxious, and you tend to press buttons before the instruction is finished.

    Goal: Give one instruction at a time, check what the customer sees after each step and avoid technical terms altogether.

  • A billing error that is the company's fault

    Support teamsBeginner

    Setup: Because of a system fault, a customer was charged three times for an annual plan, and their bank account is now overdrawn.

    Support agent:
    You can trigger the refunds, which take three to five working days, and you can request compensation for bank fees.
    Customer:
    You are stressed about rent due this week and want the money back today.

    Goal: Apologize without excuses, give exact timings and explain what the customer can show their bank in the meantime.

  • A customer who wants to cancel

    Support teamsIntermediate

    Setup: A customer calls to cancel a gym membership. Your team is expected to make one retention offer before processing it.

    Membership adviser:
    You may offer a three-month freeze or a lower-priced off-peak plan, once.
    Member:
    You have moved house and simply want to cancel without a sales conversation.

    Goal: Ask the reason, make the single offer if it is relevant and process the cancellation without making the customer ask twice.

  • You do not know the answer

    Support teamsBeginner

    Setup: A customer asks whether a software export will keep custom fields when moving to a new account type. You have never been asked this.

    Support agent:
    You must not guess, and the specialist team replies to internal questions within four hours.
    Customer:
    You are migrating data tomorrow morning and need certainty.

    Goal: Say plainly that you do not know, explain how and when you will find out and agree how the answer will reach the customer.

  • A customer who becomes abusive

    Support teamsAdvanced

    Setup: A customer whose flight was canceled starts shouting and insulting the agent personally at the service desk.

    Service desk agent:
    You can rebook them on the next available flight, and your employer's policy lets you end an abusive conversation after one warning.
    Passenger:
    You have missed a family event and are taking it out on the nearest person.

    Goal: Separate the complaint from the behavior: keep solving the rebooking and give one calm, specific warning about the language.

Difficult conversation roleplay scenarios

Conversations between colleagues where the relationship has to survive the conversation. Have the person playing the other role push back at least twice.

  • Telling your manager you are overloaded

    Anyone at workBeginner

    Setup: You have been given a third urgent project this month. The first two are behind schedule and you worked the last two weekends.

    Employee:
    You want to stay on good terms with your manager and need one project moved or re-scoped.
    Manager:
    You are under pressure from above and tend to answer with "I know, everyone's stretched".

    Goal: Present the workload as a prioritization choice for the manager to make, and leave with one project explicitly deprioritized.

  • A colleague presents your work as their own

    Anyone at workIntermediate

    Setup: In a leadership meeting a teammate presented the analysis you built and did not mention you. You ask to speak with them afterwards.

    Analyst:
    You want credit corrected and you still have to work with this person every day.
    Senior teammate:
    You did not think it mattered who presented it and feel accused.

    Goal: Describe what happened and its effect without calling the colleague a thief, and agree how shared work will be credited from now on.

  • A peer keeps missing handover deadlines

    Anyone at workIntermediate

    Setup: You depend on a colleague's data every Thursday. For the past four weeks it has arrived on Friday afternoon, pushing your own work into the weekend.

    Project coordinator:
    You are their peer, not their manager, and you would rather fix this without escalating.
    Data specialist:
    You are covering for a vacancy on your own team and had not realized anyone was affected.

    Goal: Make the consequence visible and agree a new handover time that both of you can keep.

  • Disagreeing with your manager's decision

    Anyone at workIntermediate

    Setup: Your manager has decided to launch a feature next week. You believe a known bug will generate a wave of support tickets.

    Product specialist:
    You have ticket data from the last similar launch and you accept that the final decision is theirs.
    Manager:
    You have promised the date to a client and hear objections as delay.

    Goal: State the risk with evidence, propose one alternative and make clear that you will support whichever decision is made.

  • Asking a colleague to stop interrupting you

    Anyone at workBeginner

    Setup: In the weekly team meeting the same colleague has cut you off mid-sentence three times. You catch them alone afterwards.

    Team member:
    You believe it is habit and not malice, and you want it to stop.
    Colleague:
    You think of interrupting as enthusiasm and are surprised anyone minds.

    Goal: Name the specific behavior and one occasion, and ask for one concrete change in the next meeting.

  • Owning up to a costly mistake

    Anyone at workIntermediate

    Setup: You sent a pricing sheet with an old discount to a client, who has now signed at the lower price. The difference is several thousand.

    Account coordinator:
    You discovered the error yourself this morning and have an idea for preventing it in future.
    Department head:
    You dislike surprises and your first question will be "How did this happen?"

    Goal: Report the mistake before being asked: what happened, what it costs, what you have already done and what you recommend.

  • Saying no to a senior stakeholder

    Anyone at workAdvanced

    Setup: A vice president from another department asks you, on a Thursday afternoon, for a custom report by Monday. Your own deadline is also Monday.

    Analyst:
    You can deliver a simpler version by Monday or the full report by the following Thursday.
    Vice president:
    You are used to people saying yes and you mention that your own boss is waiting.

    Goal: Decline the request as stated while offering two workable alternatives, and hold the position after the first push.

  • Responding to a rude comment

    Anyone at workIntermediate

    Setup: During a team lunch a colleague jokes about your accent in front of others. People laugh awkwardly. You speak to them later that day.

    Team member:
    You want them to understand that it was not harmless, without turning it into a formal complaint.
    Colleague:
    You meant it as friendly teasing and your first reaction is "I was only joking".

    Goal: Explain the effect of the remark in your own terms and get a clear acknowledgment, without needing the colleague to feel like a bad person.

  • Asking for a raise

    Anyone at workIntermediate

    Setup: You have been in your role for two years, took over a departed colleague's responsibilities six months ago and have had no pay review.

    Employee:
    You have a list of three results from the past year and a target figure in mind.
    Manager:
    You value this person, but the budget cycle closed last month.

    Goal: Make the request with a specific number and reasons, and if the answer is "not now", leave with a date and the criteria for a yes.

  • Telling a client the project will be late

    Anyone at workAdvanced

    Setup: A website build promised for the first of the month will be three weeks late because a key developer has left.

    Project manager:
    You have a revised plan and can deliver the most important section on the original date.
    Client:
    You have a product launch tied to the original date and have already told your own director it was on track.

    Goal: Deliver the bad news in the first minute, take responsibility and get the client's agreement to a revised plan.

Management and feedback roleplay scenarios

For new and experienced managers. Most of these go wrong in the first sixty seconds, so rehearse the opening line until it is direct and kind.

  • Feedback for an underperformer

    ManagersIntermediate

    Setup: A team member's reports have contained errors for two months, and a client noticed the latest one.

    Manager:
    You have three specific examples and want improvement, not a resignation.
    Team member:
    You feel you were never trained properly and expect to be blamed.

    Goal: Describe the pattern with examples, ask for the employee's view and agree two measurable changes with a review date.

  • Telling someone they did not get the promotion

    ManagersAdvanced

    Setup: A strong team member applied for a team lead role. An external candidate has been chosen and will be their new boss.

    Manager:
    You want to keep this person and can explain the two areas where the other candidate was stronger.
    Senior specialist:
    You believed the job was yours and you are wondering whether to leave.

    Goal: Give the decision in the first sentence, give honest reasons and discuss what would make the next application succeed.

  • First one-to-one with a former peer

    ManagersIntermediate

    Setup: You were promoted last week. Your first one-to-one is with a friend who has sat next to you for three years and also wanted the role.

    New manager:
    You want to acknowledge the awkwardness and establish how you will work together.
    Former peer:
    You are pleased for your friend and also resentful, and you test the boundary with jokes.

    Goal: Name the change in the relationship openly and agree one or two ground rules for feedback in both directions.

  • Making a role redundant

    ManagersAdvanced

    Setup: Because of a restructure, a role on your team is being eliminated. The decision is final and HR has prepared the terms.

    Manager:
    You must deliver the news clearly, cover the practical details and not debate the decision.
    Employee:
    You have been with the company six years and your first reactions are shock and "Why me?"

    Goal: Say the decision in the first thirty seconds, give the person room to react and make sure they leave knowing the next three steps.

  • Mediating between two team members

    ManagersAdvanced

    Setup: Two colleagues have stopped speaking after a disagreement over who owns a client account. Work is falling between them.

    Team manager:
    You are meeting them one after the other and need to hear each side without choosing one.
    Account manager:
    You believe the other person went behind your back and you want the manager to rule in your favor.

    Goal: Get each person to describe the problem in terms of work, not character, and to name one thing they need from the other.

  • A high performer who is burning out

    ManagersIntermediate

    Setup: Your most reliable team member has become short-tempered and has been sending emails at midnight. They insist they are fine.

    Manager:
    You want to reduce their load without making them feel demoted.
    Team member:
    You take pride in never dropping anything and hear concern as criticism.

    Goal: Raise what you have observed, without diagnosing, and agree one piece of work that will be handed over this week.

  • Announcing an unpopular change

    ManagersIntermediate

    Setup: Leadership has decided the team will move from two office days a week to four, starting next month. You personally have mixed feelings.

    Manager:
    You must explain the decision to your team, answer questions and not undermine it.
    Team member:
    You arranged childcare around the current pattern and ask "Do you actually agree with this?"

    Goal: Explain what is changing, what is not negotiable and what is, and answer the personal question honestly without blaming leadership.

  • Addressing repeated lateness

    ManagersBeginner

    Setup: An otherwise good employee has arrived twenty to thirty minutes late for the morning shift six times this month.

    Shift supervisor:
    Colleagues are covering the gap and have started to complain.
    Employee:
    A change in a bus timetable is behind it and you were hoping nobody had noticed.

    Goal: State the facts and the effect on the team, ask what is behind it and agree a specific arrangement.

  • Delegating a stretch task

    ManagersBeginner

    Setup: You want a capable but cautious team member to lead next month's client workshop, which you have always run yourself.

    Manager:
    You believe they are ready and you are prepared to coach them through the preparation.
    Team member:
    You are afraid of failing in front of a client and suggest someone else do it.

    Goal: Explain why you chose them, define what a good result looks like and agree the support they will get before the day.

  • Responding to a resignation

    ManagersIntermediate

    Setup: A valued employee asks for five minutes and tells you they have accepted another job.

    Manager:
    You are surprised and need to decide on the spot whether to explore a counter-offer.
    Employee:
    You have already signed and want to leave on good terms.

    Goal: Respond without guilt or panic, find out the real reason for leaving and agree a handover plan.

Meeting and presentation roleplay scenarios

Short exchanges that happen in front of other people, where there is no time to prepare an answer.

  • Stand-up update when you are blocked

    Anyone at workBeginner

    Setup: At the daily stand-up you have to report that your task has not moved for two days because another team has not given you access.

    Developer:
    You do not want to sound as if you are blaming anyone, and you need help.
    Team lead:
    You want a thirty-second update and a clear request.

    Goal: Give yesterday, today and the blocker in under thirty seconds, with a specific request to a named person.

  • Presenting bad numbers to leadership

    Anyone at workAdvanced

    Setup: Quarterly sign-ups are 18 percent under target. You have ten minutes with the leadership team to explain it.

    Marketing lead:
    You know two causes for certain and are unsure about a third.
    Chief executive:
    You interrupt after the first slide with "So whose fault is this?"

    Goal: Open with the number, separate what is known from what is not and finish with the decision you need from the room.

  • Pushing back on scope at a kickoff

    Anyone at workIntermediate

    Setup: At a project kickoff the client adds two "small" features to a plan whose budget and date are already fixed.

    Project lead:
    You want to keep the client's goodwill and you cannot absorb the extra work.
    Client sponsor:
    You assume small additions are included and say "It shouldn't take long, should it?"

    Goal: Acknowledge the request, explain what it would displace and offer the client a choice between scope, date and cost.

  • Introducing yourself to a new project team

    Anyone at workBeginner

    Setup: You join a cross-functional project in its third week. The lead asks you to introduce yourself to eight people you have never met.

    New team member:
    You have forty-five seconds and want people to know what to come to you for.
    Project lead:
    You follow up with "And what will you need from us?"

    Goal: Cover your name, your role, one piece of relevant experience and one thing you will be responsible for, with no rambling.

  • A hostile question after your presentation

    Anyone at workAdvanced

    Setup: You have just presented a proposal to change the team's planning process. A senior colleague says, "We tried this three years ago and it was a disaster."

    Presenter:
    You were not at the company three years ago and did not know about the earlier attempt.
    Senior colleague:
    You led the earlier attempt and still feel bruised by it.

    Goal: Thank the questioner, ask what went wrong last time and show how the proposal differs, without becoming defensive.

Interview and career roleplay scenarios

Rehearse these aloud. An answer that reads well on paper often runs a minute too long when spoken.

  • "Tell me about yourself" on a screening call

    Anyone at workBeginner

    Setup: A recruiter opens a twenty-minute phone screen for a project coordinator role with the standard first question.

    Candidate:
    You have five years of experience across two industries and tend to recite your whole CV.
    Recruiter:
    You have six more calls today and will cut in after ninety seconds.

    Goal: Answer in sixty to ninety seconds: present role, one relevant achievement and why this job.

  • A behavioural question about conflict

    Anyone at workIntermediate

    Setup: The hiring manager asks, "Tell me about a time you disagreed with a colleague and how you handled it."

    Candidate:
    You have a real example, in which you were partly in the wrong.
    Hiring manager:
    You follow up with "What would you do differently now?"

    Goal: Tell the story in under two minutes with a clear situation, action and result, and include what you learned.

  • The salary expectations question

    Anyone at workIntermediate

    Setup: Near the end of a first interview, the interviewer asks what salary you are looking for. The posting did not include a range.

    Candidate:
    You have researched the market and have a range in mind, and you do not want to anchor too low.
    HR partner:
    You have an approved range and prefer the candidate to give a number first.

    Goal: State a researched range calmly, or ask for the role's range first, and avoid apologizing for the figure.

  • Explaining a gap in your employment

    Anyone at workIntermediate

    Setup: The interviewer notices an eleven-month gap on your CV and asks about it directly.

    Candidate:
    You took the time to care for a family member and are worried it looks like a weakness.
    Interviewer:
    You are neutral and mainly want to know that the candidate is ready to return.

    Goal: Give a short, factual explanation in two or three sentences and move to what makes you ready for this role now.

  • Informational coffee chat with someone senior

    Anyone at workBeginner

    Setup: A director at a company you admire has agreed to a twenty-minute coffee after a mutual contact introduced you.

    Early-career professional:
    You would like advice and, eventually, a referral, and you know that asking for a job outright would be a mistake.
    Director:
    You are happy to help and you dislike vague questions such as "Can I pick your brain?"

    Goal: Ask three specific questions, keep to the time agreed and end by asking who else the director suggests you talk to.

No roleplay partner? Let the AI play the other role

In SayNow AI you choose a scenario such as a job interview, a salary negotiation or a difficult conversation, and the AI plays the other person in a live voice conversation. Afterwards you get scores and suggestions on fluency, structure, fit for the situation and whether you reached your goal.

Free to download · iOS and Android

How to run a workplace roleplay session

This format works for pairs, for a team of up to about twelve split into threes, or for one person rehearsing alone.

  1. Brief the roles separately

    Give each player only their own brief. The person practicing should discover the other side's motive during the conversation, as they would in real life.

  2. State the goal before starting

    Read the goal aloud. It turns "have a conversation" into something that can be judged: did the customer hear a clear choice, did the manager leave with one project deprioritized?

  3. Add an observer where you can

    In a group of three, the third person writes down exact phrases that helped or hurt. "When you said 'as I already explained', she crossed her arms" is more useful than "good job".

  4. Debrief in a fixed order

    The person practicing speaks first (what worked, what they would change), then the partner (how it felt on the receiving end), then the observer. Keep it to two minutes.

  5. Repeat with one change

    Run the same scenario again with one adjustment: a different opening line, a slower pace, or the question that was missed. Then swap roles.

Frequently asked questions

What is a workplace roleplay scenario?
A short written situation in which two people act out a work conversation in order to practice it. A usable scenario states the setting, tells each person who they are and what they want, and sets a goal for the person practicing.
What are good sales roleplay scenarios?
The ones your team meets every week: getting past a gatekeeper on a cold call, a prospect who only wants the price, a competitor's cheaper quote, a renewal with low usage and a negotiation with procurement. The sales section above has ten, from beginner to advanced.
Which customer service roleplay scenarios should new agents start with?
Start with situations where the agent has something to offer, such as a damaged parcel or a company billing error, so they can practice acknowledging the problem and giving clear options. Leave abusive customers and repeat contacts until the basics are steady.
How long should a roleplay last?
Four to six minutes for the conversation and two minutes for feedback is enough for most scenarios. Longer rounds tend to drift away from the goal. Running a short scenario twice teaches more than running a long one once.
How do I make a difficult conversation roleplay feel realistic?
Use real details from your workplace, give the other role a private motive, and ask them to respond the way the real person would, including defensiveness or silence. Agree beforehand that anyone can pause the scene if it becomes uncomfortable.
Can I practice roleplay scenarios alone?
Yes. You can speak both parts aloud, record yourself delivering the opening and listen back, or use an app in which an AI plays the other role. SayNow AI offers scenarios including job interviews, salary negotiation and difficult conversations as live voice conversations with feedback afterwards.

Related