The Teach-Back Method: Confirming They Actually Got It
Why this matters
You explain the filter schedule, the customer nods, and three weeks later you are back on a callback because they never changed it. Nodding is not understanding. It is the universal signal for "I want this conversation to end," and techs mistake it for comprehension every day. The teach-back method fixes that by making the customer say the instruction back in their own words, on the spot, before you leave. It costs you thirty seconds and catches the misunderstanding while you can still correct it, instead of finding out on the next service call.
What teach-back actually is
Teach-back is not quizzing the customer and it is not asking "does that make sense?" That question always gets a yes, because saying no feels like admitting you were not paying attention. Teach-back instead asks the customer to explain the instruction back to you, framed as checking your own explanation, not their intelligence.
The frame matters. Say:
- "I want to make sure I explained that clearly, can you walk me through what you'll do next month?"
- "Just so I know I covered it right, how would you describe this to your spouse?"
Never say "do you understand?" or "got it?" Both invite a reflexive yes with zero information content.
The three-step loop
- Explain the instruction in plain language, one idea at a time.
- Ask them to restate it using the neutral frame above.
- Correct and re-explain anything they got wrong, then ask them to restate again if the miss was significant.
This is a loop, not a single pass. If the restatement is off, the fix is never "well, just remember what I said." It is a different explanation, because the first one did not land. Repeating the same words louder or slower rarely helps; changing the analogy or the order usually does.
What a good restatement sounds like
A restatement that proves understanding is specific and sequenced, not a vague echo:
- Weak: "Yeah, change the thing sometimes."
- Strong: "Every three months, I pull the filter out here, hold it up to a light, and if I can't see light through it, I swap it."
If what comes back is vague, that is the signal to teach again, not to move on. The vague version is exactly what fails at week three.
Where to use it on a call
- Before you leave a job, on the one or two instructions that actually prevent a callback (a reset sequence, a warning sign to call about, a maintenance interval).
- After you flag a safety item, so the customer can repeat back what NOT to do until it is fixed, not just what you told them.
- When handing off a leave-behind sheet. The sheet is backup memory, not a substitute for confirming they heard the one thing that matters most today.
Do not teach-back everything you say. Pick the one or two instructions with the highest cost if forgotten, and confirm those. Teach-back on every sentence turns a helpful check into an interrogation.
Handling the customer who gets defensive
Some customers hear "explain it back to me" as being tested, especially if they are older or feel talked down to already. Soften it by explaining yourself first: "I've had customers tell me I go too fast, so I always double-check by having them repeat it back, it's on me, not you." That framing takes the pressure off them and puts the burden on your explanation, which is also more accurate: an unclear explanation is usually the actual cause of a missed instruction.
The documentation payoff
When a teach-back restatement is strong, note it. "Customer confirmed filter-check routine, restated correctly" in the job notes is a record that protects both of you if a preventable failure happens later. It shows you did not just talk at the customer, you confirmed they could act on it.
References
- Agency for Healthcare Research and Quality (AHRQ), teach-back method for health literacy (a widely adapted framework for confirming comprehension in a high-stakes, low-time interaction)
- See related: Explaining a Diagnosis So a Non-Technical Person Gets It, The Elderly Customer: Teaching Pace and Repetition