Situational judgement and customer-service orientation
Domain 5 - Situational judgement and customer-service orientation
Scenarios drawn from counter, telephone and depot work. You choose the best and worst response, or rank several. There is a defensible hierarchy behind the scoring, and the "friendliest" option is rarely the best one.
Core rules and concepts
- Priority order: safety and legality, then data protection and accuracy of information, then resolving the customer's problem, then speed, then cost.
- Never disclose customer data or confirm whether a person lives at an address. Offer the official route instead.
- Acknowledge, clarify, act, confirm: name the problem, ask the two or three questions you actually need, state what you will do and by when, give a reference.
- Do not promise what you cannot control - a specific delivery hour, or a refund before an investigation has an outcome.
- Escalate when the request exceeds your authority, but not as a first move.
- Keep the register formal: "Sie", complete sentences, no blame aimed at colleagues or at the customer.
Worked example
A customer says a parcel shows as delivered but nothing arrived, and becomes loud at the counter.
Best response: stay calm, apologise for the situation, verify the delivery address and details, explain the standard next step (a search request, Nachforschungsauftrag, quoting the tracking number) and give a reference plus a timeframe. This resolves the problem through the correct channel and commits only to what you control. Weak but tempting: "I'm sorry, I'll pass it on" - polite, no action, no reference. Worst: naming the driver as responsible, reading out from the screen where the parcel is, or promising a refund today.
Traps that cost marks
- Choosing the empathetic option that contains no concrete action.
- Options that solve the problem by breaking a rule - disclosing data, waiving a fee without authority.
- Escalating immediately, which reads as unwillingness to help.
- Matching the customer's emotional tone; the scoring rewards calm structure.
- Missing a second problem embedded in the scenario (a damaged item and an unsigned receipt).