CSAT, CES, or NPS for support?

Use CSAT and effort together at the ticket level — satisfaction tells you how it felt, effort tells you how hard it was, and the two together explain most support churn. Save NPS for the relationship, not the ticket.

Won't tying responses to a ticket reduce honesty?

Keep it tied for routing and follow-up, but tell people the score won't affect their service. Honesty stays high when there's a clear, non-punitive reason you're asking.

Survey template

Support satisfaction (CSAT) survey

A generic 'rate our support' average tells you nothing you can act on. This template ties every question to the specific interaction the person just had — was it resolved, how hard was it, was the agent helpful — so a low score points at a real, fixable moment.

Best for: Support leads and CX teams closing the loop on individual tickets.

The questions

01How satisfied were you with how we handled this request?RatingThe core CSAT score, tied to this ticket — not your overall feelings about the company.
02Was your issue fully resolved?Single selectYes / Partly / No — resolution is the strongest driver of support satisfaction.
03How much effort did it take you to get this sorted?Opinion scaleThe Customer Effort Score read — low effort predicts loyalty better than delight does.
04How helpful was the person who assisted you?Rating
05What, if anything, made this harder than it needed to be?Long text
06Is there anything we could have done to resolve this faster?Long text

How to run it well

Fire it right after the ticket closes, while the interaction is fresh — a survey sent days later measures memory, not the experience.
Tie every response to the ticket ID and agent so a low score is traceable to a specific moment instead of an anonymous average.
Watch the effort question as closely as satisfaction; high effort quietly erodes loyalty even when the issue technically got resolved.
Set an alert on low scores and reply within a day — a fast follow-up on a bad ticket recovers more goodwill than the original fix.
Separate 'resolved' from 'satisfied'; a resolved-but-painful ticket and an unresolved-but-friendly one need different fixes.

Launch this in 60 seconds

Paste these into Enform — or just describe what you want to learn and it writes the questions, reads every response, and drafts the deck.

Use this template free

FAQ

CSAT, CES, or NPS for support?: Use CSAT and effort together at the ticket level — satisfaction tells you how it felt, effort tells you how hard it was, and the two together explain most support churn. Save NPS for the relationship, not the ticket.
Won't tying responses to a ticket reduce honesty?: Keep it tied for routing and follow-up, but tell people the score won't affect their service. Honesty stays high when there's a clear, non-punitive reason you're asking.

Related templates

Demographic surveyClean role, size, industry, and region questions — inclusive and optional by default.Post-purchase surveyCatch the buying trigger and the near-miss objection while it's still fresh.Product feedback surveyWhat they tried to do, what worked, and the one change they'd make.Usability test surveyPost-task success, stuck points, and a single-ease rating that scales.