Feedback workflows send each response where it belongs the moment it arrives: a bug to Jira, an at-risk customer to HubSpot, an urgent complaint to the Slack channel your team watches. Draw the flow once, test it on a real response and let it run.
Choose what starts the flow, add the steps and branches it needs, and set each step beside the canvas.
A workflow listens to one survey and starts at the moment you choose.
Starts the moment someone answers, before anything is read. The right start for logging every response.
Starts once AI has read the response, so conditions can use its type, theme, sentiment and urgency.
Starts once, when AI or a teammate marks a response as urgent.
Watches a score or a count over time, and starts when it falls below or rises above your line.
Conditions read the answers, the NPS group, who responded and what AI found: the type, theme, sentiment, urgency or customer risk. Match all of them or any one, and add an If / else step wherever the flow should split. A teammate’s correction always wins.
Each step lands as a real message, issue or row in a tool your team already uses.
Post each response to a channel, or one thread a day, with buttons that assign it, set its status or change its type without leaving Slack. Microsoft Teams works the same way.
Open a Jira or Linear issue with the answers, the files and a link back, set its priority from the AI urgency, or add each new response to the open issue for the same theme. Every plan.
Add a row for each response to Google Sheets, and keep the row up to date as its reading and status change.
Slack, Microsoft Teams, Google Sheets, webhooks, Zapier, Jira, Linear, HubSpot, Zendesk, Intercom, Mailchimp, Klaviyo, Segment and more come with every plan. Free runs 1 workflow per survey.
See all integrationsAlerts, tickets, customers and records, each ready to adjust: urgent responses to Slack, bugs to Jira, at-risk customers to HubSpot, every response to a sheet.
Say what should happen after a response. AI asks which survey and which tools, then draws the flow for you to review before anything is created. Every plan includes AI workflow drafts, 1 a month on Free.
Set a line for NPS, an average score, the share of detractors, the number of responses or the urgent ones. Usertick checks every hour, posts to Slack or Microsoft Teams or notifies teammates when the number crosses the line, and can tell you again when it is back.
Run the draft once on the survey’s latest response. Each tool gets a real message marked as a test, and a wait doesn’t hold the run.
See 30 days of runs and what each step sent and received. A failed step tries again on its own over the next hours, and Retry sends it again right away.
Posts each response to a Slack channel when it becomes urgent.
Posts an urgent response to Slack, waits two days, and posts again if the response is still open.
Creates a Jira issue for each bug and posts the bug to Slack when it is urgent.
Creates a HubSpot task and tells the team in Slack when a customer looks likely to leave.
Creates a Zendesk ticket for each response the AI reads as a complaint.
Adds a row to a spreadsheet for each response as it arrives.
Most flows act on what an answer says, so start them after the reading, when the type, theme and urgency are known.
Bugs go to the tracker, at-risk customers to the CRM and urgent complaints to the channel people watch. A channel that gets everything is read by no one.
Post now, wait two days, and post again only if the response is still open.
Run the draft on a real response and check what each tool received.
A red dot beside a workflow means a run failed. Open Activity, read the reason and retry it.
An alert on NPS or the share of detractors tells you about a slip within the hour, without anyone checking a dashboard.
A response being submitted, a response after AI analysis, a response becoming urgent, or a number such as NPS crossing a line you set.
Slack, Microsoft Teams, Google Sheets, webhooks, Zapier, Jira, Linear, HubSpot, Zendesk, Productboard, Mailchimp, Klaviyo, Intercom, Segment, Mixpanel, Amplitude, BigQuery and more, on every plan. Zapier reaches many other tools, such as Salesforce, Asana and Notion.
Workflows send responses to other tools and notify teammates. Owners and statuses are set in the inbox, and a Jira or Linear issue can move the response’s status as the issue moves.
Not directly. A workflow can send the response to your CRM, help desk or email tool, such as HubSpot, Zendesk or Klaviyo, and the follow-up goes out from there.
An alert watches NPS, an average score, the share of detractors, the number of responses or the urgent ones over the last hour, day, week or month. Usertick checks every hour, and a rate counts once its window has 30 responses.
The step tries again on its own over the next hours, and Activity shows the reason with a Retry button. After many failures in a row, the workflow pauses and holds new events until you turn it back on.
Yes, on every plan. Describe what should happen, answer a few questions about the survey and your tools, and review the flow before it is created.
Workflows, alerts and every tool come with every plan. Each survey can have 1 workflow on Free, 3 on Starter, 10 on Pro and 25 on Business, and a workflow on Free has 1 step that sends to a tool.
Start free, see what your customers mean, and get each answer to the person who can act on it.
