A client escalation on your third month at work
You are three months into your first job. A client contact at a mid-sized company has called about a report that went out with wrong figures yesterday. They have already emailed your manager once. You did not make the mistake, but you are the one on the call, and "let me check with my team" said four times is what turns an annoyed client into an escalated one.
An advanced-level session of about 8 minutes.
They mention it early, almost in passing: they have already emailed your manager. It is not really information, it is a test of what you do next. Three months in, the instinct is to reach for the manager, for the process, for an explanation of how figures are normally checked, and each of those gets cut off halfway through. What the client needs first is evidence that the person on the phone has understood the size of the problem in their terms. The mistake was not yours, which makes this harder rather than easier. You will want to make that clear, and the sentence that does it, however carefully you phrase it, is the one that turns a difficult call into a complaint.
Angles worth taking
- When you are interrupted, stop mid-sentence and let them finish, because talking over an interruption is what escalates the call.
- Do not name the colleague, even when asked directly; saying it came from your side costs you nothing and holds.
- Deal with what the wrong figures cost them before you say anything at all about how the error happened.
- If you genuinely do not know something, say so in a short sentence, since vagueness is what they are reacting to.
- Ask whether the report has already gone anywhere else, because the answer changes what has to happen in the next hour.
- A client repeating a point they already made is telling you your first answer landed as process, not as understanding.
Who is in the room
You play
A junior associate handling the client call alone
You speak with
A client contact who is frustrated, mentions early that they have already written to your manager, and interrupts any answer that sounds like a process explanation
Phrases to reach for
These are shown to you before the session starts. They are what you are asked to use, not a list the scorer is checking off.
Ready to speak?
Free to start. You need a TalkDrill account to speak — reading this page does not.
Browse all roleplay scenariosThe format
Modes
Learn (guided) · Mock (exam-real)
How a roleplay session works
Read your brief
Your role, the situation, and what a good outcome looks like. The counterpart has their own brief, and you do not get to read it.
Open the conversation
You speak first in most scenarios. How you open sets what you can ask for later, which is most of the exercise.
Handle the turn
Somewhere in the middle it stops going your way — a refusal, a counter-offer, a rebuttal you did not prepare for. That moment is the scenario.
Read the report
Outcome, the phrases you used and the ones you missed, fluency and clarity, and the specific line worth rewriting.
What you're scored on
Across every roleplay, the report looks at the same four things — because they are what makes a real conversation work or fail.
Take ownership without blaming a colleague, acknowledge the actual impact on them, give one concrete commitment with a time on it, and end the call with the client knowing exactly what happens next.
Task outcome
Whether you got what the brief asked for: the refund, the extension, the concession, the point conceded.
Appropriacy
Whether the register fits. A complaint that is too soft gets nothing; the same complaint too hard gets a manager and no refund.
Recovery
What you do with the unexpected turn — repair, rephrase, push back, or stall. This is where most of the marks move.
Delivery
Fluency, pronunciation and pace, judged in conversation rather than in a prepared monologue.
More roleplay scenarios
All roleplay scenarios · Placement scenarios · All speaking practice