Rewrite a generic chatbot fallback into a plain-language recovery response.
The current fallback says, "Sorry, I cannot process that request" when users ask to stop a physical card but keep wallet payments active. Plain-language recovery: name the boundary, offer supported alternatives, and route high-stakes exceptions. Generic apology copy sounds polite but leaves the user guessing which part failed and what to try next. Remove vague apology Change "Sorry, I cannot process that request" to "I cannot keep Apple Pay active while stopping the physical card." The revised line names the exact boundary. Users should not have to infer what the bot cannot do. Offer supported paths Add: "I can freeze…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in