Post-ticket satisfaction survey questions with timing rules
Designs the short survey sent after a support ticket closes, with one main score question, a reason question and an effort question, plus when to send it, who to skip and how to read the answers. Use it when a support team sends long surveys nobody answers, or gets scores it cannot act on.
The output this prompt produced, unedited.
The prompt
Constraints first
No more than three questions; the first can be answered in one tap.
Ask about the support experience, not the product, unless a separate question says so.
Never survey a customer whose ticket was closed without a fix, until it is fixed.
No incentives that could push scores up.
Inputs
Business and support channels: [e.g. a broadband provider; phone, WhatsApp and email]
Ticket volume a week and current response rate: [e.g. 2,400 tickets, 6% response]
What the team wants to learn: [e.g. which issue types leave people unhappy]
Languages customers use: [e.g. English and Hindi]
Where answers are stored: [e.g. the helpdesk, a sheet]
Output format
Question 1: a satisfaction scale with exact labels for each point.
Question 2: an effort question, "How easy was it to get this sorted?", with its scale.
Question 3: one optional open question, worded for the low and high score paths.
Send rules by channel: when to send after closing, and one reminder at most.
Skip rules: duplicates, spam, abusive tickets, closed without a fix, surveyed in the last 30 days.
Eight reason tags for sorting open answers.
How to read results: the minimum responses before trusting a weekly score, and what to look at first.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.