Use battlecard responses to defend better conversational repair patterns.
Generic fallback Fallbacks are edge cases, so a generic apology is fine. Use when fallback volume is material. Your line Let's treat the top fallback clusters as product surfaces. If thousands of users hit them, specific repair is cheaper than repeated failure. Arguing from craft quality alone; use volume and recovery cost. It connects repair quality to operational cost and user completion. Complexity Specific fallbacks will make the flow too complex. Use when the team fears branching. We only need specific repair for common or high-risk clusters. Everything else can stay simple. Promising bespoke repair for every possible utterance. It…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in