Build dynamic intake routing rules by urgency and capacity

Design weighted logic to automatically assign incoming requests based on submission urgency, agent workloads, and business hours.

You getRouting Decision Tree, capacity & Weighting Rules and SLA & Escalation Protocol

Prompt

Prompt
You are a business operations architect designing an automated intake routing engine for client forms.

First, ask me 2-3 short numbered questions in one message to understand:
1. What intake categories or urgency signals are submitted on the form
2. The size of the team handling submissions and current skill specializations
3. Which tools run the intake workflow (e.g., Zapier, Make, HubSpot, Jira, Zendesk)

Wait for my answers. Once answered, design an assignment architecture that routes high-priority requests instantly while balancing standard tickets based on active user workload and operating schedules.

Output format:
- Routing Decision Tree: Step-by-step logic gate from submission to assigned owner
- Capacity & Weighting Rules: Criteria for calculating agent active load limits
- SLA & Escalation Protocol: Timed triggers when submissions remain unassigned or unaddressed
- Tool Configuration Checklist: Exact triggers, filters, and actions to set up in the workflow builder

Example output

Example for: IT helpdesk handling security incidents, hardware requests, and software provisioning

Routing Decision Tree
  1. Inbound Submission Check: New ticket triggers workflow.
  2. Severity Gate:

    • IF Severity = P1 (Outage/Security): Override all queue rules -> Send immediate page to On-Call Engineer -> Assign ticket to On-Call queue.
    • IF Severity = P2/P3: Evaluate specialization tag (Hardware vs. Software).
  3. Availability Gate: Filter eligible agents where Status = "Available" AND Current Open Tickets < Capacity Limit (8 tickets).
  4. Workload Check: Among qualified, available agents, assign to the agent with the lowest active ticket count.
  5. Off-Hours Routing: If submitted outside 08:00–18:00 local time, route P1 to PagerDuty; route P2/P3 to unassigned holding queue for next-day 08:30 round-robin.
Capacity & Weighting Rules
  • Agent Thresholds: Maximum 8 active tickets per tier-1 specialist; maximum 4 for tier-2 seniors.
  • Weighting Factor: P1 tickets count as 3 active tickets toward cap; P2 tickets count as 1.5; P3 requests count as 1.
  • Pause Conditions: Agents scheduled in training, PTO, or with "Do Not Disturb" calendar events are auto-excluded from routing pool.
SLA & Escalation Protocol
  • P1 First Touch SLA (15 mins): If unacknowledged at 10 minutes, escalate to Operations Manager via SMS.
  • P2 First Touch SLA (2 hours): If unassigned at 45 minutes, round-robin automatically overrides capacity caps and assigns to the least loaded tier-2 agent.
  • Stalled Ticket Alert: Any ticket inactive for 24 business hours alerts the team lead.
Tool Configuration Checklist
  • Trigger: New Form Submission received.
  • Filter 1: Check metadata field urgency_level.
  • Action 1: Lookup table query checking agent active assignment counts via API.
  • Action 2: Conditional split for business hours versus on-call schedules.
  • Action 3: Assign user ID to record and post audit log entry into team Slack channel.
Written by AI from this prompt. Your results will vary.

Paste this prompt into ChatGPT, Claude, or Gemini without changing a word. Answer the 3 intake questions the model asks in your first reply. Follow up by asking for JSON logic payload examples matching your chosen automation tool.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Automation & Workflows