Automated UsabilityHub Results Handoff
When a UsabilityHub test finishes collecting responses, WebRun checks Google Calendar for the related project deadline, and posts a Microsoft Teams note handing the results off to the researcher who needs to analyze them, naming the test type and how many responses came in, so finished tests move to analysis the same day instead of sitting in the results tab.
How do I make sure completed UsabilityHub tests get analyzed promptly?
WebRun watches UsabilityHub for tests that finish collecting responses, checks the related project deadline on Google Calendar, and posts a Microsoft Teams note handing the results to the assigned researcher. Finished tests move into analysis the same day, instead of sitting unnoticed in the results tab.
- Completed tests move to analysis the same day, not weeks later
- The right researcher gets notified without checking the tool themselves
- Deadlines stay visible right alongside the handoff
Built for UX researchers · product teams · UX agencies · research ops teams
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
usabilityhub.comin a real browser with your saved login - no setup, no API keys. -
1
UsabilityHub - check tests that finished collecting responses
- Open UsabilityHub and check for tests that finished collecting responses
- Note the test type and number of responses collected
- Confirm the test has not already been handed off
Done when Every newly completed test has been found.
-
2
Google Calendar - match each to its project deadline
WebRun opens Google Calendar to match each to its project deadline. - Check Google Calendar for the related project deadline
- Note how many days remain before analysis is needed
- Flag if the deadline is close
Done when Each is checked against its project deadline.
-
3
Microsoft Teams - hand off the results
WebRun opens Microsoft Teams to hand off the results. - Post a Microsoft Teams note handing the results to the assigned researcher
- Name the test type and response count
- Note the project deadline so urgency is clear
Done when The researcher has been handed the results in Microsoft Teams.
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
Does it analyze the test results itself?
No. WebRun only notices a test finished collecting responses and hands it off. Analyzing and interpreting the results stays with the researcher.
How does it know who should get the results?
It uses whichever researcher is assigned to that project. If nobody is assigned, the note still posts so the team notices it is ready.
What if the project deadline has already passed?
The handoff note still goes out and flags the deadline as passed, so the researcher knows to prioritize it.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.