2.2Provide a clear & complete answer
The essentials in 30 seconds
- Cover everything, in the customer's order: take up each numbered point — a forgotten point manufactures a second contact.
- Clear = short + concrete + verifiable: short sentences, action verbs, numbers and dates (never “quickly”), proof (link, attachment, reference).
- Close with the check: “does that answer your request?” — the closing question validates and authorizes closing.
Threaded mini-case — Rania answers Karim's 3 points
Karim's well-qualified request holds in 3 points: 2 missing parcels to reship, a €30 credit for the delay, and a full refund the T&Cs (art. 7) don't allow. Rania structures her answer point by point, with dates, tracking link and attachment — including for the no, reasoned and compensated. She ends with the closing question: “does that answer your 3 points?”.
Sequel to case 2.1 — Rania's qualification makes this full answer possible.
1. Answer everything, in the customer's order
Take up each point of the request (number them if there are several), in the customer's order of importance, not yours. An answer that forgets one point creates a second contact: the "first-contact resolution" rate is decided here.
2. Clear = short + concrete + verifiable
Short sentences, action verbs ("I'll do X on Thursday"), figures and dates (not "quickly"), evidence (reference, link, attachment). Customers must be able to check: "track on [link], delivery Thursday before 12 p.m."
3. Close with a check
"Does this answer your request? Is there anything left?" The closing question validates (or reveals what was missed) and authorises closing the ticket. Without it, the case stays open in the customer's mind.
🔎 Concrete example — 🔎 Hands-on example — A 3-point answer that closes
1. Oui : 2 colis manquants → réexpédiés demain (suivi [lien]). 2. Oui : avoir de 30 € pour le retard → joint à ce mail. 3. Non : remboursement total impossible (CGV art. 7), geste proposé ci-dessus. « Cela répond-il à vos 3 points ? Puis-je clore ? »Takeaway: even the no is handled, justified, compensated.
Lesson: a no without an alternative reopens; with one, it closes.
Section vocabulary
- Clear answer
- An understandable, structured, jargon-free solution, easy for customers to follow.
Simple example: Rania numbers the 3 points with action verbs and dates.
What it is not: a slab of internal jargon Karim can't follow.
Reflex: re-read asking “would a non-specialist understand?”.
- Complete answer
- An answer handling every aspect of the request, sparing customers a follow-up.
Simple example: Rania handles even the impossible refund instead of ignoring it.
What it is not: two of three points handled, the third hushed.
Reflex: tick off each numbered point before sending.
- Actionable solution
- An answer stating steps, what will happen and deadlines, so customers know what to do.
Simple example: “Reshipped tomorrow, tracking on link, delivery Thursday before noon.”
What it is not: “we're handling it quickly”, no date or proof.
Reflex: each promise = who does what, when, verifiable where.
- Understanding check
- Making sure customers understood and their request is met (“does that answer your question?”).
Simple example: Rania closes with “does that answer your 3 points?”.
What it is not: assuming silence means agreement and closing unvalidated.
Reflex: ask the question sincerely, leaving room to answer.
- First-contact resolution
- Resolving the request in the first exchange (a key service-quality indicator).
Simple example: Karim never had to chase: everything covered and checked.
What it is not: a vague answer forcing frustrating back-and-forths.
Reflex: aim: no point forgotten, everything verifiable, close validated.
In practice — Hands-on - Provide a clear and complete answer
- Formulate a clear answer (structured, jargon-free) and a complete one (cover every aspect of the request).
- Make it actionable: explain the steps, what will happen, any deadlines.
- Check that customers understood and that their request is satisfied ("does this answer your question?").
- If it's bad news or a partial solution, deliver it tactfully and offer what can be done (positive language).
Ready-to-say script — closing a multi-point answer (1 min)
“To recap your 3 points: one, your 2 parcels are reshipped tomorrow, tracking on this link, delivery Thursday before noon. Two, your €30 credit is attached to this email. Three, a full refund is not possible under article 7 of our T&Cs — which is why I offer this gesture. Does that answer your 3 points? May I close your case?”
Say or write point by point, then wait for confirmation before closing.
Copy-paste template — complete answer that closes
POINT 1 (customer's order): answer + date + proof: _______________
POINT 2: answer + date + proof: _______________
POINT 3 / possible NO: reason (T&Cs/art.) + alternative: _______________
ATTACHED PROOF (link, attachment, reference): _______________
CLOSING QUESTION: “Does that answer your points? May I close?”Small business / low volume
Even with no template: numbering points by hand guarantees none is forgotten.
Phone
Orally, summarize aloud point by point and get confirmation before hanging up.
Email / chat
In writing, numbered bullets + clickable links + attachment: customers verify alone.
Bad news
Reasoned no (rule cited) + empathy + concrete alternative: refusals are handled like the other points.
✓ Best practices
- Every point, in the customer's order.
- Dates + proof, never "quickly".
- Closing question every time.
✗ Common pitfalls
- Forgetting one point (2nd contact).
- Vagueness ("we're on it").
- Closing without checking.
Key takeaways
- A good answer is clear (jargon-free, structured), complete (every aspect) and useful (a real solution).
- Make it actionable: steps, what will happen, deadlines — so customers know what to expect.
- Check that customers understood and that their request is satisfied (a crucial, often forgotten step).
- Maximise first-contact resolution; a vague or incomplete answer forces frustrating back-and-forth.
48h Challenge — apply tomorrow
On your next multi-point answer, number each point in the customer's order, add date + proof to each, and end with the closing question. Note whether a callback is avoided.
- I cover all points, in the customer's order.
- I make each promise verifiable (date + proof).
- I did the 48h challenge or scheduled its date.
Frequently asked questions
Why check that customers understood if they ask no questions?
Because no questions does not mean customers understood or that their request is resolved — and assuming "no questions = all good" leads to frequent misunderstandings. Customers may leave confused without daring to say so (out of embarrassment, weariness, or because they only realise afterwards they didn't grasp everything), believe they understood when they didn't, or have received an answer to only part of their request without realising it at the time. Result: they contact you again later (a costly, frustrating recontact), or worse, they stay silently dissatisfied. Checking ("does this answer your question?", "do you need anything else?", "is this clear for you?") serves two valuable purposes. First, it flushes out misunderstandings or uncovered needs while they can still be handled in the same exchange — which maximises first-contact resolution. Second, it shows customers you care about helping them through to the end, that you're not getting rid of them after "dropping" an answer — a mark of consideration they appreciate. It's a small habit (a few seconds) with an excellent benefit-to-effort ratio. Just don't do it mechanically or hastily (a "that's fine for you?" thrown out while already hanging up doesn't invite an answer): ask the question sincerely, leaving customers room to say if any doubt remains. Checking is how you neatly close the interaction and make sure the service genuinely fulfilled its role — not just that you "answered".
How do you deliver bad news or a refusal to customers?
With tact, honesty and positive language — because how you say it matters as much as the substance. A few principles. First, don't dodge or bury the bad news: customers deserve a clear, honest answer (beating around the bush, being vague or falsely reassuring breeds mistrust and even greater disappointment later). Next, explain: bad news is better accepted when it is justified ("this isn't possible because…") rather than delivered bluntly — the explanation respects customers' intelligence. Then, use positive language and point to what can be done: instead of stopping at "no" or at the impossible, offer alternatives or the best available solution ("I can't do X, but here's what I can offer you…"). Showing empathy by acknowledging possible disappointment ("I understand this isn't the answer you hoped for") helps the news land. Stay firm but courteous when a refusal is needed (section 3.4). The idea: bad news delivered well — clearly, with explanation, empathy and alternatives — is far better received than brutal, vague or dismissive bad news. Customers can accept a "no" or a constraint if they feel respected and considered in how it's presented to them. Conversely, even a small constraint announced bluntly can trigger dissatisfaction. Delivering bad news well is a key relationship skill: it preserves the relationship even when you can't give customers what they wanted.
Karim has 3 requests including an impossible refund. What does Rania do?