🛰️
Inbound Lead Routing Patrol
Maintain
⏱️
~3 min setup
Hourly Scout check for unassigned inbound leads. Catches broken assignment rules before leads go cold. Slack alert on findings with lead IDs, creation time, and missing routing fields.
The Prompt
Copy this prompt to Claude Code
We keep losing inbound leads because assignment rules break silently. Scout should patrol hourly: 1. Check for unassigned inbound leads created in last 2 hours 2. Check for leads sitting in "Unassigned" queue > 1 hour 3. Check for leads with missing required routing fields (Territory, Region) 4. Flag broken assignment rule patterns 5. Post Slack alert to #rev-ops if any issues found 6. Include lead IDs, creation time, and missing field details Run every hour during business hours (8am-6pm PT).
How It Works
Query recent leads
Find inbound leads from last 2 hours
Check unassigned
Queue backlogs and missing owners
Validate routing fields
Missing territory/region data
Slack alert
Post full details to #rev-ops
Execution Log
💭 thinking
Run hourly patrol and flag routing failures fast.
$ command
g-gremlin scout run routing_patrol --schedule "0 8-18 * * 1-5" --timezone America/Los_Angeles
✓ Patrol started
$ command
g-gremlin scout analyze --check unassigned,queue_time,routing_fields
âš 5 unassigned leads, 3 stuck in queue, 2 missing fields
$ command
g-gremlin notify slack --channel rev-ops --template routing_alert --severity warning
✓ Posted alert to #rev-ops
✓ success
Routing patrol complete. Issues flagged before leads go cold.
Results
23
Leads checked
5
Issues found
<5 min
Response time
47s
Execution time
Try This Workflow
Start with the quickstart guide, then deploy your routing patrol.