Glossary

What is closing the loop?

Closing the loop means going back to the specific customer who gave you feedback and telling them what you did about it.

That means saying you shipped it, decided against it, or need more information.

It is the last step of a feedback program and the one most often skipped, because it requires knowing which named person said what, months after they said it. Programs that aggregate feedback into anonymous counts cannot close the loop. They no longer know who to go back to.

Why it matters

Closing the loop is the highest-return follow-up most companies have. It costs one email, it proves you were listening, it reliably produces a second round of more candid feedback, and "we built this because you asked" is the strongest expansion and referral message there is. Even a no closes well when you share the reasoning.

Example

Four customers asked for CSV export in Q1. Shipping it in Q2 and emailing those four specific people, quoting what each of them originally said, turns a feature release into four relationship moments. The same release announced only in a changelog produces none.

In UpSight

Every quote in UpSight is attached to the person who said it, and a theme's page lists the people behind it. When you ship the thing, open the theme. The list of who to tell is already there, and UpSight can draft the follow-up to that list of people.

Related terms

FAQ

Why do companies skip closing the loop?
Usually not by choice. Their tooling anonymized or aggregated the feedback, so they no longer know which individual to contact.
What if we decided not to build what they asked for?
Say so, with the reasoning. Customers respond well to a clear no and badly to silence.
How long after shipping should you close the loop?
Within days. The connection to what they asked for weakens quickly.