# 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.

Status: Discuss an integration

## 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.

## Where $80,000 of lead spend went

- Leads bought: 2,000
- Lead spend: $80,000
- Automated, no validated demand: 240
- Spend at stake: $9,600

Illustrative example. 2,000 leads at $40; 12% automated with no validated demand. Hypothetical.

## The supplier report, two ways.

| | Reported | With evidence |
|---|---|---|
| Payable leads | 2,000 | 1,760 |
| Cost per real lead | $40.00 | $45.45 |
| Spend at stake | $0 | $9,600 |

Illustrative example.

## Your numbers

Spend at stake = leads × share automated × price. Cost per real lead = spend ÷ leads not automated.

## 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

1. **Check at submission.** Run an action check on the lead form when it is submitted.
2. **Verify on the server.** Verify the signed token server-side with @doubleagent-so/node.
3. **Store with the lead.** Keep the evidence beside the lead id and supplier in your CRM.
4. **Join outcomes.** Compare accepted, rejected and qualified leads per supplier.

## What your team can do

- **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 your lead workflow](mailto:support@doubleagent.so?subject=Use%20case%3A%20Paid%20lead%20verification)

- [Server verification](https://doubleagent.so/docs/server/)
- [Double Agent for lead generation](https://doubleagent.so/for/leadgen/)
- [All use cases](https://doubleagent.so/use-cases/)