NPS-Style Relationship Survey for Existing Products
A premium model-agnostic prompt for adding an NPS-style relationship survey that does not pretend to measure granular task usability.
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 an NPS-style relationship survey that does not pretend to measure granular task usability.
Full brief678 words of prompt-specific direction. This complete prompt comes with 209 other premium prompts.
Visual proofPrompt-specific result preview included
Success standardCreates an NPS-style relationship survey with timing, cooldowns, follow-up reasons, segmentation, and clear caveats about what the score can and cannot measure.
Verifying access
Prompt brief
- Target keyword
- NPS survey prompt
- Search intent
- Informational and implementation intent: the searcher wants to design an NPS-style flow with proper timing, follow-up, and interpretation.
- Audience
- Customer success, product operations, and research teams adding relationship feedback to an existing product
- Use case
- Add a relationship-level NPS-style survey after meaningful product exposure, with qualitative follow-up and cooldowns.
- Recommendation
- Pro - requires careful caveats, segmentation, and measurement discipline to avoid misusing NPS.
Expected result
- A relationship-level survey flow that captures likelihood-to-recommend and the reason behind the score while avoiding misuse as a task-level usability metric.
Implementation notes
- Capture score, segment, optional reason, account tenure, plan, role, recent milestone, channel, and cooldown status.
- Do not mix NPS data with task-level SEQ data in the UI; label dashboards and exports clearly.
- Use existing survey, modal, banner, or email components and brand voice.
- Define analytics events for shown, selected score, submitted, skipped, error, and follow-up consent.
Accessibility and responsive requirements
- The score scale must be operable by keyboard and announced as a grouped rating control with visible selected state.
- Labels must explain both scale endpoints; do not require color or position alone to infer meaning.
- Optional follow-up text areas need persistent labels, character limits, and text-based errors.
- Respect reduced motion and avoid celebratory animation that could imply the expected answer.
Quality checklist
- The prompt positions NPS as relationship feedback, not task-level usability measurement.
- Eligibility and cooldown rules prevent over-surveying.
- Follow-up questions vary by score band and remain optional.
- Analytics and exports preserve score context and channel.
- The design includes mobile scale behavior and accessible grouped controls.
Source-informed rationale
- NN/G NPS guidance says NPS is best for loyalty or brand perception, not granular UI satisfaction.
- NN/G survey design-cycle guidance places NPS in ongoing listening and warns it should not be the only usability metric.
- NN/G user-feedback guidance supports asking in the relevant channel without interrupting the user task.
Review notes
- Good pro prompt because it explicitly prevents a common NPS misuse; would benefit from future benchmark dashboard examples.
Share a result example
Paste a public image URL from a result this prompt helped create. Submissions stay private until reviewed.