Features
What it does, and what that gets you.
Everything on this page works today, on every account, with nothing to buy. Anything we have not built is said plainly in the docs rather than written here in the present tense.
The agent's side
One queue, however many websites you run.
Filters that narrow rather than widen, search that reaches message bodies, and notes that are a different kind of message rather than a flag on an ordinary one.
My order says delivered but nothing arrived
Sorry about that. Do you have the order number?
#48120
Found it — it went to the depot. I've booked redelivery for Thursday.
Internal note · not sent to the visitor
Depot confirmed. Refunding the delivery fee too.
The inbox
One queue, however many websites you run.
The place your team lives. Built for somebody handling six conversations at once, not for a demo.
Live, both directions
Messages travel over a socket and are acknowledged only once they are committed, so "sent" means durable rather than "it left the browser". A reconnecting visitor is replayed exactly what they missed.
Assignment and transfer
Take a conversation, hand it to a colleague, or route it to a department. Filters for what is yours, what is unassigned, and what nobody has answered.
Private notes
Notes are stored as a different kind of message and are never sent to the visitor — not filtered out on the way, simply never in the stream they receive.
Search that reaches the words
Search message bodies, not just subjects, with a trigram index behind it. Tags, priority and status narrow rather than widen.
Automation
Start the conversation before somebody has to.
Rules that fire on what a visitor actually did, evaluated on your server rather than in their browser.
Triggers
Greet somebody who has been on a page for a minute, or who arrived from a campaign. Add a tag, set a priority, send a message. Once per visit, or every time.
Pre-chat and offline forms
Ask for what you need before the chat starts, and take a message when nobody is online. Answers appear beside the conversation, not buried in it.
Saved replies
Type a short key and get the paragraph you write forty times a week. Shared across the team.
Help centre and tickets
Answer it once, then let people find it.
The two halves of support that are not live chat, and that most chat tools leave you to buy separately.
Public help centre
Categories and articles, published on your own domain, searchable. Drafts stay invisible to strangers — by index and by direct link.
Tickets with real numbers
Numbered per account and gapless, so "ticket 412" means exactly one thing. Public replies go to the requester by email; internal ones never leave.
Email that arrives
Every notification is recorded as a delivery with an outcome, so "did they get it?" is a question with an answer rather than a shrug.
Team and access
The right people, on the right websites.
Permissions are data, checked on the server, on every request.
Roles you can shape
Owner, admin, manager and agent out of the box, plus custom roles you define yourself. Nobody can grant a permission they do not hold themselves.
Scoped to a website
Restrict a member to the sites they look after. They see those in the list, by direct link, in search and in replies — and the others answer as though they do not exist.
Departments and availability
Group your team, route to a group, and let agents set whether they are taking chats right now.
Numbers and integrations
Check the work, then connect it to everything else.
Reporting from your own rows, and the two integration surfaces a real deployment needs.
Reports you can trust
Volume, first response, resolution, per agent and per website — bucketed in your account’s own timezone, from sums and counts rather than stored averages.
Signed webhooks
HMAC-signed with the timestamp in the signature, retried with backoff, and every attempt visible in a delivery log. The queue is the database, so a Redis restart cannot lose one.
Scoped API keys
The same routes the dashboard uses, reached with fewer permissions. Shown once, stored hashed, revocable — and the revoked key is kept, because "which key was that" is an incident question.
See it on your own website.
Create an account, paste one script tag, and watch a conversation arrive in your inbox.