May 18, 2026 · 5 min read
Lead Routing Rules That Were Silently Broken for Four Months
A single field rename in the CRM silently broke lead routing for an entire territory. Nobody noticed for four months because the leads were still going somewhere, just the wrong somewhere.
A CRM admin renamed a custom field from "region_code" to "territory_code" as part of a broader cleanup project, intending it to be a harmless rename with no functional change. One lead routing rule, built years earlier by someone no longer at the company, referenced the old field name directly in a conditional. The rule didn't error out — it just silently failed its condition check and fell through to a default routing path that sent every affected lead to one overworked rep instead of the correct regional team.
Why nobody caught it for four months
The leads were still being routed somewhere, and that somewhere was a real sales rep who was responding to them, just slower and with no regional context, because they were buried under leads that weren't actually theirs. Nothing in the pipeline threw an error. The only signal was a gradual increase in that one rep's response time and a gradual, unexplained dip in that territory's conversion rate — both slow enough trends that they got attributed to "a tough quarter" before anyone looked at routing logic specifically.
A routing rule that fails silently into a default path doesn't look broken, it looks like a slightly worse quarter.
What finally surfaced it
A new rep joining that territory asked why they weren't getting any inbound leads, which prompted someone to actually trace a specific lead through the routing logic end to end instead of trusting the dashboard summary. That one manual trace found the dead reference within twenty minutes.
- Any field rename in a CRM needs a dependency search across automation rules first, not just a rename-and-check-for-errors approach.
- Routing rules that fail their condition should log the failure and fall-through explicitly, not just silently default.
- A monthly spot-check — manually trace five random leads through routing end to end — would have caught this in week one instead of month four.
- Default routing paths should alert someone when volume to them spikes, since a healthy system rarely needs the default path much.