Lead management softwareEvery lead,
accounted for.
Leads arrive by API or CSV, are checked against your rules, and are routed down your buyer waterfall as they come in. Every attempt is recorded, so you can see exactly where each lead went and why.
What you get
What happens between your endpoint and a buyer's system.
Routed as it arrives
Your supplier gets an answer straight away, and the lead is checked and offered to buyers in real time. Nothing waits for a batch.
Bad leads don't pay out
HLR confirms the phone is live, and dedup and suppression lists run before anything is delivered. If a dedup or suppression check can't run, the lead is held back rather than sent unchecked.
Every attempt on record
Each lead keeps a record of every buyer it was offered to: the outcome, price and response time, what was sent and what came back.
Intake
The same rules for API and CSV leads.
Suppliers post leads to your endpoint in real time, or you drop in a CSV. Both go through the same routing, filters, buyer dedup and suppression before anything reaches a buyer.
- One endpoint per campaign, protected by an API key. Suppliers are told straight away whether a lead was accepted or a duplicate.
- CSV imports of up to 500,000 rows, processed in parallel 50,000-row chunks, with batch HLR as they load.
- New fields are picked up automatically, and the raw request is kept with secrets redacted.
Checks & dedup
Stop bad leads before they pay out.
Each buyer can require a live phone, and every lead is checked against your dedup windows and suppression lists. Dedup and suppression checks fail closed: if one can't run, the lead is held back rather than sent unchecked.
- HLR lookups confirm the number is live and return the network and line type. Choose per buyer whether absent subscribers are accepted.
- Dedup at three levels: when a lead arrives, per buyer (across all your campaigns or just one) and per route, each with its own lookback in days (campaign and buyer dedup can also have no time limit).
- Suppression lists from any campaign, plain or MD5 / SHA-256 hashed, matched on email and phone.
- Smart filters on any field, postcode area, day of the week, buyer history or a reference list, combined with AND / OR.
- TPS / CTPS screening against the UK opt-out registers. Coming soon
Routing & delivery
Down the waterfall until a buyer says yes.
Route groups run in priority order, and within each group you choose priority, round-robin or weighted distribution. Timeouts, errors and rejections move the lead on to the next buyer automatically.
- Daily, weekly and monthly caps per group and per buyer, reset at UK midnight.
- Direct post or ping post, with per-buyer field mapping, static fields, body templates and headers.
- Retries on timeouts, server errors and rate limits, with a timeout you set per buyer.
- Multi-sell: deliver one lead to several buyers in a group.
Built in
On every plan, from day one.
Lead management FAQ
How do API leads and CSV imports differ?
Both go through the same routing, smart filters, buyer and route dedup, suppression and HLR. Campaign-level dedup runs when a supplier posts through the API, so the supplier hears about duplicates straight away. A CSV can also be loaded without distributing it, if you only want the leads stored.
What does dedup match on?
Email address. You can dedupe when a lead arrives in a campaign, per buyer (across all your campaigns or just one) and per route, each with its own lookback in days (campaign and buyer dedup can also have no time limit). Suppression lists are matched on both email and phone.
What happens to a lead that fails a check?
If it's a duplicate, the supplier is told in the API response. If it's on a buyer's suppression list or fails that buyer's own checks, such as HLR, it isn't sent to that buyer and carries on down the waterfall. Every outcome is recorded against the lead, from filtered and capped to rejected and delivered, so you can see why it went where it did.
Can I edit or resend a lead after it's in?
Yes. You can edit a lead's fields and redistribute it through your routing, with options to skip caps, filters, suppression or buyer dedup for that one send. Buyers can return leads too, which reverses the revenue on that lead.
What if a buyer is slow or down?
Each buyer has its own timeout. If it times out, errors or rejects the lead, the next buyer in the waterfall gets it. Network errors, server errors and rate limits can be retried. Every attempt is stored with the response code, body and timing, and you can get push alerts for delivery failures and caps.
Send us
your first lead.