Closing the loop on feature requests: tell the people who asked
Every software company collects feature requests. They come in through support tickets, sales calls, QBRs, Slack channels shared with customers, a feedback board, and the notes a CSM types after a frustrating call. Product teams read them, weigh them and, over time, build a good share of them.
Then the feature ships, and the people who asked for it often never find out. Or they find out months later, by accident, from a release note they skimmed or a colleague who stumbled on the new button. The request was heard. The person who made it does not know that.
This post is about that last step: telling the people who asked. It is the cheapest part of the whole feature request process, and the one most teams skip.
Why requests get lost on the way back
The path in is wide. The path back out is narrow, and usually missing.
A request enters wherever the customer happens to be. A support agent tags a ticket. An account executive mentions it in a deal note. A CSM writes "they really want bulk export" in the CRM after a renewal call. A user upvotes an item on a public board. Each of these lands in a different system, owned by a different team, written in different words.
By the time the product team prioritizes, those inputs have been summarized into a theme or a roadmap item. That is the right way to plan. But the summary drops the names. When the feature ships months later, the engineers who built it know what they built, and the product manager knows why, but nobody holds a clean list of every account and person who asked, through which channel, in their own words.
So the announcement goes to everyone, in the same form, or to nobody in particular.
What the requester gets out of hearing back
A customer who asks for something is spending a little goodwill. They took time to explain a problem, sometimes more than once. When they hear back that it was built, three things happen.
- They feel heard. Their input changed the product, and they can see it did.
- They trust the next conversation more. If a CSM says "I've passed that on to product," that sentence carries weight once the customer has seen it lead somewhere before.
- They use the feature. The person who asked for a capability is the most likely person to adopt it, because they already have the problem it solves. If they never learn it exists, they keep their workaround.
The last point is the one revenue teams tend to underrate. A shipped feature that the requesting account never uses produces nothing for that account: no extra value, no expansion conversation, no renewal argument. The work was done and the payoff was left on the table.
Why a board notification is not enough
Most feedback tools can send an automatic notice when a request changes status: planned, in progress, shipped. That is better than silence, and it is worth having. But it covers only the people who used the board, and it reads like a system message, because it is one.
Compare two messages for the same release.
Status update: "Bulk export to CSV" has been marked as Shipped.
Hi Dana, you asked about exporting the full order history back in March when your finance team was pulling it by hand each month. That's live now: Reports, then Export, and you can pick the date range. Happy to walk Priya through it if that helps.
Both are accurate. Only the second one connects the change to the reason the customer asked, comes from someone they already work with, and names the colleague who will actually do the export. It also gives the CSM a natural reason to be in touch that is about the customer's problem, not about a renewal date.
The board notice also misses most of the people who asked. Requests made on calls, in tickets or in CSM notes never touched the board, so those requesters are never subscribed to anything.
A practical process
Closing the loop does not need a big program. It needs requests to be stored in a way that survives until the feature ships, and a habit of checking that store when something goes out.
Step 1: capture the request on the account
Wherever a request comes in, record it against the account and the person, not only against a theme. Keep the customer's own words and the problem behind the ask, not just the feature name. "Wants bulk export" is useful to product. "Finance pulls 12 months of orders by hand every month-end, takes half a day" is what makes the eventual message land.
This works best when the capture lives where the account team already looks, usually the CRM or the CS platform, with a link to the ticket or call it came from. Product can still roll requests up into themes, as long as each theme keeps a pointer back to the accounts and people underneath it.
Step 2: match what shipped to who asked
When a change goes out, ask one question: who asked for this, or has the problem this solves? Start with the explicit requests linked to the roadmap item. Then widen it a little. A fix to a sync bug matters to every account that filed a ticket about that sync, even if they described it differently. A new filter matters to the accounts whose users keep building the same workaround report.
Matching is the step teams skip, because it means reading across tickets, notes and deal records by hand. It is also where most of the value is, so it is worth making routine. A short checklist in the release process ("pull the linked requests, check tickets from the last two quarters for the same problem") is enough to start.
Step 3: tell the requester, from someone they know
The message should come from the rep or CSM who owns the relationship, not from a no-reply address. Keep it short. Say what they asked for, in their terms. Say what changed and where to find it. Offer help if it is useful. Do not turn it into a pitch.
Timing matters by type. A fix to a ticket the customer filed should go out as soon as it is live, because they are waiting on it. A larger feature can wait a day or two for the account owner to send a considered note.
Step 4: tell the people on their team who will use it
The person who asked is often not the person who will use the feature every day. A VP asks for a reporting change. An analyst on their team is the one who builds the report. Look at who in the account works in that part of the product and include them, or ask the requester to pass it on. One well-aimed message to the right two people does more than a newsletter to the whole account.
What to watch
You do not need a dashboard to know whether this is working. A few signals are enough: requesters replying to the notes, the requesting accounts actually using the shipped feature in the weeks after, and CSMs saying they had more to talk about in their next check-in. If the notes get no replies, look at whether they are too generic or coming from the wrong sender before you conclude nobody cares.
The hard part is not writing the message. It is keeping track of who asked for what across every channel, and noticing when the matching change ships.
Cheerblast does that matching and drafts the note for each account owner to review and send.