Your visitor types. Your agent sees it as they type. That round trip is the whole product, and everything else here exists to keep it fast and to keep your agents from repeating themselves.
Before a visitor touches the launcher there is no session row, no heartbeat, no polling and no WebSocket — just a bubble painted from config that arrived inlined with your snippet. The socket opens on the first click and carries everything after that: messages, typing, presence, delivery and read state.
Canned responses live in a shared library your admins curate, and agents insert them mid-sentence. Internal notes stay on the ticket and never reach the visitor. Tags make a month of conversations searchable rather than merely archived.
When a second agent opens a conversation someone else is already answering, both of them are told. A manager can join a live chat to help without taking it over, and a transfer hands the whole history across rather than starting the visitor again from scratch.
Visitors can rate the chat and email themselves the transcript. Every email address that asks to stop hearing from you lands on a suppression list your agents cannot override, and converted leads are collected in one screen your sales team can export.
No. A visitor who opens the widget is queued for a human. The automation we ship — canned responses, routing, quick replies — makes your agents faster; it does not stand in for them.
The widget falls back to a polling loop so the conversation still works on networks that block sockets. The fallback engages only when it is needed, so the common path never pays for it.
It depends on your plan — the free tier keeps three days, paid plans keep it indefinitely. The exact cap for your workspace is shown on your billing page.
They can, and they are warned when it happens. Opening a conversation a colleague is already replying to shows you their presence on the ticket before you start typing.
One line of code, no card to start. If it is not right for you, you will know within an afternoon — and so will we.
Pick the categories you're comfortable with. Essential is always on — everything else is yours to decide. See our cookie policy.
Session, security and CSRF cookies. Needed to keep you signed in and the site secure — there's no version of the site that works without them.
Remembers small things — billing cycle preference, last viewed plan. Disabling makes the site slightly less smart, never broken.
Anonymous, aggregated visit data — which pages get read, which features get clicked. We use this only to decide what to build next.
Attribution for ad campaigns and remarketing pixels. Off by default — enable only if you don't mind retargeting.