Automated Smartlook Checkout Error Handoff
Every morning, WebRun opens Smartlook, scans yesterday's session recordings for visitors who hit a checkout or payment error, saves the recording links and the error detail to a tracking sheet in Google Drive, and posts the list to Slack, so a developer can watch the exact failed checkout instead of trying to reproduce it blind.
How do I hand off checkout error recordings from Smartlook to a developer?
WebRun scans yesterday's Smartlook recordings every morning for visitors who hit a checkout or payment error, logs the session link and error detail to Google Drive, and posts the list to Slack. A developer can watch the exact failed checkout instead of trying to reproduce a vague bug report, so fixes happen faster.
- Developers get a linked recording of the exact failed checkout
- Checkout errors get surfaced the next morning instead of found by chance
- A running log in Drive shows how often checkout errors are happening
Built for E-commerce teams · Front end developers · Product teams · QA 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
app.smartlook.comin a real browser with your saved login - no setup, no API keys. -
1
Smartlook - find checkout error sessions
- Open Smartlook and scan yesterday's session recordings
- Find sessions where a visitor hit a checkout or payment error
- Capture the session link, the error, and the step it happened on
Done when Every checkout error session from yesterday has been captured.
-
2
Google Drive - log the recording references
drive.google.com
WebRun opens Google Drive to log the recording references. - Log each flagged session's link and error detail to the checkout issues tracker
- Note the date and the step in checkout it occurred
- Keep prior days' entries in place
Done when Today's checkout error sessions are logged in Drive.
-
3
Slack - post the handoff list
slack.com
WebRun opens Slack to post the handoff list. - Post the list of checkout error sessions to the engineering channel
- Include the session link and error for each
- Tag the channel so a developer can pick it up
Done when The engineering channel has today's checkout error handoff list.
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 WebRun fix the checkout error itself?
No. It only finds and hands off the session recordings. Diagnosing and fixing the checkout issue stays with your developer.
What counts as a checkout error worth flagging?
Any session where a visitor encountered a payment or checkout failure, based on the errors Smartlook already captures in the recording.
Does it record anything new or change our Smartlook tracking?
No. It only reads sessions Smartlook has already recorded. Recording settings and tracked pages are never changed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.