Local lead routing is a delivery system, not merely a CRM assignment rule. A weekly report should show whether a request reached the correct location, owner, queue, and next action, and whether the outcome matured. Aggregate lead volume can hide a location with a broken phone, an unworked form, a duplicate, or a queue that has no capacity.
1. Define the weekly decision
Write what the review may change: routing rule, location coverage, response SLA, source investment, form fields, staffing, booking path, or reporting definition. Name locations, services, source systems, time zone, sales cycle, capacity, report owner, and stop rule.
Choose a stable review window and a maturity rule. A lead received yesterday may be useful for routing health but not for a final quality verdict. Keep current, mature, and unknown cohorts separate.
2. Create a location-aware record contract
Every request should retain location ID, service, source, campaign or referral, landing path, contact key, consent state, received timestamp, owner, queue, and routing decision. Define wrong location, outside area, duplicate, missing location, unassigned, transferred, and shared-account states.
The Salesforce lead implementation guide can prompt explicit definitions for ownership, qualification, conversion, and disposition. Map those concepts to local locations and services; do not assume a CRM stage is a routing outcome.
3. Reconcile sources before evaluating teams
Join form, call, booking, profile, advertising, chat, and partner records using stable IDs and timestamps where the privacy design allows it. Preserve first source, latest source, location, service, and transfer history. Flag missing, overwritten, duplicate, and unjoinable records.
For web actions, the GA4 event documentation describes events as measurements of interactions. Use events such as form_submit, call_connected, and booking_confirmed as inputs, then reconcile with actual routed and accepted records. A local event count is not a completed job.
4. Report routing health separately from lead quality
Routing health metrics include assigned rate, wrong-location rate, unassigned age, transfer rate, duplicate rate, first-response time, SLA compliance, queue age, and failed notification. Lead-quality metrics include accepted, wrong fit, service unavailable, no response, opportunity, appointment, completed work, and margin where available.
Do not penalize a location for a lead it never received. Do not call a slow response a low-quality lead. Show the first broken handoff and its owner. Use reason codes that a manager can act on rather than a single “bad lead” bucket.
5. Make capacity and local exceptions visible
Record open slots, staffing, holiday hours, service limits, language coverage, travel radius, and booking restrictions. A route can be technically correct and operationally wrong when a location is full or temporarily closed.
Keep central and local ownership distinct. Central marketing may own source and campaign; the location may own availability and response; revenue operations may own stage and data quality. Assign escalation for a location that cannot meet the declared SLA.
6. Define weekly cohorts and lag
Break the board by location, service, source, device, campaign, day, owner, and maturity. Compare similar cohorts and preserve the start date, lead age, attribution window, sales cycle, and last refresh. Avoid ranking locations with different offers or capacity as if they were identical.
If paid channels use offline outcomes, the Google Ads conversion measurement documentation can clarify platform conversion concepts. Keep platform conversion, routed lead, accepted lead, opportunity, and completed work in separate columns. A lower reported cost per lead does not prove better local economics.
7. Turn the report into a decision log
For each exception record observation, evidence, owner, action, expected effect, due date, and stop condition. Examples: repair a phone queue, add a location field, split a service, change a fallback, pause a campaign, add staffing, or keep observing.
Review a small sample of records, not only totals. Ask the local owner whether the request was reachable, serviceable, timely, and correctly described. Record disagreement and unknown rather than forcing a clean explanation.
8. Run a bounded routing repair
Choose one location, one source, one service, and one review window. Change one routing element and freeze other major variables. Snapshot counts, queue age, response, accepted quality, capacity, appointments, and mature outcomes. Keep a parallel or pre-change comparison when it is genuinely comparable.
Stop if privacy or consent is unclear, the notification path fails, the queue exceeds capacity, records duplicate, or the change sends urgent requests to an unowned route. Preserve old rules, the new mapping, test records, and rollback authority.
9. Apply the weekly routing gate
| Gate | Required evidence | Hold if | | — | — | — | | identity | location ID, service, source, contact, consent | location is inferred from free text | | routing | rule, owner, queue, transfer, fallback | unassigned records age silently | | response | received, first attempt, SLA, escalation | delay is hidden in a total | | quality | accepted, reason, appointment, outcome, maturity | all leads share one status | | capacity | slots, staff, hours, area, exception | route is unworkable locally | | measurement | event, join, dedupe, source, version | platform count is called delivery | | action | owner, repair, due date, stop, review | report has no decision rights |
Choose repair the route, add a field, split a queue, change local capacity, adjust source, keep observing, or hold. Preserve the weekly board, record sample, rule version, owner map, exceptions, decisions, and next review date. Keep this framework local and non-indexable until current CRM, analytics, privacy, overlap, and editorial review are complete; it does not guarantee faster response, more appointments, or revenue.
How did this article land?
Choose one reaction. You can change it anytime.
