Comments & sharing

Say what you saw at the second you saw it

A replay is most useful when it reaches the person who can fix what it shows. Comments pin a note to a moment; a share link sends exactly one resource to someone without an account, for as long as you choose.

AI insights & Ask Agents Journeys Heatmaps & zones Forms Replay Segments Reports MCP Mobile Experiments Surveys Comments & sharing AI agent analytics Data platform

Comments

Threads on the replay, marked on the progress bar

Anyone signed in to the organisation can comment, viewers included: watching replays and saying what they saw is their job. A comment on a session is stamped with the playhead; its chip (“0:16”) seeks the player, and a violet dot marks it on the progress bar beside the error and rage marks. Threads have one level of replies, markdown, @mentions of people in the organisation, resolve and reopen.

The same panel sits on reports, dashboards and investigations, so the discussion stays with the evidence instead of in a chat thread that links to it.

A Northwind session replay paused at 0:17 on the cart page with the Apply coupon button under the cursor; violet comment dots and orange and red error and rage marks on the progress bar; the timeline highlights ‘Dead click on Apply coupon’; below, a Comments panel with 3 threads at 0:10, 0:16 (with a reply) and 0:37, each stamped with its moment. — Comments are pinned to a moment: the violet dots on the progress bar are the three threads, and a ‘0:16’ chip seeks the player to the dead coupon click. The reply under it closes the loop (‘the click handler was dropped in the v2.4 cart refactor’). New comments are stamped with the playhead (‘at 0:17’).

Share links

One resource, the parts you choose, until a date you choose

The Share button on a replay, report, dashboard or investigation creates a public link. You pick its scope (the replay, the comments, the AI summary) and an expiry of 1, 7, 14, 30 or 90 days. The link is shown once; only its hash is stored. The resource’s links are listed with their views and last view, and any can be revoked.

The page opens without a sign-in and says who shared it and when it expires
A shared session shows the cached AI summary; a public read never calls the model
No person record is included with a shared session
Revoked and expired links answer with a plain page (410), and every read is rate-limited

The public shared replay page, opened without signing in: ‘Read-only · Shared by Demo user on Oct 26, 2026 · expires Nov 9, 2026’, the replay player at 0:17 on the cart, the timeline, the AI summary with seven timestamped highlights, and the three comment threads read-only. — What a colleague without an account sees: the replay, the timeline, the AI summary and the comments, read-only, with who shared it and when the link expires (14 days here). The link was created with the replay, comments and AI scopes on; each can be left off, and the link can be revoked.

How it works

A shared replay: from a comment at 0:16 to a read-only page for someone outside

Each public read runs on a database session pinned to the link’s organisation, so even a forged link row cannot reach another tenant’s data.

What you can ask

Questions this answers

Type them into Ask, give them to an agent as a goal, or send them through MCP from your own assistant.

Comment on this momentA thread stamped with the playhead

Share this replay with the vendor for a weekA 7-day link with the replay scope only

Who has opened the link I sent?Views and last view per link

Revoke every link to this dashboardEach link marked revoked; the page answers 410

Send the board report to the CFOA report link with the last render, or email it as a PDF

What did the team say about this session?The threads, oldest first, with replies

Outcomes

What teams do with it

Bugs with evidence

The ticket links to a replay with a note at the exact second.

Outside help without accounts

An agency or vendor sees one replay for as long as you allow.

Reviews in context

Report and dashboard comments stay with the numbers they are about.

Where it stops. Mentions are recorded on the comment and, where the platform’s notification table is present, notify the person; there is no separate in-app inbox in InsightClickIQ yet. A shared investigation shows its findings and the sessions it watched, not their replays.