A cafe near where I used to work had a comment card box by the till for about two years. Handwritten cards, a pen on a string, the whole thing. I filled one in once, mostly to be nice, and never heard anything about it again. Not a word about whether anyone read it. As far as I could tell the box was furniture.

They may well have been reading every card. They may have changed things because of them. I'd never have known, because the loop stopped at the box. Which means that from the outside their feedback process looked exactly identical to a business that had a box and ignored it.

That's the thing about acting on feedback silently. It's worth doing regardless, but it buys you almost nothing in credibility, and credibility is what determines whether anyone bothers next time. People are pretty rational about this. If you ask a customer for their time and nothing visible happens, they'll assume the next request is also for nothing. That assumption is where declining response rates come from, more than survey length or bad timing.

Saying it is nearly free

The reason this doesn't happen isn't cost. Telling people what changed takes a sentence. It's that nobody owns it, and it feels slightly awkward, because you're admitting that something wasn't right before.

The awkwardness is misplaced. Customers already know your business isn't perfect. They were the ones who told you. What they don't know is whether you're the kind of operation that does anything about it, and that's a genuinely useful thing for them to learn. A sign by the till reading "you told us the queue at lunch was slow, so there's a second till open from 12 til 2" does more for how people feel about the place than any amount of quiet competence. It also does more than a polished brand statement about how much you value your customers, because it contains a specific fact that can be checked.

Small and specific beats big and vague here. "We've listened to your feedback and are committed to improving your experience" is corporate throat clearing and everyone can smell it. "Three people said the tables by the window were freezing in February, so we've had the draught excluder replaced" is a real thing a real person did. The second one is also much easier to write, because you're just describing what happened.

Where to put it

There's no need for a newsletter or a campaign. The venues that work are the ones customers already look at.

In a physical business, a small sign or a chalkboard where people queue does the job. Salons and clinics can mention it at the desk when someone books again. A restaurant can put a line on the menu insert. In software, the changelog is the obvious place, though a changelog nobody reads is only slightly better than silence, so the more effective version is a direct reply to the person who asked. That's a two line email that says what they told you, what you did, and nothing else. No upsell attached to it. If you have a habit of replying to feature requests you've declined, the same courtesy applied to ones you've built lands even better, and what to do with feature requests you won't build covers the harder half of that conversation.

If you collect feedback with a form, the thank you screen is an underused slot. Most of them say "thanks for your feedback" and stop. A line saying what you changed last month gives the person who just filled it in evidence that the thing they did has a purpose. It costs you one edit and it's read by exactly the audience most likely to respond again.

The part that changes behaviour

The interesting effect isn't gratitude, it's the shift in what people tell you next time. A customer who has seen you act on something specific gives you noticeably better feedback. They stop writing "everything was lovely" and start writing the thing they'd actually like fixed, because they now believe the sentence has a destination. You're not asking them to fill in a form anymore, you're asking them to contribute to a process they've watched work.

The reverse is also true and much more common. Ask for years, change nothing visible, and you'll gradually be left with only the extremes: people delighted enough to gush and people annoyed enough to complain. The reasonable middle stops bothering, which is a shame, because that group is where the practical suggestions live. Low response rates are feedback too is the fuller version of what that decline is telling you.

There's a natural sequel to closing the loop. The moment right after someone sees you fixed their complaint is the moment they're most inclined to say something nice publicly. That's a fair time to ask, and much better than asking a stranger at random. How to ask for a review covers the timing of that properly.

Keeping track of what you actually changed

The practical obstacle to any of this is memory. Six weeks after you fix the draught you've forgotten which comment prompted it, and by the time you're writing a sign you can't remember whether it was two people or six who mentioned the cold. Then it becomes a job, and jobs get postponed.

Having your feedback in one place solves the boring half of that. Qria keeps the structured responses you collect and the public reviews you get on Google or Yelp in a single view, with the AI summarising what keeps coming up, so when you sit down to write the sign you can see how many people raised it and roughly when. It also means the thing you fixed and the thank you you get for fixing it end up next to each other, which is a more satisfying record than it sounds.

You don't need to report on everything. Most feedback won't produce a change, and announcing every minor tweak turns into noise. One thing a month, stated plainly where customers can see it, is enough to make the difference between a business that asks and a business that listens. The comment card box in that cafe eventually disappeared. I've no idea whether anyone noticed it was gone.