Automated Lookback Session Handoff Tracking
When a Lookback session recording finishes processing, WebRun posts a note to the research Slack channel naming the study and participant, and sends a Telegram handoff message with the recording link to the teammate assigned to review it, so completed usability sessions get watched and written up while the details are still fresh.
How do I make sure completed Lookback sessions get reviewed promptly?
WebRun watches Lookback for session recordings that finish processing, posts a note to the research Slack channel, and sends a Telegram handoff with the recording link to the assigned reviewer. Completed usability sessions get picked up the same day, while details are still fresh for whoever writes them up.
- Completed sessions get reviewed the same day, not weeks later
- The right teammate gets the recording link without asking around
- The research channel always shows what is newly ready to watch
Built for UX researchers · research ops teams · product teams · UX agencies
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
lookback.ioin a real browser with your saved login - no setup, no API keys. -
1
Lookback - find newly completed sessions
- Open Lookback and check for session recordings that finished processing
- Note the study name and participant for each
- Confirm the recording link is accessible
Done when Every newly completed session has been found.
-
2
Slack - post to the research channel
WebRun opens Slack to post to the research channel. - Post a note to the research Slack channel naming the study and participant
- Include the recording link
- Note how many sessions are now ready for review in that study
Done when A note is posted to the research Slack channel.
-
3
Telegram - hand off the recording link
WebRun opens Telegram to hand off the recording link. - Send a Telegram handoff message to the teammate assigned to review that study
- Include the recording link and participant name
- Keep the message internal to the research team
Done when The assigned reviewer has been sent the recording link on Telegram.
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 watch or summarize the session itself?
No. WebRun only notices that a recording finished processing and hands off the link. Watching and analyzing the session stays with your researcher.
How does it know who should review a session?
It uses whichever teammate is assigned to that study. If no one is assigned yet, it still posts to the Slack research channel so it is not missed.
Does it work for both live and recorded sessions?
It triggers once a session recording is available to watch, regardless of whether it started as a live or an unmoderated session.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.