6.2Recurring issues (playbook)
The essentials in 30 seconds
- Reflex: one symptom = likely causes = an action sequence — diagnose before fixing.
- Root: trouble that keeps coming back almost always sits in the system (records, scripts, reviews), not in people.
- Order: start from the table's most frequent cause, then check on the job before applying the rest.
Rania thread — 1 year on: the playbook posted at the switchboard
One year on, Rania keeps this playbook near her desk. Verdict: three lines served her most — the customer repeating their story, the silent hold that enrages, and sleeping tickets. For each, she ended up fixing the root (CRM records, announced waits, SLA and daily review) instead of repeating the incident.
Observed symptom, verified causes, actions in order: the reflex holds in three steps.
One reflex per symptom
Most customer relations blockers are old classics. Linking each symptom to its likely causes and to an action sequence saves precious time.
| Symptom | Likely causes | Actions |
|---|---|---|
| Customer repeating their story | no record, transfer with no context | 3-line CRM + transfer with summary, record audit |
| Silent hold that enrages | unannounced search, no check-backs | announce + time-box + check-backs + offered callback |
| Reply missing a point | partial reading, no point-by-point | number points, answer everything, closing question |
| Delay hidden until D-day | fear of announcing, no milestones | early warning + new deadline kept + gesture |
| Rising anger | skipped listening, straight reasoning | 4 steps: welcome, listen, rephrase, propose |
| Humiliating “it's policy” | abrupt no with no reason and no alternative | empathy + reasoned no + A/B choice |
| Sleeping tickets | no priority, no owner | categories + SLA + daily review |
| FAQ generating contacts | jargon, 10 clicks, never measured | customer language, 2 clicks, measured resolution |
| Team turnover | zero power, AHT as sole judge, no debrief | gesture budget + rotation + displayed thank-yous |
Ready-to-say script — name the symptom before fixing (1 min)
“My symptom: [repeating customer / silent hold / sleeping tickets]. My no. 1 hypothesis: [the playbook's most frequent cause]. I check on records and the job, then apply the sequence. I review in two weeks.”
Copy-paste template — express diagnosis sheet
Observed SYMPTOM (facts, records, calls): ...
Since when / frequency: ...
Likely CAUSES (6.2 playbook): ...
Verification (CRM records, on-the-job listening, tickets): ...
ACTIONS (in order): 1) ... 2) ... 3) ...
Targeted SYSTEM (records, scripts, reviews): ...
REVIEW in 2 weeks: improved? stable? worse?Small business (2-3 people)
No formal table: one symptom, one cause verified on the job, one dated fix.
Remote / hybrid
Add the escalation circuit to likely causes: at a distance, an unpassed signal looks like a calm service.
Algeria SME
Build short staffing and peaks into the causes before concluding a matter of will.
Cross-cultural
Check practices (familiarity, formulas, channels) before acting: a perceived clumsiness here may be neutral elsewhere.
Key takeaways
- Diagnose (symptom → verified causes) before acting.
- Recurring trouble = a system to fix (records, scripts, reviews).
- Each action refers to the guide section to dig into.
48h challenge — apply tomorrow
Spot 1 current symptom in your service, fill the express diagnosis sheet above and test the 1st action.
- I can link a symptom to its likely causes.
- I filled (or scheduled) an express diagnosis sheet.
- I know the referral to the section to dig into for my case.
Frequently asked questions
Several symptoms at once, where to start?
With the one blocking customers or the team most (often the repeating customer or sleeping tickets). One fixed system often unlocks two others.
What if the causes are not in the table?
The table covers the classics, not everything. Listen (records, calls), observe the facts, and dig with the guide's matching section.
How long before concluding?
Test the action sequence for 2 to 4 weeks with a dated review. With no progress, change the cause hypothesis rather than insisting.
A customer must repeat their story at every handover. Which reflex does the playbook apply?
Resources
Recurring trouble is not ten incidents: it is a system to fix (records, scripts, reviews).