Automated Hotjar Feedback Routing
Every morning, WebRun opens Hotjar, reads yesterday's survey and feedback responses, groups them by the page they came from and the sentiment rating left, posts each group to the Microsoft Teams channel that owns those pages, and texts the experience lead the strongly negative ones.
How do I route visitor feedback to the right team automatically?
WebRun routes your Hotjar feedback every morning. It reads yesterday's survey and feedback responses, groups them by page and sentiment rating, posts each group to the Microsoft Teams channel that owns those pages, and texts the experience lead the strongly negative ones, so real comments get answered rather than filed.
- Each team sees only the comments about their own pages
- Strongly negative feedback reaches the lead the next morning
- Unmatched responses are flagged for routing instead of dropped
Built for product managers · UX researchers · support leads · growth marketers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
insights.hotjar.comin a real browser with your saved login - no setup, no API keys. -
1
Hotjar - sort yesterday's responses
WebRun opens Hotjar to sort yesterday's responses. - Open Hotjar and read the survey and feedback responses left yesterday
- Capture the comment, the page it came from and the sentiment rating
- Note whether a session recording is attached to the response
- Group the responses by page and match each page to its owning team
- Set aside anything with no page match for a human to route
Done when Every response from yesterday is grouped by page with an owning team.
-
2
Microsoft Teams - route to the owning team
WebRun opens Microsoft Teams to route to the owning team. - Post each group to the channel that owns those pages: product, support or marketing
- Quote the comment, name the page and show the sentiment rating
- Link the session recording where one exists
- Post the unrouted responses to a shared channel so someone assigns them
Done when Every team has only the comments about their own pages.
-
3
Twilio - text the lead the worst
WebRun opens Twilio to text the lead the worst. - Text the experience lead the strongly negative responses and the pages they came from
- Keep it short: the count, the worst two comments and their pages
- Send only to your own team numbers. WebRun never replies to a visitor or contacts a respondent
Done when The lead has seen yesterday's worst feedback.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it reply to the visitor who left feedback?
No. WebRun only routes the comment internally to your Teams channels. Replying to a respondent stays with your support or product team.
How does it decide which team gets a response?
By the page the feedback came from, matched against the page ownership map you give it, so checkout comments reach the team that owns checkout.
What happens to feedback that matches no page owner?
It goes to a shared channel flagged as unrouted rather than being dropped, so a person assigns it and the ownership map gets better over time.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.