A user says something is broken, you have no idea what they did
Without session data, support is a guessing game. With it, you watch what happened, understand the context, and reply with confidence.
Support queue · Linked to session data
T-4812 sarah.m@"Export button does nothing on my page"
/dashboard/exports
Export CSV
ERROR
400 Bad Request on POST /api/exports 0:42RAGE 4 rage clicks on "Export" button 0:58
CONTEXT Chrome 131 · macOS · 14,820 rows in view -
Pull the session, watch it, resolve it
Filter sessions by user ID, error type, or page. Find the one you need in seconds. Watch what the user did, see where the error fired, and know exactly what to fix.
Find a session
User ID or email
[email protected] 1 match
Error type
4xx errors Rage clicks JS exceptions
Page contains
/dashboard/exports Found 1 session · 2m 08s · 2 errors · 4 rage clicks Open →
Some users go quiet before they cancel
Usage drop-off shows up in session data before it shows up in your churn numbers. Funnel data shows you where users stopped progressing. Fix the friction before they leave.
At-risk users · 6 week trend 4 quieting down
The tools that power this
Three features that turn support into signal.
Know what happened,
every time
Sessions are available in real time, the moment they happen.
Resolve tickets from sessions Week of Mar 15
Tickets resolved 84 ↑ 22% vs last wk
Avg time to resolve 12m ↓ 38% vs last wk
Tickets with replay 92% ↑ 14pp
Saves before churn 9 ↑ 3 MRR saved
"Closed a ticket in 4 minutes because I could just watch exactly what happened. The replay had the exact 400 error and the request payload."