Customer-Service English Shadowing: Explain the Problem and Work Toward a Solution
Practise customer-service English shadowing: state the problem, check the facts, discuss possible options and confirm only the next step that is actually agreed.
State the problem in facts, check the key detail, discuss a possible next step, then confirm only what has actually been agreed.
“I need a refund” may be the outcome you want. It is not yet the problem explanation. “I’ll replace it” may sound wonderfully helpful. It is not yet a confirmed option.
Move from problem to next step, not from problem to promise: State → Check → Explore → Confirm.
State what happened before you argue for the fix
The CEFR treats complaints and service problems as real goods-and-services communication tasks. A strong opening gives the other person something concrete to work with: what happened and the identifying detail that helps locate the case.
All order numbers, products and service situations below are fictional practice.
Original practice example
I’m calling about order 4821. The parcel arrived, but the charger is missing.
The first sentence identifies the case. The second states the observable problem without guessing why it happened.
Useful when a delivery or service is incomplete and the other side needs the key facts first.
State job: identifying detail + observable problem.
Replace the order number and missing item with fictional details, then say the two-sentence problem without adding a solution yet.
Explore more language-learning guides in Media-Based Language Learning.
Check the facts before you explore the solution
British Council service role-plays use information gaps: each person has part of the situation, so clarification matters. Facts first, fixes second.
Original practice example
Just to check: the parcel arrived, but the charger wasn’t inside. Is that right?
The service side repeats the central fact back before discussing remedies. This catches misunderstandings early.
Useful when the representative needs to confirm exactly what is missing or what went wrong.
Check job: read back the problem → ask for confirmation.
Change the problem and practise one short read-back question.
Say what you want without presenting it as guaranteed
The customer can be specific about the preferred outcome without claiming that company policy has already confirmed it. A request and an entitlement are not the same thing.
Original practice example
Yes. A replacement would work for me. Could you tell me what options are available?
The speaker names a preferred outcome, then leaves room for the actual options to be checked.
Useful when you know what would solve the problem for you but do not know the company’s policy or authority.
Explore job, customer side: preferred outcome → open question.
Replace a replacement with another desired outcome, then keep the options question unchanged.
On the service side, promise the process you control
Helpful language does not require a promise-shaped sentence. If the outcome still depends on records, policy, stock, authority or another check, say what you can do now and keep the final remedy open.
Original practice example
I can check the order details now. I can’t promise a replacement yet, but I can check what options are available.
The representative commits to a process they can perform while clearly separating that from an unconfirmed remedy.
Useful when the customer asks for an outcome that still needs verification.
Explore job, service side: controlled action → honest uncertainty.
Replace order details with case notes or availability and preserve the uncertainty boundary.
Confirm the next step, not the hopeful ending
British Council problem-solving material moves from the problem into response and resolution language. When the final remedy is still unknown, the conversation can still end usefully if both people know the next action.
Original practice example
So you’ll check the order first, and then we’ll look at the available options—is that right?
The customer confirms the process that was actually agreed. The line does not turn a possible replacement into a confirmed replacement.
Useful when the service conversation has a clear next step but the final outcome is still open.
Confirm job: agreed process + remaining uncertainty.
Say the line again with a different fictional next step, such as checking case notes or checking appointment availability.
Solution Boundary Lab: label what is fact, possible and confirmed
Switch roles. Your job is not to “win” the service conversation. Your job is to reduce uncertainty without inventing policy, authority or promises.
Round 1: a missing item
Fictional situation: Order 4821 arrived, but the charger is missing. The customer would prefer a replacement. The service representative must check the order before confirming any remedy.
See one possible exchange
Fact: “I’m calling about order 4821. The parcel arrived, but the charger is missing.”
Check: “Just to confirm, the parcel arrived and only the charger was missing—is that right?”
Requested outcome: “Yes. A replacement would work for me. What options are available?”
Possible option / process: “I can check the order details now. I can’t confirm a replacement until I’ve checked.”
Confirmed next step: “So you’ll check the order first, and then we’ll look at the options—is that right?”
Round 2: a service visit did not happen
Fictional situation: A customer had a service appointment, but nobody arrived. The customer wants another appointment. The service representative does not yet know availability.
See one possible exchange
Fact: “I had an appointment this morning, but nobody arrived.”
Check: “Just to check, the appointment was for this morning and the visit didn’t happen—is that right?”
Requested outcome: “Yes. I’d like to arrange another visit.”
Possible option / process: “I can check the available times. I can’t confirm a new slot until I’ve checked.”
Confirmed next step: “Okay, so you’ll check the availability first.”
Round 3: an expected update never arrived
Fictional situation: The customer expected an update about a case but did not receive one. The service representative can check the case notes but cannot promise the final outcome.
See one possible exchange
Fact: “I was expecting an update on my case, but I haven’t received one.”
Check: “Can I confirm the case reference first?”
Requested outcome: “I’d like to know the current status and what happens next.”
Possible option / process: “I can check the case notes and tell you what information is available.”
Confirmed next step: “Great. Let’s check the case notes first.”
Correction lab: separate strong language from unsupported certainty
“I have problem with my order.”
Classification: wrong in standard English because the singular count noun needs an article here.
What a listener will probably understand: something is wrong with the order.
Likely learner intent: open a service-problem explanation.
Natural alternative: “I have a problem with my order.” or, more specifically, “There’s a problem with my order.”
Context note: the article is the grammar issue; the message becomes more useful when the next sentence names the actual problem.
“You sent me wrong product.”
Classification: wrong/non-standard because the noun phrase needs a determiner, and the wording is more accusatory than necessary for a factual opening.
What a listener will probably understand: the delivered product was not the one expected.
Likely learner intent: explain a delivery mismatch.
Natural alternative: “I received the wrong product.” or “The product I received isn’t the one I ordered.”
Context note: “You sent me the wrong product” is grammatically valid; the alternatives simply keep the opening focused on the observable mismatch rather than assigning blame.
“I want you refund me.”
Classification: wrong in standard English.
What a listener will probably understand: the customer wants a refund.
Likely learner intent: request a refund as the preferred solution.
Natural alternative: “I’d like a refund.” or, if availability/entitlement is unknown, “A refund would work for me. Could you tell me what options are available?”
Context note: correct grammar does not establish that a refund is available or owed.
“Don’t worry, I will replace it.” before checking policy or authority
Classification: grammatically valid, but contextually overcommitted when the speaker does not yet know whether replacement is available or authorised.
What a listener understands: replacement is promised.
Likely learner intent: sound helpful and reassuring.
Natural alternative: “I’ll check whether a replacement is available.” or “I can check what options are available.”
Context note: the original is appropriate only when the speaker genuinely has the authority and information to make that promise.
“We will solve this today.” when the outcome is still unknown
Classification: grammatically valid, but it makes a deadline/outcome promise that may not be supported.
What a listener understands: the problem will definitely be resolved today.
Likely learner intent: reassure the customer.
Natural alternative: “I can check the case now and tell you what the next step is.”
Context note: promise only the action, timing and outcome you are actually authorised and able to guarantee.
The five-label sprint
Choose one fictional service problem. Say five short lines without looking back: Fact → Check → Requested outcome → Possible option → Confirmed next step. Then switch roles and run it again.
Move from problem to next step, not from problem to promise
Good customer-service English does not require instant certainty. State what happened. Check what is understood. Say what outcome you want. Explore what may be possible. Then finish with the next step that is genuinely agreed. A conversation can make real progress even when the final solution still needs checking.