Most teams don't lack feedback. They lack a reliable way to read it and act on it. Work through this checklist after the Quickstart Guide. Each item links to the article that covers it in full.
Who to involve
Userback works best when the right people are in it from day one. You don't need everyone set up before launch, but decide who owns what.
Product manager or head of product: owns the feedback workflow, reviews incoming feedback, and connects it to the roadmap.
Developer: installs Userback and sets up user identification. The sooner this is done properly, the more useful every submission becomes.
Designer: uses annotated screenshots and session replays to spot visual and UX problems.
Support or customer success: often hears about issues first, and can log and escalate them with full context.
Launch checklist
Invite your team. See Inviting and Managing Your Team Members.
Identify your users. Pass each logged-in user's ID, name, email, and any attributes you care about, such as plan or company. For example:
Userback.identify('USR123', { name: 'Jane Doe', email: 'jane@yourapp.com', plan: 'Pro', account_id: 456785 });See How to Identify Users.
Set up categories and statuses that match how your team talks about the product. See Configure Your Feedback Settings.
Turn on AI Assist so incoming feedback is classified, titled, and checked for sentiment automatically. See AI Features in Userback.
Turn on Session Replay so bug reports arrive with a recording of what happened. See Session Replay vs. Full Session Replay.
Create automations for default assignees and due dates, so bugs go to your dev lead and ideas go to your PM. See Automate Your Feedback Management.
Connect your tools, such as Slack, Jira, Linear, or ClickUp. See Integrations.
First 30 days
Review new feedback daily and act on anything urgent. Set the triage owner's Inbox to Focus mode so they see their own work without every new unassigned item. See Manage My Notification Settings.
Invite your support and customer success team if they aren't in yet.
Use Reports to spot early patterns before sprint planning.
Turn on reporter confirmation and resolved emails so users know they've been heard.
When you're ready to go further
Email Forwarding: Forward feedback from your support inbox straight into Userback. See Email Forwarding.
Browser Extension: Let developers, designers, and QA capture feedback on any page during sprint reviews and pre-launch testing.
Surveys: Run targeted NPS, CSAT, or feature-specific surveys for chosen user segments.
Ideas Portal: Give users a public place to submit and vote on feature requests and follow your roadmap. It needs regular moderation, so it suits products with an engaged user base. See Getting Started with Your Ideas Portal.
AI Themes: Once feedback has built up, group your recent feedback into themes with a sentiment breakdown for each. Run it before sprint planning. See Understand AI Themes.
Agree on a workflow before you go live
The biggest predictor of whether Userback delivers value is whether your team knows what happens when feedback arrives. Answer these four questions together:
Who reviews incoming feedback? One person owns triage and checks new submissions as they come in.
How does feedback get prioritized? Bugs and ideas are categorized automatically, urgent items are flagged, and due dates keep things moving.
How does feedback reach the roadmap? High-signal feedback is tagged and brought into sprint planning, and integrations push confirmed issues to your dev tools.
How do users know they were heard? Status changes are visible to reporters, and reply templates cover common responses.