Session Recording Tools
What an AI can do with your session recordings from Yaplet or a connected AI app: find recorded website visits, read what a visitor did step by step, and sum up many visits to see where people get stuck. It only reads, and it reads text, not video.
Overview
From Yaplet, the assistant inside your dashboard, or a connected AI app, an AI can work with your session replays: find recorded visits, read what one visitor did step by step, and sum up hundreds of visits to see where people get stuck. It looks the actions up with find_actions and runs them with run_read_action — see MCP Server.
The AI reads text, not video. Every recorded visit is also kept as a short text timeline: the pages opened, what was clicked, which fields were filled in and which boxes ticked, how far down the page the visitor scrolled, idle stretches, switching to another tab, rage clicks (three or more fast clicks on one thing; four on plain text or a picture, since three clicks there just select a paragraph), clicks after which nothing on the page changed — often a broken button — and clicks the page answered only after a few seconds. A button with no text is named by its icon when it has one. A field is named by its label; what a visitor typed is never in the timeline, and text your website hides from recording stays hidden.
All three actions only read, so they work at every access level, including Read only, and Yaplet runs them without a Confirm card.
Actions
| Action | Level | What it does |
|---|---|---|
replays.list_recordings | Read | Finds recorded visits, newest first: when, how long and how much of it was active, phone or computer, the website, the visitor (name, email and country when known), the first and last page, clicks, rage clicks, clicks that changed nothing, and errors the page reported. It can narrow them down by dates (the last 30 days unless told otherwise), website, a page address such as /checkout, phone or computer, one visitor, a minimum active time, or only visits with problems, and sort them by newest, most problems or longest. 20 visits per answer, up to 50. |
replays.read_timeline | Read | What happened in up to 5 visits, each as numbered lines with the time from the start of the visit, under a short header with the visit's totals and a link to watch the recording in the dashboard while it still exists. |
replays.summarize_recordings | Read | Sums up to 300 visits in one answer: median and average active time, the share on phones, how many had problems, the pages people arrived on and left from, the buttons and links with the most rage clicks and with the most clicks that changed nothing, the most clicked ones, and the fields filled in on the most visits. |
For a question like "where do people get stuck?" the AI starts with the summary, then reads a few example visits. That is far quicker than reading visits one by one.
What to Know
- Only visits recorded since these tools arrived (November 2026) have a timeline. Timelines are written as recordings come in, so older recordings can only be watched in the dashboard.
- A timeline outlives its recording. When your recording slots are full and an old recording is deleted to make room, its timeline stays, and the AI says the recording itself is gone. A timeline is deleted together with its visitor, its website or your workspace, and each website keeps at most its newest 2,000 timelines.
- Big periods are narrowed for you. A list or a summary looks at the newest 500 matching visits, and a summary reads the newest 300 of them. The answer says so when more matched; ask for a shorter period or one page to go further.
- Gaps are explained. Where nothing was recorded for a while, the timeline says whether the visitor was idle, away from the website or on pages that are not recorded — or whether part of the visit is missing, so what happened then is unknown.
- Some moments have no exact time. On websites that change pages without reloading, a page change is shown at the page-title change that goes with it; when no title changed, it is listed at the end of that stretch, without a time. Errors the page reported are counted for the visit, without a time.
- Website text is information, not instructions. Button and page texts come from your website as the visitor saw it, so an AI reads them as information only.
What Uses Credits
Nothing here. The actions read stored text and call no AI, so they use no credits; a connected app does the thinking itself.
What an AI Cannot Do Here
- Switch recording on or off. A person does that on the chat widget's Install tab, under SDK Features, together with the recording rules.
- Watch a recording. The AI reads the timeline; a person watches the recording on the Session Replays screen, and the timeline's link opens it there.
- See what a visitor typed. Only which field was filled in, by its label.
- Pin or delete a recording. That stays in the dashboard.
Example Prompts
- "Where do people get stuck on our checkout page this month?" (uses
replays.summarize_recordings, thenreplays.list_recordingssorted by problems andreplays.read_timelinefor a few visits) - "Show me last week's visits on phones that had rage clicks."
- "Which buttons on our website don't respond when people click them?"
- "From which page do most visitors leave?"
- "What did this visitor do before they opened the chat?"