Routing Forensics Contact
Free, for Salesforce

Scan your routing configuration.

Drop your routing export here. Every defect comes back graded, with its evidence, the fix and an effort size.

The scan reads Salesforce exports. On HubSpot? The nightly Monitor connects to HubSpot directly: ask for early access.

Your export never leaves this browser. The checks run on this page, in Python loaded from a public CDN (jsDelivr). Nothing is uploaded, stored or sent to us. The export holds configuration only, never a lead or contact record.

  1. 1

    Your admin exports the configuration

    Salesforce only lets a user export configuration if they could also deploy changes, so this is a job for your own admin. It takes a few minutes with the Salesforce CLI.

    Show the commands
    sf org login web --alias ourorg
    sf project generate --name rf-metadata
    cd rf-metadata
    sf project retrieve start --target-org ourorg \
      --metadata AssignmentRules Flow FlowDefinition Queue CustomObject:Lead GlobalValueSet \
      StandardValueSet:LeadSource StandardValueSet:LeadStatus StandardValueSet:Industry

    Then zip the rf-metadata folder.

  2. 2

    Drop the zip

The scan reads assignment rules and active Lead flows, plus queues and picklists when they are in the export. Anything it cannot prove from configuration alone is marked "confirm" rather than asserted. To see what those rules actually did to your leads, every night, ask for early access to the Monitor.