Intelligent Intake and Routing: Directing Users to the Right Agent at Scale
The Intelligent Intake and Routing pattern places a front-door agent between users and your fleet of specialist agents. It classifies intent and routes the request to the correct Genie, MCP Server, or workflow — without requiring users to know which agent handles what.
How It Works
A main Genie — or the Workato Slack Single App Experience — listens on the primary channel or messages tab. When a user sends a message, the front-door agent classifies the intent and routes the request to the appropriate specialist Genie. The specialist handles the request; the user experiences a seamless, single-entry-point interaction.
Slack Single App Experience
Workato's Slack Single App Experience extension (available via FDE Agentic Common Utilities) provides a unified Slack application that supports multi-Genie orchestration natively:
- Home page: Configurable home page for the main Genie, with the ability to add specialized home pages for domain Genies (e.g., HR Genie home page).
- Channel Genies: Add a specific Genie to a Slack channel to handle all messages, mentions, or intention-matched messages. Supports threaded replies.
- Agent Orchestration: The main Genie listens on the messages tab and hands off to the appropriate domain Genie based on user query classification.
Routing Quality Depends on Genie Descriptions
The most common failure mode: Mis-routing caused by vague or overlapping Genie descriptions. Write each Genie's description the way you'd write a tool description — specific about what it handles and, equally important, what it does not handle.
| Good Genie Description | Poor Genie Description |
|---|---|
| "IT Support Genie: handles hardware requests, software provisioning, VPN access, and password resets. Does not handle HR policy questions or finance approvals." | "IT Genie: helps with IT issues" |
| "HR Genie: handles PTO requests, benefits inquiries, and onboarding questions. Escalates performance issues to HR Business Partners." | "HR Genie: HR-related questions" |
Anti-Pattern: Over-Routing
Forcing every request through a front-door classification step adds latency and introduces a new failure point. Over-routing is the pattern of building a routing layer when direct access to specialist agents would serve users faster and with fewer errors. Before adding a routing layer, confirm that users genuinely can't be expected to navigate directly to the right agent.
Channel Configuration Options
| Mode | Behavior | Best For |
|---|---|---|
| All Messages | Genie responds to every message in the channel | Dedicated support channels with a single domain |
| Mentions Only | Genie responds when explicitly @-mentioned | General channels where the Genie is one of many resources |
| Intention-Based | Genie responds when the message matches a defined intent | Mixed-use channels where only specific request types go to the Genie |