Register interest

Integrations

Works with the systems your leads actually run through.

Routing Forensics works with the systems lead routing actually runs through, and only ever reads them.

SystemWhat it checks or doesHow it connects
SalesforceLead and deal routing: assignment rules, flows, queues, owners, speed to lead, the handoff, territoriesA read-only user your admin sets up
HubSpotContacts with no owner, late assignment, first response, rotations, workflows that set the ownerRead-only scopes; workflows by an export your admin makes
LeanDataHeld leads, routing errors, round robin pools with leavers or nobody available, the processing queueIts records in Salesforce, read by the same user
Traction CompleteRound robins without retraction, criteria that cannot match, routing to people who left, stuck pausesIts records in Salesforce, read by the same user
Omni-ChannelLeads waiting to be offered, and offers declined or timed outSalesforce, read by the same user
Slack and Microsoft TeamsAn alert the first night something breaksAn incoming webhook you create
Zapier, Make, n8n, PipedreamNew and fixed findings as data, to reach Jira, Asana, Linear or a spreadsheetA webhook you create

Alerts and webhooks carry the check, a count and the proof. They never carry a lead.

One independent check across your whole routing stack.

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