Customer Satisfaction Survey Template
Ask a customer about last Tuesday’s support call and you’ll get a shrug. Ask them forty seconds after the call ends and you’ll get the truth, with specifics. Memory of interactions decays in days, but most satisfaction programs ask questions weeks later and wonder why the answers have gone soft. This template is built for the other approach: a short pulse, triggered by the interaction itself, rated while the experience is still vivid enough to describe.
The Pulse, Not the Questionnaire
Transactional satisfaction lives and dies on brevity:
- One rating as the spine — how satisfied were you with this [purchase / delivery / support call]? on a clean opinion scale
- One context question — which touchpoint is being rated, so the response attaches to the right moment. Support calls and delivery experiences score differently, and conflating them produces averages that describe nothing
- One effort or success check — a quick yes/no on whether they got what they came for. A satisfied customer who didn’t accomplish their goal is a paradox worth catching
- One optional comment — for the interactions that need explaining
Four questions, under a minute, done on a phone before the kettle boils. That’s the whole instrument.
Timing Is the Design
The trigger matters more than the questions:
- Minutes after, not days — embed the link in the order confirmation, the ticket-close email, the delivery notification. The moment the interaction ends is when the rating is most accurate and the customer most willing
- Every interaction, or a sample? — high-frequency touchpoints (every order, every ticket) can pulse a sample; rare, high-stakes ones (onboarding, major purchases) pulse everyone
- The response-rate math — post-interaction placement routinely earns strong completion rates precisely because the ask arrives when the experience is fresh and relevant
What Transactional Data Sees That Surveys Can’t
Because every response attaches to a specific moment, the data does things relationship surveys can’t:
- Touchpoint league tables — which of your interactions consistently scores lowest? The weakest step in the journey names itself within a few weeks of collection
- Before-and-after reads — change the delivery process, and the next month’s delivery scores register the effect. Transactional data is how you verify improvements rather than assume them
- Recovery triggers — a low score minutes after an interaction is a rescue opportunity; an alert to the right person turns a bad Tuesday call into a saved relationship
One Caution About Averages
Resist publishing one blended satisfaction number across all touchpoints. The value of transactional measurement is resolution — knowing the checkout delights while the returns process frustrates — and averaging the two destroys precisely that. Report by touchpoint, trend each line separately, and let the weak steps volunteer themselves.
Frequently Asked Questions
When exactly should the pulse be sent?
At the interaction’s natural end: ticket-closed email, order-delivered notification, call-wrap confirmation. The closer to the moment, the higher the completion rate and the sharper the specifics. A pulse sent a week later is measuring memory, not experience.
Will customers mind being asked after every single interaction?
They mind being asked at length repeatedly. A one-screen, thirty-second pulse tied to a real event reads as attentive rather than nagging — but for high-frequency touchpoints, sampling a portion of interactions keeps the welcome mat out. Frequency fatigue comes from volume plus length; this design removes the length.
Should the pulse mention that it's about the specific interaction?
Yes — name it in the first line: how was your delivery yesterday? Specificity lifts response rates and anchors the rating to the right moment. Generic how are we doing? framing after a transaction produces mushy, memory-based answers.
What do we do with a stream of low scores on one touchpoint?
Treat it as a work order. The touchpoint tag localizes the problem; the comments describe it; a month of focused fixing shows up in the next month’s scores. This loop — measure, fix, verify — is the entire reason transactional measurement exists, and it’s the part organizations skip at their peril.
Can this pulse replace our periodic relationship survey?
No — they measure different things and belong together. The pulse audits individual moments; the relationship survey tracks how the customer feels about you overall, which is more than the sum of touchpoints. Run the pulse for operations and the periodic survey for strategy, and never ask one to impersonate the other.