How to Collect Customer Satisfaction Feedback on a Resolved Complaint

Resolving an Issue and Satisfying the Customer Are Not the Same Metric

A team can have a strong resolution rate and still be losing customers. The number only reflects what happened on the internal side - a status was changed, a reply was written, a ticket moved to the next column. None of that confirms the person who submitted the complaint agrees their problem is actually gone.

This gap is easy to miss because it's invisible from the inside. The team sees a clean, closed queue. The submitter, meanwhile, might have received a reply that didn't fully address what they reported, or a fix that solved part of the issue but not all of it. They rarely come back to argue the point - they just quietly stop reporting things, or take their business elsewhere. Resolution rate stays high. Trust erodes anyway.

The only reliable way to close that gap is to ask the submitter directly, at the moment their resolution is delivered, whether it actually worked. Not a quarterly NPS survey, not a generic 'how did we do' email - a single, specific question tied to the exact issue they reported.

Where to Ask: The Tracking Page Is the Right Moment, Not a Follow-Up Email

The submitter's tracking code already brings them back to one page to check on their complaint. That page is the natural place to ask the satisfaction question - not a separate email sent days later asking them to click through to a survey tool they've never seen before.

Timing matters as much as placement. The moment status changes to Resolved and the submitter checks their tracking code is the moment the resolution is freshest in their mind. Wait a week and send a generic satisfaction email instead, and most people either ignore it or can't recall the specifics of what was actually fixed well enough to answer honestly.

This also keeps the whole interaction inside one zero-friction flow. The submitter never created an account to report the issue in the first place - asking them to log into a separate feedback platform to confirm it was fixed breaks the same frictionless pattern that got them to submit the complaint at all.

What to Actually Ask (Keep It to One Question)

The question itself should mirror the complaint, not a generic customer experience survey. 'Did this resolve your issue?' with a Yes/No choice, or a lightweight 1-5 scale if more granularity is useful, is enough. Anything longer - multiple questions, open comment fields required before submitting, star ratings on five separate dimensions - drops response rates fast, because the submitter has already told you what was wrong once and doesn't want to repeat the exercise.

A 'No' answer is the most valuable data point in the whole system, so it needs a path forward, not a dead end. A single optional text box - 'what's still not right?' - captures enough to route the item back into the workflow without forcing the submitter to resubmit from scratch or track down the business through a different channel.

A 'Yes' answer is what should actually close the loop. As covered in the FeedSolve article on what to do after resolving a complaint, 'Resolved' is an internal status - it's the submitter's confirmation that turns it into a genuinely closed, trustworthy number.

Turning Individual Answers Into a Team-Level Satisfaction Number

Once the question is in place, the individual Yes/No answers add up to something more useful than any single response: a satisfaction confirmation rate sitting right next to the feedback resolution rate. Resolution rate answers 'how much did we close?' Satisfaction confirmation rate answers 'how much of that was actually a good close?' A team can be strong on the first number and weak on the second without ever noticing, because nothing in a standard Kanban workflow surfaces that gap on its own.

The combination is what makes the number actionable. A supplier feedback board with an 85% resolution rate but only 50% confirmed satisfaction points at a specific, fixable problem - the team is taking action, but the action often isn't landing. That's a very different conversation from a board where both numbers are low, which usually points to a capacity or process problem instead.

Breaking satisfaction down by board, category, or the team member who resolved the item turns a single blended percentage into something a manager can actually act on - whether that's a product category with a recurring root cause, or a reminder that resolution replies need to be more specific about what was actually done, as covered in the resolution workflow piece.

FAQs