A routing tool's log is the right place to see what the tool did to a lead it handled. It is not built to tell you about the leads it never touched, or what happened after it finished.
| Question | The router's log | Routing Forensics |
|---|---|---|
| What did the tool do to this lead? | Yes | Yes, read from the same log |
| Which leads never reached the tool? | Not recorded | Counted from your leads |
| Did a flow change the owner afterwards? | Not its concern | Traced, in Salesforce's order |
| Is the tool set up so leads go nowhere? | Only if it errors | Checked from its configuration |
| Did a fix actually hold? | No | Proven by the next night's run |
Two things we found on real orgs
- LeanData's "Owner Changed?" field compares users only, so a lead moved into or between queues reads as unchanged.
- Traction Complete keeps its history log only while history logging is switched on, and on a fresh install it was off: leads routed and nothing was recorded.
Neither is a flaw in the tool. They are why a check that sits outside the tool is worth having.
See what your own routing is missing.
Routing Forensics connects as a read-only user and checks your routing against your real leads every night. Register interest and you will be first to get a free health report.
Or check it now: the free scan finds routing configuration defects in your Salesforce or HubSpot workflow export, in your browser, and nothing is uploaded.
More about Routing Forensics
- What Routing Forensics can touch in your CRM: nothing.
- Every check is proven on real Salesforce before it reaches you.
- The lead routing health checklist.
- Works with the systems your leads actually run through.
- A Salesforce report shows what matches. Not what is broken.
- An audit is a photograph. Routing changes every week.