The chat bubble is on your site, in front of your customers, so it should look like it belongs there. Every part of it is set in the dashboard — colour, copy, position, behaviour, what it asks for and when it is open — and none of it needs your developers twice.
Start from a preset or set primary, accent and surface colours yourself. Choose which corner it sits in, whether it opens on load, on click or after a teaser, and whether agent avatars show. On paid plans you can hide our branding entirely, or write your own CSS.
The header, the welcome message, the quick-reply chips a visitor can tap instead of typing, and what the widget says when nobody is on shift — all of it is your copy, not ours. You can write a different set for out-of-hours, because “we are closed” and “how can we help” are not the same conversation.
Collect a name, an email, a phone number or a subject before the conversation starts — and mark each one required or optional independently. Or let visitors skip the form entirely, because a form in front of a support question is how you lose the question.
Your docs site and your storefront do not have to share a greeting or a colour. Set the workspace default once, then override only what needs to differ on a particular domain — the rest keeps inheriting, so a brand tweak does not mean editing every site by hand.
Once. They paste one script tag. Everything after that — colour, copy, position, behaviour, hours, form fields — is dashboard settings, and no change requires a redeploy of your site.
On paid plans, yes. The “Powered by” line is a toggle in the widget settings.
Almost nothing until it is used. Before the first click there is no session, no heartbeat, no polling and no socket, and the widget registers no beforeunload handler — so your pages keep their back/forward cache and your Core Web Vitals stay yours.
Yes. Set a workspace default and override per domain only where it needs to differ. The snippet stays the same on every site.
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.