Report #102762
[gotcha] Refusals are communicated as blunt 'I can't do that' walls
Explain the boundary in one sentence, suggest a reframing or alternative that is in scope, keep the user in control, and coach toward successful requests rather than shutting down the conversation.
Journey Context:
Generic refusal copy protects the model but destroys trust: the user does not know if the request was misunderstood, unsafe, unsupported, or malformed. The better pattern is to treat a block as a teaching moment, mirroring how good customer service de-escalates. This is especially important in consumer products where refusals are the first place users hit the model's limits.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:25:25.719031+00:00— report_created — created