Inbound Lead Routing Patrol

ScoutMaintain

~3 min setup

Example scout operating loop for routing review. Start with Gremlin's unassigned inbound detection, add routing-field context, and alert RevOps with evidence.

Where this fits in Gremlin Scouts

This playbook is a concrete scout use case, but it is not a claim that one shipped scout primitive does every step shown here. It is an example operating loop built around `unassigned_inbound` plus adjacent CRM checks.

This example focuses on routing failure detection: run the scout on demand or on a customer-managed schedule, package the evidence, and route the issue before leads go cold. For the concept hub, start at Gremlin Scouts. For the detection-versus-execution split, see Scouts vs. Modules.

The Prompt

We keep losing inbound leads because assignment rules break silently. By the time we notice, leads are cold.

Use Gremlin's scout layer plus adjacent CRM checks:
1. Run unassigned_inbound against recent inbound leads
2. Check queue backlog and missing routing fields
3. Summarize likely broken assignment patterns
4. Post a Slack alert to #rev-ops with lead IDs and timestamps
5. Hand the issue to the owner who fixes routing rules

Run this as a recurring scout workflow on customer-managed infrastructure during business hours.

How It Works

1. Run Unassigned Inbound Scout

Use unassigned_inbound to surface recent leads with missing owners or queue ownership

2. Check Routing Context

Review queue backlog and recent inbound timing around the scout findings

3. Validate Routing Fields

Check for missing Territory, Region, or other routing criteria around the affected leads

4. Summarize Likely Pattern

Package the likely routing failure pattern for RevOps review

5. Slack Alert

Post alert to #rev-ops with lead IDs and issue details

Execution Log

After you paste this prompt, Claude Code:

"Routing patrol kickoff. I'll anchor this review in Gremlin's unassigned inbound scout, then add routing-field context for RevOps."

Running

$ g-gremlin scout run unassigned_inbound --param lookback_days=1 --param sobjects=Lead --format json --output unassigned_inbound.json

[Scout] Check: unassigned_inbound [Scout] 5 recent inbound leads missing owners or stuck in queue

Running

$ sf data query --query "SELECT Id, Name, Email, Company, OwnerId, CreatedDate, Territory__c, Region__c FROM Lead WHERE CreatedDate >= LAST_N_HOURS:2 AND LeadSource IN ('Website','Demo Request','Contact Form')"

23 inbound leads found in last 2 hours

"Now I will combine the scout findings with routing-field context and summarize the likely rule failure for RevOps review."

Running

$ combine scout findings with routing-field context

[Review] 5 leads unassigned, 3 leads sitting in queue too long, and 2 leads missing Territory__c

Running

$ summarize likely assignment-rule pattern

[Pattern] Likely EMEA assignment-rule miss: 3 United Kingdom leads stayed unassigned instead of routing to the EMEA queue

Preparing the RevOps handoff package

Alert includes 5 unassigned lead ids, timestamps, missing routing fields, and the likely EMEA assignment-rule miss

Running

$ handoff artifact: RevOps alert draft

[Slack] Drafted for #rev-ops: Lead Routing Patrol Alert - 2:00 PM PT Issues found: - 5 unassigned inbound leads - 3 leads in Unassigned queue too long - 2 leads missing Territory field Likely pattern: EMEA assignment rule appears broken 3 UK leads did not route to the EMEA queue

Routing patrol workflow complete. Unassigned inbound leads were surfaced, routing context was packaged, and RevOps received a reviewable handoff before more leads went cold.

The Result

In this example, the scout surfaces unassigned inbound leads quickly, then the workflow adds routing context and hands the issue to RevOps. Any downstream fix still belongs to a controlled execution path.

Leads checked

Issues found

<5 min

Response time

47s

Execution time

Detection pattern

Example recurring workflow anchored in `unassigned_inbound` plus supporting CRM checks.

Evidence shape

Lead ids, timestamps, missing routing fields, and routing context for RevOps review.

Execution boundary

The scout surfaces the issue fast. Any downstream fixes still belong to a controlled execution path.

Stop Losing Inbound Leads to Broken Routing

Start your free 30-day trial. No credit card required.

Start Free Trial More Playbooks Explore Scouts