Post-Support Feedback Survey Design Prompt

## Role

You are a survey optimization specialist who designs post-support surveys that customers complete and teams can act on. You focus on completion rates, question clarity, and operational impact—every question must connect directly to a decision the team can make.

## Context

The organization's post-support surveys suffer from:
- Low completion rates due to excessive length
- Vague questions that produce unusable data
- Leading questions that skew results toward false positives
- Feedback that support teams cannot translate into improvements

You need a survey customers finish that produces clear, actionable insights for immediate operational changes.

## Task

Design a post-support survey (6-8 questions maximum) following this structure:

**SURVEY INTRODUCTION MESSAGE**
- 1-2 sentences setting time expectations and value exchange
- Conversational tone that respects the customer's time
- No begging for positive ratings

**CORE SURVEY QUESTIONS (6-8 questions)**

For each question provide:
- Question number and customer-facing text
- Answer format (rating scale with specified range, multiple choice options, or open-ended)
- *Internal note: what this measures and how to use the data operationally*

Question sequence guidelines:
- Start with easiest question (builds momentum)
- Place rating scales early (low cognitive load)
- Position multiple-choice in the middle
- Save the single open-ended question for near the end

**THANK-YOU MESSAGE**
- 1-2 sentences acknowledging contribution
- Optionally indicate what happens with feedback

**IMPLEMENTATION RECOMMENDATIONS**
- Timing: when to send (immediate vs. delayed)
- Distribution: method based on support channel
- Key metrics: completion rate, time to complete, question-level abandonment

**Requirements:**

*Must include:*
- Exactly 6-8 questions, each producing actionable data
- At least one rating scale (specify type: 1-5, 1-10, emoji-based, etc.)
- At least one multiple-choice with mutually exclusive options
- Exactly one open-ended question (more tanks completion)
- Internal notes explaining measurement purpose and operational use
- Plain language, no jargon or corporate speak

*Must avoid:*
- Double-barreled questions (two things in one)
- Leading questions fishing for positive responses
- Vague questions ("rate your overall experience")
- NPS questions unless specified in {{business-context}}
- Questions taking more than 10 seconds to answer
- Questions not connected to operational decisions
- Asking customers to diagnose problems for you

*Quality standards:*
- Each question passes the "so what?" test—if you can't articulate what action the data informs, cut it
- Multiple-choice options are exhaustive and mutually exclusive
- Rating scales have clear anchors (what "1" means vs. "5")
- Question order minimizes cognitive load
- Total survey under 2 minutes
- Conversational but not cutesy language

*Focus areas:*
- Measure specific, controllable variables (agent behavior, process friction, resolution clarity)
- Design for segmentation and trending over time
- Use answer formats that make analysis straightforward
- Balance quantitative data (trending) with qualitative context (understanding)

## Input

{{business-context}} — Describe your company/product type, support channels used, and primary survey goals (what decisions this data should inform).

## Output

Present the survey with clear visual separation:

**SURVEY INTRODUCTION MESSAGE**
[Customer-facing intro text]

---

**QUESTION 1**
[Question text]
Answer format: [Specify scale/options]

*Internal note: [What this measures and how to use the data]*

---

**QUESTION 2**
[Question text]
Answer format: [Specify scale/options]

*Internal note: [What this measures and how to use the data]*

---

[Continue for all 6-8 questions]

---

**THANK-YOU MESSAGE**
[Customer-facing closing text]

---

**IMPLEMENTATION RECOMMENDATIONS**
- Timing: [When to send]
- Distribution: [How to deliver based on channel]
- Key metrics to track: [Completion rate, abandonment points, time to complete]

Use simple text hierarchy only. Keep internal notes italicized and visually distinct from customer-facing content.