HEARD—Hear, Empathize, Acknowledge, Resolve, and Diagnose—creates a confident rhythm when emotions run high. One retail agent, Lila, used HEARD during a billing dispute: she mirrored the concern, apologized for the inconvenience, solved the immediate issue, and scheduled a follow‑up check. The customer changed tone within minutes, later praising her clarity and care. Use a short HEARD checklist to avoid skipping the crucial acknowledgment that customers crave most.
LAST—Listen, Apologize, Solve, Thank—reminds us that respect does not require agreement. A travel support team adopted it to manage rebooking frustrations. They listed concerns without interrupting, offered a sincere apology for the disruption, proposed two solution paths, and thanked the traveler for patience during policy constraints. The result was lower escalation rates and renewed goodwill. Include a standard wrap‑up sentence that confirms action and invites quick feedback to close the loop.
LEARN—Listen, Empathize, Apologize, Resolve, Next steps—keeps recovery efforts honest and forward‑looking. A SaaS agent used LEARN after a misapplied feature flag caused downtime. She acknowledged impact, offered a targeted apology, deployed a short‑term fix, and shared a preventive change request ID. The client appreciated the transparency more than perfection. Template your LEARN handoff with timestamps, owners, and review dates, so progress and accountability are never ambiguous.

DESC—Describe, Express, Specify, Confirm—and SBI—Situation, Behavior, Impact—help you name the issue without blame. Example: “When multiple accounts were opened this week (situation), we had a Terms conflict (behavior), which risks suspensions (impact). I’d like to explore consolidating access (specify) and confirm a path forward (confirm).” This format reduces defensiveness and clarifies boundaries. Pair it with a reference link to policy pages so customers see rules as shared guardrails, not arbitrary obstacles.

Feel–Felt–Found must be sincere to work. Try: “I understand why a surprise fee would feel disappointing. Other customers felt similarly before we walked through how the discount schedule works. They found that aligning billing cycles removed the confusion and saved money.” Avoid robotic phrasing by adding a specific next step and personal detail. A brief, relevant anecdote signals you are not copy‑pasting but genuinely connecting experience to the current situation.

Boundaries are kinder when alternatives are ready. Borrow from BATNA thinking by preparing acceptable options before difficult calls. Example: “While I can’t extend the expired promotion, I can offer a prorated upgrade or a training session that achieves the same goal.” Naming the constraint plainly, then proposing credible choices, preserves fairness and momentum. Finish with a preference question to honor autonomy: “Which path feels most helpful given your timeline and priorities right now?”
SPIN—Situation, Problem, Implication, Need‑payoff—organizes thoughtful questions that respectfully guide customers from current state to desired value. An agent might ask: “What changed in your workflow?” then “What breaks now?” and “What happens if this persists?” before “If solved, what becomes possible?” This ladder reduces guesswork and increases relevance. Document one concise insight per step, so the resulting solution statement reads like a collaborative plan instead of a technical monologue.
SPIN—Situation, Problem, Implication, Need‑payoff—organizes thoughtful questions that respectfully guide customers from current state to desired value. An agent might ask: “What changed in your workflow?” then “What breaks now?” and “What happens if this persists?” before “If solved, what becomes possible?” This ladder reduces guesswork and increases relevance. Document one concise insight per step, so the resulting solution statement reads like a collaborative plan instead of a technical monologue.
SPIN—Situation, Problem, Implication, Need‑payoff—organizes thoughtful questions that respectfully guide customers from current state to desired value. An agent might ask: “What changed in your workflow?” then “What breaks now?” and “What happens if this persists?” before “If solved, what becomes possible?” This ladder reduces guesswork and increases relevance. Document one concise insight per step, so the resulting solution statement reads like a collaborative plan instead of a technical monologue.
All Rights Reserved.