6.1Case studies
The essentials in 30 seconds
- Assemble: a real case mobilizes the whole chain — listen, qualify, handle with dates, call back, measure.
- Order: understand first (listening, 4Qs, locked-in summary), handle next (A/B choice, dated milestones), prove last (callback, review, indicators).
- Reflex: faced with a customer situation, replay the levels' sequence in order instead of treating an isolated symptom.
Rania thread — 1 year on: two files that hold
One year after levels 0 to 5, Rania re-reads her two landmark files: the lost parcel turned into a 5-star review, and the switchboard unclogged in 3 months thanks to self-service. Both cases below reuse her sequence: locked-in listening and A/B choice on one side, Pareto and pilot PDCA on the other, check-back calls in both cases.
Each case follows Context → Steps → Result: replay it on your own service.
Why case studies
The previous levels laid the bricks; here we assemble them end to end. It is the chaining of the right reflexes — listening, qualifying, dated handling, callbacks, measuring — that separates a service that builds loyalty from a switchboard that merely copes.
Case 1 — Lost parcel turned into a 5-star review
Context: E-shop: parcel lost for an urgent gift, furious customer on the phone.
Déroulé :
- LISTEN welcome: thanks, 90 s of listening, named emotion, locked-in summary.
- A/B choice: free express reshipment OR refund + €20 → express chosen.
- SMS milestones + delivery Thursday 10 a.m. + Friday callback: everything received.
- Review requested at the peak: problem+solution story published.
Result: An ambassador who tells the story: the best-handled complaint of the year.
Case 2 — Switchboard unclogged in 3 months
Context: SME: 40% of calls “where is my order?”, CSAT 80, overwhelmed team.
Déroulé :
- Journey + Pareto: the no. 1 irritant quantified (volume × severity).
- Auto SMS + tracking page + “where is my parcel?” FAQ (2 clicks).
- PDCA pilot on 20% → calls -55%, CSAT +6 → rollout.
- Team freed up for complex cases, a 30-min weekly that decides.
Result: -35% calls, CSAT +8: self-service that frees up humans.
Ready-to-say script — request a review at the satisfaction peak (30 s)
“Everything arrived safely, perfect. Your review would help other customers — and us: would you tell in one sentence how this got fixed? I will send you the link right away.”
Copy-paste template — replayable case sheet
Customer SITUATION to handle (complaint, call peak): ...
LISTENING AND QUALIFICATION (named emotion, 4Qs, locked-in summary yes/no): ...
DATED HANDLING (A/B choice, milestones, check-back call on ...): ...
MEASUREMENT (reviews, CSAT, call volume): ...
Guide REFERENCES (L0 → L5): ...
Expected RESULT (indicator and deadline): ...Small business (2-3 people)
One case at a time, on one page: context in 2 lines, 4 steps, result in 1 sentence.
Remote / hybrid
Double traceability at a distance: written summary and dated milestones before acting, shared callback after.
Algeria SME
Build real constraints (short staffing, peaks, phone/WhatsApp channels) into each step of the case.
Cross-cultural
Check local practices before transposing a case: a channel or gesture fitting here may not fit elsewhere.
Key takeaways
- Assemble: listen, qualify, handle with dates, call back, measure.
- Turned-around complaint: listening + A/B choice + callback + review at the peak.
- Unclogged switchboard: Pareto + 2-click self-service + pilot PDCA.
- Replay the order on your cases, not the script to the letter.
48h challenge — apply tomorrow
Take 1 real situation from your service and write its 5-step sequence (listen → qualify → handle with dates → call back → measure). Test the 1st step this week.
- I can chain the reflexes in the right order on a real case.
- I have a replayable case sheet for my next situation.
- I did the 48h challenge or scheduled its date.
Frequently asked questions
Which case should I start with?
The one closest to your current situation: case 1 if you handle sensitive complaints, case 2 if your team is drowning in repetitive contacts.
Must I follow the sequence in order?
The listen → qualify → handle with dates → call back → measure order is a good default. But adapt the pace: a furious customer needs listening first, a call peak needs Pareto fast.
What if my context matches neither case?
Use the 6.2 playbook (symptom → causes → actions) to diagnose, then come back here for the sequence.
Rania's customer is furious on the phone about an urgent lost parcel. Which sequence follows the guide?