A password vault full of logins
One workspace per client means one login per client, and an offboarding checklist nobody enjoys.
Running support for clients is a volume business, and most chat tools are priced as though you were one company with one website. Every new client means another workspace, another licence and another password in the shared vault.
The agency version of the same four problems — and the reason "one workspace, many domains" is the first thing on this page.
One workspace per client means one login per client, and an offboarding checklist nobody enjoys.
Taking on a small client costs a full subscription, so the small ones stop being worth taking on.
And rightly so — the widget is on their site, in front of their customers, wearing your vendor’s default blue.
One queue, five clients, and an agent reading three messages in before they work out which brand they are answering as.
Every client domain lives in the same workspace, on the same snippet and the same token. Your team signs in once and sees all of it, filtered by domain. Taking on a small client stops being a procurement decision.
Set a sensible default for your agency, then override per domain only what needs to differ — colour, greeting, position, business hours, whether there is a pre-chat form. Everything you do not override keeps inheriting, so a change to your default reaches every client that has not opted out of it.
Group your people into departments and assign each client domain to the team that knows it. An agent opening a conversation knows which brand they are speaking as before they read the first message, and a new joiner inherits their team’s clients rather than being added to eleven of them by hand.
Three of the six feature pages, picked for this audience rather than listed alphabetically.
Connect a real IMAP/SMTP mailbox and answer email beside your chats. Gracee agents, same screen, no second tool to keep open.
Shared inboxDepartments, per-domain assignment and per-agent concurrency limits — so nobody is drowning while a colleague sits idle.
Routing & teamsColours, position, greetings, quick replies, business hours and a pre-chat form — all set in the dashboard, none of it a redeploy.
Widget & brandingNot today. Access is scoped by domain assignment within your workspace, which controls what your AGENTS see — it is not a client-facing login. If a client portal is what you need, tell us: we would rather hear it than guess.
Domains count against your plan’s limits. The tiers and their limits are published on the pricing page, and larger volumes are what the Enterprise conversation is for.
You can set colour, copy, position and behaviour per client domain, hide the “Powered by” line on paid plans, and add custom CSS.
Remove the domain from the workspace and the widget stops answering on it. There is no separate account to close or licence to cancel.
More of these on the general FAQ.
One line of code, no card to start. If it is not right for you, you will know within an afternoon — and we would rather hear why.
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.