Guide

LeanData is routing, but some leads are going nowhere.

LeanData keeps a routing log for every record it routes. Most problems are in there, if you know where to look.

Routing errors

A log with an error was not routed as intended. The error text is a long text field, which Salesforce cannot filter on, so a report cannot count them for you. Read the logs and count those with an error.

Pools with nobody available

A round robin pool whose members are all Unavailable, or inactive, still receives leads. Check each pool that routed a lead in the last 30 days has someone available.

A change the log does not flag

The log's "Owner Changed?" field compares the owner before and after, users only. A lead moved into or between queues reads as unchanged. Compare the before and after owner yourself, queues included.

Check it yourself

SELECT LeanData__Error_Details__c FROM LeanData__Log__c WHERE CreatedDate = LAST_N_DAYS:30
SELECT COUNT() FROM Lead WHERE LeanData__Routing_Action__c = null AND IsConverted = false AND CreatedDate = LAST_N_DAYS:30

Have it checked every night instead.

Routing Forensics connects as a read-only user and checks this, and the rest of your routing, against your real leads. Register interest and you will be first to get a free health report: what is leaking, where, and what it is worth.