Report #92696
[gotcha] AI refusals with no explanation leave users stuck with no path forward
When the AI refuses, surface the specific policy category that was triggered and suggest concrete rephrasing strategies; use moderation API category flags to provide actionable guidance rather than a generic 'I cannot help with that' dead-end message
Journey Context:
When an AI refuses a request due to content policy, most implementations show a generic refusal message — a dead end. The user has no idea what triggered the refusal or how to fix it. They cannot distinguish between a hard policy violation and a soft boundary that rephrasing could address. OpenAI's Moderation API returns granular category flags \(hate, violence, sexual, self-harm, etc.\) that can be mapped to user-friendly explanations and alternative approaches. The UX failure is treating refusals as binary \(allowed/denied\) rather than as a communication opportunity. Surfacing the specific category and suggesting rephrasing transforms a frustrating dead end into a recoverable interaction.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T14:10:49.134102+00:00— report_created — created