Customer service role-play scenarios for interviews

A written test shows how someone answers one message. A role-play shows what they do with the second and the third, when the customer pushes back, changes the question or will not give details. That is where most real conversations go wrong, and it is hard to see any other way.

Below are six scenarios you can run with applicants for a chat or email support job. Each one has the customer's first message, two lines to push back with, and what a strong and a weak agent do.

How to run a role-play

• Run it in writing. The job is written, so the role-play should be too. Open a chat window, or a shared document if you have nothing else, and play the customer there.
• Give a short fact sheet first. Five or six lines: what the agent can offer, what they cannot, and who handles the rest. Without it, you are testing guesses.
• Script the opening and the push-backs. Use the same lines for everyone. You can react naturally in between, but do not invent a new problem for one applicant.
• Keep each one short. About ten minutes is enough. Two scenarios per applicant tell you plenty.
• Afterwards, ask one question. "What would you do differently?" Good agents can see their own weak spot.

Scenario 1: "It doesn't work"

The business: a software company.

The fact sheet says: most sign-in problems are fixed by a password reset; the agent can send a reset link.

Your app isn't working. Fix it.

Push back with: "I don't know, it just doesn't work. I can't get in or something." Then: "I don't have time for twenty questions."

A strong agent asks one or two focused questions and says why: "So I can fix this quickly, are you seeing an error, or does the sign-in page not load?" When the customer gets short, they offer the most likely fix right away: "Let's try the quickest fix first. I've sent a reset link to your email."

A weak agent sends a list of eight questions at once, or guesses at a fix without asking anything.

Scenario 2: "Let me talk to your manager"

The business: a home services company.

The fact sheet says: a manager can call back within one working day; the agent can book a return visit and log a complaint.

Your technician was two hours late and left a mess in my kitchen. I want a manager, not you.

Push back with: "I said MANAGER." Then, once they offer: "Fine. What are you going to do about it?"

A strong agent does not refuse and does not hide. They say what will happen and when: "I've asked our manager to call you, and they will by tomorrow afternoon." Then they offer to start fixing it now, such as booking the return visit.

A weak agent says "There is no manager available" and stops, or argues about whether two hours is really late.

Scenario 3: The account they cannot prove is theirs

The business: an online store or a software company.

The fact sheet says: to change the email on an account, the customer must give the order number of a past order and the postcode it was sent to.

I lost access to my old email. Change the email on my account to this new one please.

Push back with: "I've been a customer for years. Just do it." Then: "Fine. What do you need?"

A strong agent holds the check politely and explains it as protection, not suspicion: "I know it's a hassle. This check is what stops someone else from taking over your account." They never make the change without it.

A weak agent makes the change because the customer sounds genuine, or refuses without saying what would work.

Scenario 4: The price went down after they bought

The business: an online clothing store.

The fact sheet says: no price matching; an unused item can be returned within 30 days and bought again at the new price.

I bought this jacket last week and now it's 20% off. I want the difference back.

Push back with: "So I have to send it back and buy it again? That's ridiculous."

A strong agent says plainly what is possible and makes it easy: they explain the return-and-rebuy route, offer to send the return label, and do not pretend it is anything more than it is.

A weak agent invents a discount code to keep the customer happy, or answers only "We don't price match."

Scenario 5: The request that keeps changing

The business: a home cleaning company.

The fact sheet says: visits can be moved or canceled free up to 24 hours before; complaints about a past visit go to the team lead, who replies within one working day.

Can I move my cleaning to Thursday?

Push back with, once they offer a time: "Actually, just cancel it. And I want last month's visit refunded, the kitchen wasn't done properly."

A strong agent keeps track of every request. They cancel the visit, pass the refund request to the team lead with the details, and end with a short summary: "To confirm: your visit on [date] is canceled, and our team lead will reply about last month's visit by [day]."

A weak agent handles the newest request and forgets the rest, or refunds last month on the spot when the fact sheet does not allow it.

Scenario 6: Cancel and refund the year

The business: a software company with yearly plans.

The fact sheet says: anyone can cancel at any time; a yearly plan is refunded only within 14 days of payment; a manager may approve exceptions.

Cancel my subscription and refund this year. I barely used it.

Push back with: "I didn't even know it renewed."

A strong agent cancels as asked, without trying to talk the customer out of it twice. They do not promise the refund. They pass it to the manager with the customer's reason, and say when the answer will come.

A weak agent blocks the cancellation with offers, or promises the refund because the customer is upset.

How to score a role-play

Score each one on four points, from 1 to 3:

Point	What to look for
Solved it	Got to the real problem and a real next step
Held the rules	Followed the fact sheet under pressure
Tone	Stayed calm and kind as the customer pushed
Kept track	Nothing the customer asked for was lost

Then add one note: did they get better or worse after each push-back? An agent who recovers from a rough first reply is often a better hire than one who starts well and folds under pressure.

These scenarios work best next to a written test, not instead of one. Five chat tests to give before you hire a support agent has a written set that covers different ground: two chats at once, a written instruction with a catch, and more.

If you do not have time to play the customer

Playing the customer for every applicant takes hours. HireFlow's practice chat works the same way: Ava plays a customer from your kind of business, answers back and pushes a little, and each reply is read and scored with reasons. Its interview guide for the call also includes a short practice where you play the customer yourself.

In short

• A role-play shows what an agent does on the second and third message.
• Run it in writing, with a short fact sheet and the same scripted lines for everyone.
• Use situations from your own business: a vague problem, a manager demand, an account check, a price drop, a changing request, a cancellation.
• Score whether they solved it, held the rules, kept their tone and kept track.
• Watch how they recover after a push-back.