Lead Routing Under a No-Code, Six-Week Deadline
Northwind Components is a B2B manufacturer with 85 inside sales reps in four regions. It receives about 1,200 inbound leads a month from web forms, trade shows, and a partner portal. Today one active lead assignment rule set sends every lead to one of four regional queues; reps self-assign from list views. Three reps per region are supposed to work leads round-robin. In the last quarter, 22% of leads had no first touch within 48 hours, several prospects were contacted by two reps, and managers say top performers cherry-pick the easiest leads. The partner channel manager must receive all partner-sourced leads and no inside rep should see them. Northwind has no Apex developer, can buy one AppExchange app, and must launch in six weeks.
1. Recommend a lead routing architecture that meets the six-week, no-Apex constraint. Explain what each layer does and why it is needed.
Read the worked answer
Use assignment rules for deterministic segmentation and a routing app for distribution. The assignment rule set should be the first pass: partner-portal leads go to a partner channel queue owned only by the channel manager; everything else goes to the correct regional queue based on a reliable field such as country or region. Keep lead organization-wide defaults private and control visibility through queue membership so inside reps cannot see partner leads.
Assignment rules can route to a user or queue, but queues are pools, not round-robin engines. Self-assignment from a queue list view explains the cherry-picking and the 48-hour gap. Add one AppExchange routing app that reads queue membership and assigns round-robin or by capacity. This is faster and safer than building a custom round-robin in Flow with two admins and six weeks.
Add a scheduled Flow escalation: if a lead has no first touch after four business hours, reassign it or alert the manager. Track first touch with a custom timestamp set when the first Task is created. Add duplicate rules and matching rules on email, phone, and company so two reps do not work the same prospect.
2. The VP of Sales proposes one central queue where reps claim leads first-come, first-served. Evaluate this against the current problems and constraints.
Read the worked answer
A single claim queue would reduce double contact because only the claiming rep owns the lead, but it would worsen the two biggest symptoms: cherry-picking and slow first touch. Reps would watch the queue for easy leads, and undesirable leads would age even longer. It also creates no accountability for follow-up because ownership begins only when someone claims the lead.
It also conflicts with the partner requirement. If partner leads sit in the same queue, inside reps may see or claim them. A separate partner queue is mandatory regardless of the model.
If leadership insists on a claim model, limit it to a small exception pool and pair it with a service-level escalation and capacity reporting. Do not use it as the primary model for 1,200 monthly leads across four regions. Keep assignment-based ownership and use the AppExchange router to distribute fairly.
3. What reports, dashboards, and operating cadence would prove the routing fix is working?
Read the worked answer
Build a small set of operational reports, not a vanity dashboard:
- Lead aging by queue and owner: open leads with age since created and since last activity; highlight over 48 hours.
- First-touch time: use the custom first-touch timestamp; report median and percentage under four business hours by region and source.
- Duplicate prevention: count duplicate-rule alerts and blocked saves; review weekly for false positives.
- Partner queue SLA: partner leads by status and age, visible only to the channel manager and sales ops.
- Source-to-conversion: conversion rate by source and region to catch routing that sends high-value leads to low-capacity reps.
Use a dynamic dashboard so each regional manager sees their team, and schedule a weekly 30-minute routing review for the first quarter. Targets: 95% first touch within four business hours, under 5% untouched after 48 hours, and fewer than two duplicate outreach cases per week. Review queue membership monthly because round-robin fairness depends on it.