← Platform home
Platform

Lead history and purchase intelligence

A new request can reach a buyer after several providers have called, quoted or completed the work. Follow the evidence for the requested service before deciding whether to buy.

Trace the inquiry

Read its origin, dated deliveries and reported outcomes in the history available to your organization.

Test your buying rules

Start at 100. Apply your deductions and see which conditions moved the score.

One inquiry across multiple sellers

Confirmed shared references connect separately owned submissions for the same service inquiry. Combined history counts each buyer once across sellers, while retaining every delivery and permitted confirmed purchase. Supplier names and confidential transaction details remain protected.

Multi-seller example

Across Sellers, Count Every Buyer Once.

The same confirmed service inquiry can arrive through several sellers. LeadRegistry keeps their submissions and transactions separate, while combining the history you have permission to see.

2Sellers
6Confirmed purchases
5Distinct buyers

Seller 1 reaches Buyers 1, 2 and 3. Seller 2 reaches Buyers 1, 4 and 5. Buyer 1 appears twice, so six purchases represent five distinct buyers—not six. Each chargeable purchase remains a separate transaction.

Automatic checks flag possible cross-seller matches even when seller lead IDs differ. History shows the matching evidence and review status. Unconfirmed flags keep their histories, buyer counts and scores separate. Confirmed shared references link the same service and original inquiry, with agreeing identifiers and active permissions. Contact details alone do not merge different projects. Seller labels protect identities; circulation through two sellers does not prove a resale between them.

Try the multi-seller lead example Try possible-match review
Demo workspaceLead historyExposure & riskPre-ping & routingDisposition intelligenceBuyer policiesIntegrations