Cancellation Feedback Flow Without Dark Patterns
A premium model-agnostic prompt for adding cancellation feedback after cancel intent while preserving a clear cancellation path.
Premium prompt
What the full prompt specifies
Verifying your account access. Premium prompt content will load automatically if this account has access.
Design jobA premium model-agnostic prompt for adding cancellation feedback after cancel intent while preserving a clear cancellation path.
Full brief692 words of prompt-specific direction. This complete prompt comes with 209 other premium prompts.
Preview statusNo reviewed output is available for this prompt yet.
Success standardCreates a respectful cancellation feedback flow with reason capture, optional follow-up, clear completion path, and churn-analysis metadata.
Verifying access
Prompt brief
- Audience
- SaaS founders, retention teams, customer success teams, and product designers improving existing subscription cancellation flows
- Use case
- Add a cancellation reason survey and optional recovery path after the user has clearly chosen to cancel.
Expected result
- A respectful cancellation feedback flow that captures churn reasons, supports optional recovery, and keeps cancellation completion obvious and accessible.
Implementation notes
- Reuse existing billing, destructive-action, confirmation, and alert components so the flow feels trustworthy and consistent.
- Store reason, optional comment, selected offer, skipped feedback, cancellation status, plan, tenure, and account segment for churn analysis.
- Do not block cancellation because analytics, feedback submission, or offer loading fails.
- Route urgent technical or support reasons to existing support workflows after cancellation is completed or explicitly paused by the user.
Accessibility and responsive requirements
- Use clear headings that distinguish feedback from final cancellation confirmation.
- Reason options must be keyboard and screen-reader friendly, with selected state conveyed beyond color.
- If a destructive confirmation is required, describe consequences in text and keep focus order predictable.
- Errors must not trap the user; provide a path to complete cancellation even if feedback submission fails.
Quality checklist
- The flow asks for feedback after cancel intent, not before.
- Cancellation remains clear, available, and not visually demoted behind retention options.
- Only one optional follow-up appears from the selected reason.
- The final confirmation explains billing, access, data, and reactivation details.
- The design avoids shame copy, confusing buttons, or forced support contact.
Share a result example
Paste a public image URL from a result this prompt helped create. Submissions stay private until reviewed.