Five modules that were never separate products.
Everything writes to the same visitor record. That is why the replay is already attached when the message arrives, and why nothing here needs an integration page.
Live chat
Every site you run pours into a single stream. Filter by site instead of walking through eight separate consoles.
- Merged cross-site inbox
- Two-way translation
- Visitor panel with city, ISP and device
AI agent
Write it a handbook, hand it read-only keys, and read what it drafts. Turn on automatic handling and it answers by itself — never with an action you have not allowed.
- Drafts you approve, or automatic handling
- Handbook separate from facts
- Read-only business functions
Session replay
Every conversation carries the recording of what the visitor just did. Same visitor id, same row, no guessing from timestamps.
- rrweb capture, kilobytes per session
- Inputs masked before upload
- Attached to the conversation automatically
Analytics
Pageviews, sources and funnels joined to conversations, because they were never separate data to begin with.
- Sources, pages and funnels
- Joined to conversations by visitor id
- No second tracking script
Email channel
Connect the support address you already publish. Mail lands in the same inbox, keeps its thread, gets the same translation.
- IMAP in, SMTP out, your domain
- Threads kept intact
- Same translation and same agent
The join key is the product
Two vendors cannot produce this no matter how good the integration is, because their ids were never meant to line up.
Chat
visitor_id 8c1f04ae
Recording
visitor_id 8c1f04ae
Analytics
visitor_id 8c1f04ae
Bolt a recorder onto a chat tool and you get two id systems with nothing to join on. The best anyone can do after that is guess from timestamps and IP addresses.
Put it on one site tonight.
One script tag, no card, unlimited seats. If it does not earn its place by the weekend, delete the line.
Free plan stays free. The AI is the only thing that ever costs you anything.