Leads and partnershipsDiscuss an integration
Add evidence before you accept a paid lead.
Every accepted lead is a payment. Bring automation evidence into the acceptance step, so leads with no real demand behind them are held for validation before the invoice arrives.
For lead marketplaces, buyers and agencies paying per accepted lead.
Opens your email app, addressed to support@doubleagent.so.
See how it worksWhere $80,000 of lead spend went
- Leads boughtLeads bought: 2,000
- Lead spendLead spend: $80,000
- Automated, no validated demandAutomated, no validated demand: 240
- Spend at stakeSpend at stake: $9,600
Human 86%Agent 2%Bot 10%Unknown 2%
Where money is affected
A lead becomes money the moment you accept it.
Suppliers are paid per accepted lead. Automated submissions with no validated demand cost the same as real ones, and disputing them afterwards costs more.
An agent is not automatically a fake customer: a shopping agent can request a real quote. And human submissions can be invalid too. Evidence is one input next to contact validation and duplicate checks.
The real picture
The supplier report, two ways.
Illustrative example Hypothetical figures; your own numbers will differ.
Your numbers
What it could mean for you.
Replace the example with your own figures.
- Spend at stake
- $9,600
- Cost per real lead
- $45.45
- Leads to hold for validation
- 240
Spend at stake = leads × share automated × price. Cost per real lead = spend ÷ leads not automated.
Illustrative example Your numbers, not a promise. Savings depend on the decisions you make with the evidence.
An example decision
One lead, before it is accepted.
- Lead
- L-10428
- Supplier
- sup-114
- Automation evidence
- bot · confidence high
- Decision
- Hold for validation
Contact checks and duplicate checks still run. The lead is not paid until it passes.
How it fits
From evidence to a decision.
- 01
Check at submission
Run an action check on the lead form when it is submitted.
- 02
Verify on the server
Verify the signed token server-side with @doubleagent-so/node.
- 03
Store with the lead
Keep the evidence beside the lead id and supplier in your CRM.
- 04
Join outcomes
Compare accepted, rejected and qualified leads per supplier.
What your team can do
Act on it, your way.
Hold a lead
Route likely automated leads to validation before acceptance.
Review a supplier
See acceptance, qualification and disputes next to detection coverage.
Keep real agent leads
Treat an agent making a real request on its own terms.
Before you start.
Is every automated lead fake?
No. An agent can submit a genuine request for a person. Your validation decides; the evidence informs it.
Is a session label enough to reject a lead?
No. A complete decision needs action evidence at submission, server verification and your own outcome data.
Is this a finished marketplace integration?
The action checks and server verification exist today. The lead-marketplace integration and supplier report are proposed.
What about leads you cannot classify?
They stay unknown. An absent bot signal does not prove a person was there.
Discuss an integration
See the real picture.
Opens your email app, addressed to support@doubleagent.so.
Server verificationDouble Agent for lead generationAll use cases