EnforcedFlow
EnforcedFlow routes work across teams with configurable advanced round-robin groups, agent criteria, availability, and email assignments.
Verdict
Common use cases
- Assign next available support agent to incoming ticket
- Route qualified leads to sales reps in rotation
- Check which agents are active before escalating
- Update agent metadata when skills or availability change
- Audit routing-field requirements across multiple groups
Integration
- Vendor
- EnforcedFlow
- Category
- crm
- Auth
- API_KEY
- Tools
- 5
- Composio slug
enforcedflow
Tools
- Get Group Routing Fields
Get detailed routing-field configuration and metadata field names for one round-robin group.
- List Group Agents
List agents in a round-robin group, optionally filtering by active status, with metadata and configured field values.
- List Round Robin Groups
List round-robin groups accessible to the connected account, including group IDs and summary routing-field requirements.
- Select Next Agent
Select the next available agent for a round-robin group using optional configured criteria. This advances the group's round-robin routing state and may consume one routing request from the account's monthly quota; it is not a read-only prev
- Upsert Group Agent
Update the first agent matching a filter, or create an agent when the filter matches none. A missing or empty filter always creates an agent. Use a precise, stable filter because any filter miss takes the create path and can produce duplica
Setup
Setup guide
- 11. In Switchy, open Settings and navigate to Integrations. 2. Search for EnforcedFlow and click Connect. 3. You'll be prompted to paste an API key — generate one from your EnforcedFlow dashboard under Account > API Keys. 4. Copy the key and paste it into Switchy, then click Authorize. 5. Switchy confirms the connection and shows which round-robin groups the key can access. 6. Open any Project and type '@EnforcedFlow list round robin groups' to verify the integration works. 7. If the response lists your groups with IDs and routing-field summaries, you're ready to invoke selection and upsert tools in live workflows.
What teammates see: by default, memories from EnforcedFlow are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Assign Next Agent
@EnforcedFlow select the next agent for group ID 'support-tier-1' with criteria skill:billing and status:active
List Active Agents
@EnforcedFlow list agents in group 'sales-outbound' filtering by active status true
Check Routing Rules
@EnforcedFlow get routing fields for group 'escalations' and show me the metadata field names
Update Agent Profile
@EnforcedFlow upsert agent in group 'support-tier-2' matching email 'jane@example.com' and set skill tags to refunds,cancellations
Audit All Groups
@EnforcedFlow list all round robin groups and include group IDs plus routing-field requirements
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@EnforcedFlow list all round-robin groups and show me which ones have active agents available right now
Found 3 round-robin groups in your account: 'Sales - West Coast' (ID: rrg_8x2k) has 4 active agents with routing fields configured for territory and product line; 'Support - Enterprise' (ID: rrg_9m1p) has 7 active agents requiring language and tier fields; 'Onboarding Specialists' (ID: rrg_3n7q) has 2 active agents with no routing-field requirements. All groups are currently operational and ready to route.
This example shows the MCP's read-only discovery workflow — useful when you need to audit which groups exist before routing a lead. Requires API key with read access to round-robin groups. No side effects; this query does not advance routing state or consume routing requests from your account quota.
@EnforcedFlow select the next agent from the Sales - West Coast group for a lead with territory=CA and product_line=enterprise
Selected agent Sarah Chen (agent ID: agt_4k8m) from 'Sales - West Coast' group. Sarah's configured fields match your criteria: territory=CA, product_line=enterprise, active=true. This selection advanced the group's round-robin state and consumed 1 routing request from your account. Sarah is now assigned to handle this lead; her contact details are available in your EnforcedFlow dashboard.
This example demonstrates the core routing action — it permanently advances the round-robin queue and consumes one request from your monthly quota. The MCP will fail if no agents match the criteria or if your account has exhausted routing requests. Always verify group configuration with Get Group Routing Fields before calling this tool to avoid wasted quota.
@EnforcedFlow review the last 10 routing decisions in our Support - Enterprise group and tell me if we're distributing load evenly across agents
The EnforcedFlow MCP does not provide historical routing logs or analytics — it only exposes current group state and performs forward routing actions. To analyze distribution fairness, you would need to: (1) use List Group Agents to see current agent metadata, (2) compare those results against your CRM's assignment history, then (3) ask me to calculate variance in ticket counts per agent. EnforcedFlow's API focuses on real-time routing, not retrospective reporting.
This example highlights a key limitation: the MCP cannot retrieve past routing decisions or generate fairness reports. It's designed for forward-looking agent selection, not audit trails. If you need distribution analytics, you'll need to track assignments in your CRM or data warehouse and bring that data into Switchy separately for analysis.
Use-case deep-dives
When EnforcedFlow wins for high-volume inbound routing
A 12-person support team handling 200+ tickets daily needs fair distribution without manual triage. EnforcedFlow's round-robin groups let you route by skill, timezone, or workload—agents get the next ticket matching their configured fields, and the MCP's Select Next Agent tool advances the queue automatically. The catch: if your team is under 30 tickets a day, the overhead isn't worth it; a shared Slack channel and eyeball assignment is faster. But once you hit triple-digit volume and agents start complaining about uneven load, this MCP pays off in week one. Set up your groups in EnforcedFlow's dashboard, then wire the MCP into your Switchy workspace so any teammate can assign the next agent without leaving the conversation.
EnforcedFlow for fair lead distribution in tight teams
A 4-person SDR team closing 40 inbound leads a month wants every rep to get equal shot at high-intent prospects. EnforcedFlow's List Group Agents and Upsert Group Agent tools let you maintain a single source of truth for who's active, on PTO, or ramping—then Select Next Agent picks the fairest match when a lead converts. The trade-off: if your lead volume is under 20 a month, you're better off with a Google Sheet and manual assignment; the API overhead and token cost don't justify automation at that scale. Cross the 50-lead threshold, though, and the MCP eliminates the 'who gets this one' Slack thread every time a demo request lands. Wire it into Switchy and your ops lead can update agent status without touching EnforcedFlow's UI.
When EnforcedFlow handles CSM territory rebalancing
A 6-person customer success team rebalances accounts quarterly as customers churn or expand, and manual reassignment in the CRM takes hours. EnforcedFlow's Get Group Routing Fields and Upsert Group Agent tools let you define routing rules by ARR band, industry, or region, then programmatically update agent assignments when territories shift. The boundary: if you're rebalancing once a year or your CSM count is under 4, a spreadsheet and bulk-update script is simpler. But if you're doing this quarterly and your routing logic has more than two dimensions—say, ARR plus timezone plus product line—the MCP saves 3-4 hours per rebalance and eliminates the 'wait, who owns Acme Corp now' confusion. Connect it to Switchy so your RevOps lead can trigger the rebalance from a shared workspace without API credentials.
Frequently asked
What does the EnforcedFlow MCP do in Switchy?
It automates round-robin lead assignment across your sales or support team. Switchy's AI can query available agents, pull routing rules, and assign the next rep in rotation based on criteria like territory or skill set. You skip manual spreadsheets and get fair distribution baked into your workflows.
Do I need admin access to connect EnforcedFlow?
You need an API key from your EnforcedFlow account. Whoever generates the key must have permission to view groups and agents; most EnforcedFlow admins have this by default. The key authenticates all routing and agent-update requests Switchy makes on your behalf.
Can the MCP create new round-robin groups or only use existing ones?
It works with existing groups only. You configure groups and routing fields inside EnforcedFlow's dashboard, then Switchy reads those rules and assigns agents accordingly. If you need a new group, set it up in EnforcedFlow first.
How is this different from calling EnforcedFlow's API directly?
Switchy's AI decides when to route a lead based on conversation context—no hardcoded triggers. The MCP wraps EnforcedFlow's API so the assistant can check agent availability, apply filters, and log assignments in one natural step instead of you writing integration code.
Does selecting an agent count against my EnforcedFlow plan limits?
Yes. Each time Switchy calls Select Next Agent, it consumes one routing request from your EnforcedFlow account quota. Monitor usage in EnforcedFlow's billing dashboard if you're on a metered plan, especially during high-volume campaigns.