The expert is a single point of failure
Every support team has the person who "just knows" — billing edge cases, the legacy feature, the workaround for that one browser. It feels like an asset; it is a liability with a nice personality. The day they are on vacation, every conversation touching their territory stalls. Knowledge sharing for a small team is not a wiki project — it is a set of small habits that move answers out of heads.
The rule: discovered once, written once
When an agent figures something out mid-chat — digs through settings, asks the expert, finds the workaround — the conversation is not done until the answer is written where the NEXT agent will find it. Three destinations, by audience:
- Customers would ask this again → a help-center article (which also becomes AI training material — write once, deflect twice).
- Agents will need this phrasing again → a shared canned response, the team's working memory.
- Internal-only nuance (when to refund, whom to escalate to) → the team playbook doc, one page, ruthlessly current.
Transcripts are the apprenticeship
The expert's transcripts ARE the training course nobody wrote. Point newer agents at them deliberately: "read Maya's last ten billing conversations" transfers judgment — how she words the policy, when she bends, how she says no — in a way no document does. This is the same mechanism as onboarding, applied continuously.
Run the bus-factor audit quarterly
List your top ten conversation topics. For each, ask: how many people on this team can resolve it without help? Every topic with an answer of "one" is scheduled deliberately — the expert writes the playbook page, and the next occurrence of that topic routes to someone else with the expert as backup. Uncomfortable for a week; existential insurance forever.
Let the tools carry what they can
A shared canned library means the best phrasing is everyone's phrasing. A knowledge base means the documented answer outranks the remembered one. An AI assistant trained on those articles means the "expert" for the repetitive tier is software that never takes vacation. What remains in human heads should be judgment — and judgment is exactly what the transcripts teach.