How to close the feedback loop with customers

Closing the feedback loop means telling the people who gave feedback what happened to it. It sounds like a courtesy. In practice, it’s what keeps feedback coming: customers who hear back keep telling you things, and customers who don’t eventually stop, often without saying why.

This guide covers the moments when a reply matters, what to say at each, and how to keep it manageable as feedback grows.

Why it matters

Think about it from the customer’s side. They took time to describe a problem. Weeks pass. Nothing. Maybe the feature ships, but they find out by accident, or not at all. The lesson they learn is that writing in doesn’t change anything.

When the loop is closed, the lesson is the opposite:

• Customers feel heard, even when the answer is “not now”.
• They give more, and better, feedback next time.
• They adopt what you ship, because they’re told it exists.
• Support gets fewer repeat questions, because customers already know the status.
• Accounts stay. “You asked, we built it” is one of the most persuasive messages in a renewal conversation.

The moments that need a reply

Not every change needs a message. These do.

1. When you receive it

A short acknowledgement: you got it, here’s where it lives, here’s how they’ll hear about it. If the feedback goes on a board, the customer can see it there, and that is the acknowledgement.

2. When you decide

When a request is planned, tell the people who asked. When you decide not to do it, tell them that too, with a reason. Decisions are the moment customers care about most, and the one teams most often skip.

3. When work starts

Optional, but valuable for big or long-awaited items. It shows the plan is real.

4. When it ships

The most important message. Tell the people who asked that it’s done, what it does, and how to use it. Ideally they get this before they’d find out any other way.

5. When it changes

If a planned item is delayed or dropped, say so. A short note beats silence every time.

What to say

Keep messages short, specific and in plain words.

• Name their request. “You asked for scheduled exports” lands better than “we shipped some improvements”.
• Say what happened. Planned, started, shipped, or not planned.
• Give one useful next step. A link to try it, to follow progress, or to add details.
• Be honest about “no”. “We’re not planning this because we’re focusing on X. We’ll keep your request open and look again if more customers need it.” Customers respect a clear no far more than a vague maybe.
• Thank them. Briefly. It costs nothing.

Make it scale

Replying to each customer by hand works for the first dozen requests. After that, you need the loop to close itself as part of normal work.

Keep who asked with each request

You can only notify the people who asked if you know who they are. Every request should keep its author, its voters and, ideally, the people who commented. When requests are merged, all of them carry over.

Tie messages to status changes

When a request moves from “Under review” to “Planned” to “Done”, the status change itself should trigger the update. Then nobody has to remember to send it.

Announce in one place, notify in another

A changelog or release notes page is the public record of what shipped. Personal notifications to the people who asked are what makes them notice. Do both: the changelog for everyone, a direct message for those who asked.

Write in the customer’s language

If your customers speak several languages, an update in their own language is far more likely to be read.

Examples you can adapt

• Planned: “Thanks again for suggesting scheduled reports. We’ve put it on our roadmap for the coming weeks; you can follow it here. We’ll let you know when it’s ready.”
• Not planned: “We’ve looked carefully at offline mode. It isn’t something we’ll build in the near future, because we’re focusing on reliability and integrations. We’ll keep your request open, and if more customers need it, we’ll revisit it.”
• Shipped: “You asked for scheduled reports, and they’re live. Open any report, choose Schedule, and pick who gets it. Thanks for asking; it helped us decide.”
• Delayed: “A quick update on single sign-on: it’s taking longer than planned because of a security review. It’s still in progress, and we’ll write again when it’s out.”

Each one names the request, says what happened, and gives one next step. None is longer than a few sentences.

Close the loop internally too

Customers aren’t the only ones waiting. Support agents who linked a ticket to a request, salespeople who promised a prospect “it’s on the roadmap”, account managers who raised it at a renewal: they all need to know when it moves. A shared board that they can follow, or a short internal note when big items ship, keeps them from finding out from the customer.

Measure whether it works

A few signals show the loop is closing:

• Fewer tickets asking about things that already shipped.
• More customers voting on existing requests instead of writing new tickets.
• Shipped features that the people who asked actually start using.

Common mistakes

• Announcing only to everyone. A general release note is easy to miss. The people who asked deserve a direct message.
• Skipping the “no”. Silence reads as “we ignored you”.
• Losing voters in merges. If duplicates are merged without moving the people behind them, those people never hear back.
• Promising updates you won’t send. If you say “we’ll let you know”, make sure something actually will.

How AntNexo helps

AntNexo keeps the author, voters and commenters with every post, and carries them over when duplicates are merged. When a post’s status changes, the customers who signed in and posted, voted or commented on it get an email in their language. When something ships, pick its initiatives and the AI drafts a changelog entry for you to review; once it’s published, the followers of the posts behind it are emailed that what they asked for is done.

See how the changelog works, how feature request management keeps everyone attached to their request, or what changes for customer success.