How to make sure every user who gives feedback hears back, from the first acknowledgment to the fix, without writing every reply by hand.
Closing the feedback loop means every person who gives feedback learns what happened to it. You don't need to reply to every submission personally. You need a system that acknowledges feedback, keeps the conversation going, and tells people when something changes. Users who hear back are more likely to give feedback again, and to give more detail when they do.
Know who needs a reply first
Some feedback is a passing comment. Some comes from a user who is clearly waiting for an answer, or frustrated. Start with those.
AI Assist flags feedback where the user appears to expect a reply, based on the tone and language of their message. It also detects sentiment, so negative feedback surfaces early instead of sitting in the queue. See AI Features in Userback.
Confirm receipt automatically
The gap between submitting feedback and hearing anything back is where users lose trust. Send an acknowledgment the moment feedback arrives.
Go to Feedback > Settings > Automation.
Under Reporter automations, turn on Email reporters to confirm their new feedback has been received.
Click Edit Email to write the message.
Use the message to set expectations, for example how your team reviews feedback and when the user might hear more. A confirmation that promises a reply within a day only helps if your team can keep that promise.
See Configure Your Feedback Settings for step-by-step instructions on the confirmation email, including how to edit its subject and message.
Reply at scale with templates
Reply templates let you send a considered, on-brand reply in seconds. Build templates for your most common situations, such as "We're looking into this", "This is a known issue", or "Thanks for the idea".
Personalize before you send. Every template can be edited. Add the user's details or refer to the exact issue they raised.
Use merge fields. Fields like
%%reporter_name%%and%%feedback_link%%fill in automatically.
Share one library. Templates are shared across your account, so everyone replies in the same voice.
In the comment box, click the Attach template icon to pick one. See Reply Templates.
Tell users when it's fixed
This is the step most teams skip, and the one users notice most.
Under Reporter automations, turn on Enable a "Resolve & Auto-reply" option when marking feedback as resolved.
Click Edit Email to write the message.
When you resolve feedback the reporter should hear about, choose the Resolve & Auto-reply option instead of a plain resolve.
Say what changed, thank the user for reporting it, and point them to where they can see the fix.
See Configure Your Feedback Settings for step-by-step instructions on the Resolve & Auto-reply option, including how to edit the reply email.
Check the fix worked
A fix that looks finished in your backlog isn't always one that solved the user's problem. The reporter satisfaction survey asks them.
Under Reporter satisfaction survey, turn on When feedback is resolved, email the reporter with a satisfaction survey. It's off by default.
In Survey, choose the CSAT survey to send.
In Send it, choose how long after resolving to send it, for example 1 hour.
In Trigger, choose Ask me each time to decide per item, or Always send to send it every time.
With Ask me each time, a "Feedback resolved" dialog appears when you resolve an item, with Send survey and Don't send buttons. Follow up personally on low scores. See Configure Your Feedback Settings.
Catch replies after you resolve
When a user replies to resolved feedback, that reply needs to reach your team, not sit under a closed status.
Under Reporter automations, turn on Automatically re-open feedback when reporter responds. Resolved feedback goes back into your queue as soon as the reporter replies. Replies to Userback notification emails are added to the feedback thread, so the whole conversation stays in one place.
See Configure Your Feedback Settings for step-by-step instructions on reopening feedback automatically.
Close the loop with everyone at once
Individual replies matter. The bigger signal is changing the product and showing users you did.
Find the patterns. Reports and AI Themes show which issues come up again and again, so you fix what affects the most users. See Best Practices for Making Better Product Decisions with Reports.
Show progress publicly. On your Public Roadmap, users can watch ideas move from open to in progress to shipped, without anyone contacting them.
Notify voters when an idea ships. When you resolve an idea in your Ideas Portal, Userback prompts you to email everyone who voted for it. See Best Practices for a Successful Ideas Portal.
Announce releases. Post an Announcement for each meaningful release so users see what's new.
What's next