Invisible to Visitors
The department is assigned behind the scenes. Visitors experience a seamless chat without being asked to navigate menus or make routing decisions.
Set Department Module
Automatic Chat Routing
Automatically assign a department to the conversation behind the scenes — without asking the visitor to choose. Based on the page URL, time of day, conditional logic, or any workflow variable, the Set Department module silently routes the chat to the right team before the visitor even knows it happened.
- No credit card
- 14-day free trial
- UK hosted
- Visual builder
What Is the Set Department Module?
The Set Department module assigns a department to the current conversation silently, behind the scenes. Unlike the Department Select module, which asks the visitor to choose, Set Department makes the decision automatically based on rules you configure in the workflow. The visitor never sees it happen — they simply experience a conversation that's already routed to the right team.
When the workflow reaches a Set Department node, it writes the specified department to the conversation's metadata. From that point forward, any Human Chat handoff in the workflow will route to an agent within that department. This happens in the background with zero delay — the visitor's experience is completely uninterrupted.
The module is particularly powerful when combined with other contextual nodes. Place it after a Page Match to route by URL, after a Time of Day check to route by schedule, or after a Conditional to route by any custom variable. You can even chain multiple Set Department nodes — the last one to execute wins, allowing you to build layered routing logic.
Zero Delay
Set Department executes instantly with no wait. The conversation continues to the next step without any pause or visible transition.
Rule-Based Routing
Combine with Page Match, Time of Day, Conditional, or any other module to assign departments based on URL, schedule, visitor data, or business logic.
Stackable Logic
Use multiple Set Department nodes in a single workflow. The last one to execute determines the final routing, enabling layered, context-aware decisions.
Why Use Automatic Department Routing?
Asking visitors to choose a department adds friction. Many visitors don't know which department can help them — is a refund handled by "Support" or "Billing"? By the time they guess wrong and get transferred, their patience is gone. Automatic routing eliminates this friction entirely by using contextual signals you already have — the page URL, the time of day, the visitor's account status — to make the routing decision for them.
Silent routing is also faster. The Set Department node executes in milliseconds, so the visitor moves from greeting to handoff without any intermediate steps. For high-volume websites where every second of friction increases bounce rates, this speed matters. Visitors on your pricing page are connected to sales. Visitors on your help centre are connected to support. Visitors browsing after hours are routed to the overnight team. It all happens automatically.
From an operations perspective, automatic routing reduces misrouted conversations. When visitors self-select, a meaningful percentage choose the wrong department, creating rework and transfer delays. When the system routes based on known context, accuracy is near-perfect — especially when you combine multiple signals (page URL + time of day + account tier) for precision routing.
When to Use Set Department
Use the Set Department module whenever you can infer the correct department from context rather than asking the visitor. Common scenarios include:
- URL-based routing: Visitors on
/pricinggo to Sales; visitors on/helpgo to Support; visitors on/billinggo to Accounts. - Time-based routing: During business hours, route to your primary team. After hours, route to the overnight or offshore team.
- Post-conditional routing: After a conditional check determines the visitor's intent (e.g., based on a previous button selection), silently assign the correct department.
- Webhook-informed routing: An API call identifies the visitor as a paying customer — automatically route to the Premium Support department.
- Default department fallback: Place a Set Department node early in the workflow to assign a default team. Override it later with a more specific assignment if conditional logic determines a better fit.
Example: URL-Based Sales Routing
A B2B software company uses Set Department to route pricing-page visitors directly to the sales team — no questions asked.
Pricing Page → Sales Team Routing
Visitors browsing pricing are automatically connected to a sales representative with full page context.
START
Human Chat
Sales team
Step-by-Step Breakdown
- Page Match: The workflow detects that the visitor is browsing a URL containing
/pricing. This triggers the sales-specific branch. - Set Department: The Set Department node silently assigns "Sales" to the conversation. The visitor sees nothing — the workflow continues seamlessly.
- Greeting: A targeted message acknowledges the visitor's interest in pricing, creating an immediate connection between their intent and the conversation.
- Human Chat: The conversation is routed to the Sales department queue. Because Set Department already assigned the department, the Human Chat node knows exactly where to send the visitor.
Best Practices & Tips
Get the most from the Set Department module with these proven routing strategies.
Set a Default Department Early
Place a Set Department node near the start of your workflow to ensure every conversation has a department, even if no conditional logic triggers. Override it with more specific assignments downstream.
Pair with Page Match
The most common pattern is Page Match → Set Department → Human Chat. Map your key website sections to departments: /pricing → Sales, /support → Support, /account → Billing.
Combine with Time of Day
Route to your primary team during business hours and to your overnight or offshore team after hours. Use the Time of Day module to branch, then Set Department on each path.
Layer Multiple Signals
Combine URL, time, and visitor data for precision routing. For example: pricing page + business hours = Sales; pricing page + after hours = AI Agent with Sales follow-up next morning.
Frequently Asked Questions
Does the visitor see anything when Set Department runs?
No. The Set Department module is completely invisible to the visitor. It executes instantly in the background and the workflow proceeds to the next node without any visible pause, message, or indication that routing happened.
Can I override the department later in the workflow?
Yes. If a second Set Department node executes later in the workflow, it overwrites the previous assignment. This is useful for layered logic — set a default department early, then override it with a more specific one if a conditional check identifies a better fit.
How is this different from Department Select?
The Department Select module asks the visitor to choose a department. Set Department assigns one automatically without visitor input. Use Department Select when the visitor's intent is ambiguous; use Set Department when you can determine the correct department from context (URL, time, conditional data).
What if the assigned department has no online agents?
The Set Department module only assigns the department — it doesn't check availability. Use a conditional node after the assignment (or before the Human Chat handoff) to check whether agents are online. If they're not, branch to an offline form, AI chat, or a different department as a fallback.
Related Modules
The Set Department module pairs with these modules for precise, context-aware chat routing.
Automate Your Department Routing
Route every conversation to the right team automatically — based on page, time, or custom logic. No code, no friction, no wrong departments.