Departments in Website Chat: Routing Sales, Support and Billing Without Transfers
A department selector avoids "let me transfer you". How to set up teams, automatic distribution (round robin, least load) and AI as the receptionist.
In this article
"Let me transfer you to the right team" is the sentence that turns a good website chat into a phone-menu experience. The visitor explains their invoice problem to a salesperson, gets moved, explains it again to support, and finally reaches billing after two waits. Departments in website chat exist to skip all of that: the visitor picks Sales, Support or Billing before typing, or the system works it out from the page they are on, and the first person who answers is the right one.
This is about routing, not the pre-chat form: who gets the conversation, how it is shared inside a team, what happens when the team is offline, and how an AI agent can act as the receptionist so most visitors never see a menu at all.
The department selector: required, optional or invisible
In Omnifox each website chat channel can show a department selector before the conversation begins. Each department (team) has a name, a color and an icon, and you decide whether choosing one is required or optional.
Three sensible configurations, in order of how much you ask of the visitor:
- Invisible. No selector; every chat lands in one team and the AI agent or triggers do the sorting. Right for teams of two to five people who all answer everything.
- Optional. The selector appears, with a "not sure" path to a general queue. Right for most small and mid-sized businesses.
- Required. The visitor must pick. Right when the teams are genuinely separate, such as a US HVAC company with sales, service dispatch and accounts, or a UK university with admissions, student support and fees.
Write the options in the visitor's words, not your org chart's; nobody outside your company knows what "Customer Success" means.
How can we help today? Buying or upgrading – pricing, demos, quotes Something isn't working – setup, errors, how-to Invoices and payments – billing, refunds, account changes Not sure – we'll point you to the right person
One behavior to know before launch: a visitor who already chose a department does not see the selector again while that conversation is still open. That is by design; it stops the "which department?" question reappearing every time they return to the tab. A visitor who chose wrong is reassigned by the agent inside the inbox, not by being asked again.
Distribution inside the team
Picking a department gets the conversation to a team; the team's distribution strategy decides which person gets it. Omnifox offers three:
| Strategy | How it works | Use it when | Watch out for |
|---|---|---|---|
| Round robin | Each new chat goes to the next agent in turn | Sales teams where fair lead distribution matters and everyone has similar capacity | An agent on a long call still gets their turn; pair with status discipline |
| Least load | The chat goes to whoever has the fewest open conversations | Support teams with uneven chat lengths | A fast agent who closes quickly ends up doing more; monitor over weeks, not days |
| First available | The chat goes to the first agent who accepts it | Small teams, peak hours, or when speed to first reply is the metric | Quiet chats can sit if nobody claims them; set a fallback |
For sales, round robin is usually the honest choice: every rep sees the same number of new leads and the CRM pipeline reflects it. For support, least load keeps the queue balanced when one ticket takes forty minutes and the next takes two. First available suits a team watching the shared inbox together, such as a three-person front desk at a dental group in Phoenix during the morning rush. Strategies are set per department, so Sales on round robin and Support on least load is a common combination.
Routing by page: the visitor on /help does not need a menu
The selector is one way to route; triggers are the other, and they ask nothing of the visitor. A trigger with a URL condition can assign the conversation directly to a team, agent or AI agent, or show the selector only on pages where it makes sense. Rules that work for most sites:
- URL contains
/helpor/docs→ assign to Support, skip the selector. The visitor is already reading documentation; asking "sales or support?" is redundant. - URL contains
/pricingor/demo→ assign to Sales. Optionally let the AI agent send the first message with the goal of qualifying and booking a demo. - URL contains
/accountor/billing→ assign to Billing; if you identify logged-in users through the widget, the agent sees who they are before replying. - Everything else → show the selector (optional), or route to a general queue with the AI agent answering first.
Conditions combine with AND/OR, so you can add time on page or device: a visitor on the pricing page for more than 90 seconds is a stronger sales signal than one who bounced in from a blog post. Every conversation also keeps its landing page, referrer and UTM on the contact record in the CRM, so the rep who receives a round-robin lead sees which page and campaign produced it before saying hello.
The AI agent as receptionist
The most effective way to avoid transfers is to let an AI agent take the first message and classify the request. Set its response strategy to "only the first message," instruct it to identify the intent and hand off to the right team, and most visitors get a useful first reply in seconds while routing happens behind the scenes. The handoff message is where this succeeds or fails; a vague "transferring you now" recreates the phone-menu feeling. A specific one does not:
Thanks, that's a question about a duplicate charge on your March invoice, so I've passed it to the billing team with the details you just gave me. Sam or Priya will pick it up here in this chat; you won't need to repeat anything. If you'd rather get the answer by email or text, leave your address or number and we'll follow up there.
Three details do the work: it names what was understood, it promises the visitor will not repeat themselves, and it offers a second channel in case they leave the tab. The agent's tools tag the contact and assign the team directly, so routing is done by the time the human opens the conversation. Where the AI answers from a knowledge base it may resolve the request outright; the knowledge-base setup for website chat covers how to feed it your documents and FAQ.
After hours, per team
Departments rarely share a schedule: sales might answer until 8 p.m. Eastern while billing stops at 5. Business hours are set per day with a timezone; outside them the widget shows a configurable message and, if enabled, a name-and-email form that creates the conversation so the lead is not lost. The AI agent can keep answering out of hours if active. Say the hours honestly: "Billing replies Monday to Friday, 9 to 5 UK time; leave your email and we'll answer first thing" beats a spinner that never resolves.
Frequently asked questions
What is a department selector in website chat?
It is a menu the visitor sees before the chat starts, listing your teams with a name, color and icon, so the conversation reaches the right team without a transfer. It can be required, optional or hidden.
Which distribution strategy should a sales team use?
Round robin, in most cases: each rep receives new chats in turn, which keeps lead distribution fair and easy to audit. Support teams usually do better with least load.
Can website chat route by page instead of asking the visitor?
Yes. A trigger with a URL condition can assign the conversation to a team, an agent or an AI agent automatically, for example sending everyone on /help to Support without showing the selector.
Why doesn't the department selector show again for a returning visitor?
Because their conversation is still open. By design, a visitor who already chose keeps the same team until the conversation closes; an agent can reassign it from the inbox.
Route once, answer once
Departments, distribution strategies, URL triggers and an AI receptionist are four layers of one idea: the visitor explains their problem once, to the person who can solve it. Start with an optional selector and a strategy per team, add URL routing for the obvious pages, and let the AI handle the first message where it can.
All of it is configured on the website chat, included in every plan; set up your departments during a 7-day free trial and watch the transfers disappear.
Ready to try it in your business?
Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.
7 days free. No credit card required.
Read more
-

Automatic Welcome and Away Messages: Templates and Best Practices
-

What Is RCS and Why It's Replacing SMS
-
Combining Phone Calls and Messaging in One Customer Workflow
-

How to Connect Shopify With Your Customer Service Platform
-
After-Hours Coverage Across Canadian Time Zones
-

IVR vs Contact Center: When to Use Each
-
TikTok Ads vs Facebook Ads: which delivers better returns
-

What Is a Prompt and How to Write a Good One (Step by Step)
Comments (0)
No comments yet. Be the first to share your thoughts.
Leave a comment
Your email is never published. Comments are moderated before appearing.