Routing & teams

Nobody drowning, nobody idle.

Routing is not a nice-to-have once you pass three agents; it is the difference between a team and a scramble. Assign agents to domains, group them into departments, and cap how many chats any one person can hold at once.

Multi-domain

One workspace. Every site you run.

Your business probably has a marketing site, a docs site and an app. Most tools want a separate workspace — and a separate invoice — for each. Here they are all domains under one roof, sharing one snippet, one team and one bill, with conversations landing in the inbox of the agent who owns that domain.

  • Whitelist every domain and subdomain you run
  • The same snippet and the same token on all of them
  • Assign agents per domain, not per workspace
  • Filter every inbox and report by domain
Departments

Assign a team, not eleven people.

Group agents into departments — Billing, Onboarding, Tier 2 — and assign the department to a domain in one action. Adding a new hire to the team gives them everything the team can see, without eleven separate clicks and one you forgot.

  • Departments as first-class groups
  • Bulk-assign a whole department to a domain
  • New joiners inherit their department’s access
  • Transfers can target a department, not a person
Load

A cap on how many chats one person holds.

An agent juggling nine conversations is doing nine of them badly. Set a concurrent-chat limit per agent and the queue respects it. When everyone is at capacity the waiting queue is visible to your admins, who can hand a chat to whoever has room.

  • Per-agent concurrent-chat limits
  • A visible waiting queue for admins
  • Manually assign a waiting chat to a specific agent
  • Response-time performance reporting, exportable

Questions people actually ask.

Do I pay per domain?

No. Domains are part of your plan’s limits, not a separate line item, and the same widget token serves all of them. That is the single most common reason teams move to us from a per-brand-workspace tool.

What happens when every agent is at their limit?

The conversation waits in a queue your admins can see, and they can hand it to whoever has capacity. Nothing is silently dropped.

Can a chat move between departments mid-conversation?

Yes. A transfer carries the full history, so the receiving agent reads what happened rather than asking the visitor to start again.

Do I have to add a domain before the widget works on it?

Yes — domains are whitelisted and reviewed. That is what stops someone pasting your snippet onto a site you have never heard of.

Try it on your own site. Today.

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.