Skip to main content
Customer simulation & scenarios

Difficult customer role play: practising how to stay calm

Facing an angry customer, people either argue or promise what they cannot deliver. This guide covers five observable behaviours of calm, intensity levels, the boundaries of safe practice and a sample profile.

September 30, 20266 min read

Short answer

Practising with an aggressive, dissatisfied customer teaches employees to "stay calm" — but calm is not a feeling, it is behaviour: not interrupting, naming the emotion, separating an apology from accepting blame, asking for the facts of the problem and giving the customer a concrete next step. Trying these behaviours for the first time in front of a real angry customer is expensive; simulation lets people practise them safely.

This kind of practice also needs careful design. Below are intensity levels, the abuse boundary, the debrief after practice and a sample profile.

Why this practice is needed

A conversation with an unhappy customer is one of the most stressful moments for sales and support teams. Under pressure people fall into one of two reflexes: they get defensive and argue ("but you contacted us late"), or they over-concede and promise something they cannot deliver. Both make things worse.

Reflexes do not change through knowledge. An employee may know the rule "name the emotion", but the sentence does not come to mind when someone is shouting at them. Repeated practice makes it automatic.

Calm as observable behaviour

  1. Not interruptingWait until the customer has finished. In chat — do not answer one message with three.
  2. Naming the emotion"I can see this has really frustrated you" — not agreeing, but showing you heard.
  3. Apology versus blameYou can say "I'm sorry you've had this experience" without saying "it's our fault" before the cause is clear.
  4. Asking for factsWhat happened, when, which order or service — turning the problem into a specific task.
  5. A concrete stepWho will do what, and when the customer will hear back. No promise that cannot be kept.

Intensity levels

  • Level 1 — unhappy: the customer is disappointed and does not raise their voice, but repeats the complaint.
  • Level 2 — angry: speaks sharply, interrupts, says "there's no point talking to you".
  • Level 3 — aggressive: threatens (a complaint, a review, cancelling the contract) but does not insult.

Start new hires at level one. Level three should be practised only once behaviour is stable at the first two.

Weak and good answers

The dialogue fragments are illustrative. Customer: "This is the third time I've called, and nobody does anything!"

  • Defensive: "But our system shows only one request from you." The customer feels called a liar and tension rises.
  • Empty promise: "Don't worry, it will definitely arrive tomorrow." The date was not checked; if it does not arrive, the fourth call will be harsher.
  • Good answer: "I'm sorry you've had to call three times; that really is exhausting. Give me your order number and I'll check where it is now." After checking: "I'll get the exact date from the courier today and message you myself by 5 pm."

A sample practice profile

The profile below is illustrative.

  • Type: a customer who ordered from an online shop; delivery has been late twice.
  • Surface words: "This is the third time I've called, and nobody does anything!"
  • Real need: to know exactly when the order will arrive; it is a gift and the date matters.
  • Behaviour: level 2 — interrupts and brings up the earlier calls.
  • End condition: if the employee names the emotion, asks for the facts and gives a concrete step, the customer calms down; if they argue or make an empty promise, tension rises.
  • Standard: no interrupting, name the emotion, ask for the order details, a real step and a time to update the customer, no promise of a date that cannot be kept.

Profile fields are explained in the AI customer profile, and raising tension in layers in the objection scenario template.

After practice: the debrief

After a difficult-conversation session a score alone is not enough. A short debrief should answer three questions: at which moment did tension rise or fall; which sentence worked; how did the employee feel. The third question matters — practising with a difficult customer, even in simulation, carries an emotional load. The manager should treat that as normal, and the employee should know that practice can be stopped.

Practice and real calls

Evaluating real calls with angry customers — measuring how de-escalation happened — is a separate topic; see de-escalation with dissatisfied customers. Joining the two helps: the reaction seen most on real calls (becoming defensive, say) becomes the topic of the practice profile.

Illustrative example: a utility

This is not a real customer case. An internet provider's support team receives many angry calls on outage days. The manager notices that new staff either switch to technical explanations or say "it'll be fixed soon" without knowing when. They build two profiles: an unhappy home customer at level one, and a customer working from home and losing work at level two. The key requirement in the standard: do not promise an unknown time; instead say when updated information will be given. In the first week's reports, "soon" is the phrase most often marked as a weak answer.

Common mistakes

  • Testing new hires straight away on the most aggressive profile.
  • Writing insults and personal attacks into the profile.
  • Settling for the score and skipping the debrief.
  • Advising "stay calm" without showing the behaviour.
  • Counting an undeliverable compensation or date as a "good answer" in the standard.

Limitations

Simulation does not fully reproduce the intensity of real emotion — an AI customer's anger feels different on a screen or phone from a real person's. That is both an advantage (safety) and a limitation. Practice does not replace working conditions, shift planning and a manager's support in reducing employees' stress. Practice scores should be read especially carefully here: emotional state affects the result.

In Vexvon AI Training

In Vexvon AI Training a dissatisfied customer is built as its own profile — the intensity level in the behaviour field, the nature of the complaint in the objection list, and the behaviours above in the good call script. In chat practice, greeting and tone are a criterion of their own; in call practice, listening and not interrupting fall under communication. The employee can stop the conversation at any time, and a manager can stop a session from the panel.

Next step

Take the complaint your team hears most and write a level-one profile for it — the harsher version comes later. Other scenarios are in customer simulation and scenarios; to build your profile together, get in touch.

Further reading on this topic: active listening sales training, AI sales coaching feedback.

Live demo

Ready? Let's start

See Vexvon live in a 10-minute demo.

  • A scenario built for your business
  • A live sample call
  • A tour of the platform
Get a demoorBook a meeting

Your details are used only for the demo and to get in touch.