Closing the Loop with Customers

Definition

Collecting a customer's score is worthless unless someone acts on it — ideally by calling the specific customer who gave a low score, within roughly 24 hours, while the incident is still fresh for both customer and employee. "Closing the loop" means routing feedback to the person positioned to fix it (usually the same person, or their direct supervisor, who caused it), diagnosing the root cause, and fixing both the individual case and, where a pattern emerges, the underlying process.

In the Book

Chapter 8 opens with a paired contrast Fred experienced personally: a cable provider that collected his zero-rated feedback on a botched service call and never followed up in two years, versus Verizon Wireless, where a "how likely to recommend" text survey score of 3/10 produced a callback within days from the area store manager, who reviewed his actual billing history, apologized, and arranged a better-fitting plan. At Charles Schwab, branch manager Cheryl Pasquale starts her day reviewing the prior day's feedback report for her six financial consultants, spots a kiosk usability complaint to raise at the weekly team meeting, and gets an automatic "manager alert" flagging a client willing to discuss a transaction delay by phone — the same day. Apple forwards the customer's score and verbatim comments directly to the employee involved; Progressive Insurance's supervisors record actual detractor calls (with permission) and forward the audio so employees hear the customer's real tone, not a manager's paraphrase. Verizon's own manager told Fred the earlier satisfaction programs had failed for years because they were "add-ons, never a core part of the daily workflow" — the fix was hardwiring alerts into the computer screens managers already used every day.

Why It Matters

It is the mechanism that turns a measurement system into a management system: without closing the loop, a metric produces reports; with it, a metric produces behavior change at the point of contact. The pattern generalizes wherever feedback exists but routing and response latency are broken — a bug tracker nobody triages, an employee engagement survey with no follow-up meeting, a customer support ticket closed without confirming the fix worked. The lesson is that the loop's speed and specificity (the actual person, the actual voice, within a day) is what makes it change behavior — a quarterly aggregate report accomplishes almost none of what a same-week phone call does.