Assaf Barnir · The Support Machine · Second Edition
The machine, drawn out
Six operating gates and four supporting ideas, drawn in black and white. Each figure also appears beside its discussion in the book.
Diagnose the queue
Read a sample of customer questions and distinguish product behavior, hard-to-find answers, repeatable tasks, and work needing human investigation.
Choose the machine
A support system has several layers. Buy, extend and build remain options at each layer; each component still needs funded operating ownership.
Design the guardrails
The answer path uses applicable evidence. The action path separately checks permission, executes, and verifies a receipt. Missing evidence or authority leads to a stop or human handoff.
Shadow-run the machine
Give a human reference review and an isolated candidate run the same request-time evidence. Compare the results; the candidate has no live messaging or write capability.
Launch with direct accountability
Readiness checks lead to a bounded cutover and observation. Evidence supports continuing; stop conditions route to containment and a staffed human service path.
Operate the living system
Customer evidence moves through review, an accountable owner, a tested change, release, and a later outcome check. The evidence feeds the next iteration.
The 16% problem
Of 100 eligible conversations, an agent is involved in 40. If 40 percent of those 40 are reported resolved, that is 16 of the original 100. These are illustrative counts, not company results.
Evaluation over time
Check related returns seven and thirty days after reported resolution. Each denominator needs a mature observation window and known coverage. Weekly independent answer review runs on a separate track.
When the effect is unknown
An authorized attempt can leave an uncertain effect. Inspect provider state or assign a human owner before deciding what to retry. If a credit succeeded but its confirmation failed, recover the message without issuing another credit.
From goalkeeper to midfield
Support engineers keep a staffed human recovery path and spend protected time improving documentation, product behavior and onboarding to prevent repeated customer problems.
