Lead Return Policies: What Sellers Publish, and How to Write Yours

What 440 lead companies publish about returns

We read the websites, terms and FAQs of every company in our pay-per-lead directory and recorded what each one says about returns. 186 of the 440 say nothing at all. Another 30 mention the topic without giving terms, such as "pay only for valid leads" with no definition, or a policy page that is linked but empty. That leaves 224 companies with terms of some kind, from a single line to a full page of reasons. The table counts how many of those 224 include each element.

Publishing anything puts a seller ahead: fewer than half of the 440 companies give a buyer reasons they could cite. Of the 151 that do, 96 accept bad contact details, the only reason most of them share, so buyers will expect it. And buyers ask. Of the 209 companies whose sites carry a buyer FAQ, 63 answer a question about returns, refunds or bad leads. If your FAQ does not answer it, the first sales call will.

Credit, refund or replace

The published policies use three remedies. 36 companies offer both credit and replacement, often at the seller's choice.

1. Credit

   The most common remedy, named by 105 of the 224. The returned lead's price goes back onto the buyer's account balance, or comes off the next invoice or order. Several say the credit is the full price paid. A few attach limits: credits that cannot be cashed out, credits capped at the original fee, or credits that expire.

2. Replacement

   84 companies send another lead in place of the bad one. Replacement is most common where leads are sold in fixed orders or packages, so the buyer still receives the count they paid for. It works when you have inventory to spare. It gets awkward in real-time exclusive markets, where a matching replacement may not exist, and one company gives a partial refund when no replacement is available.

3. Refund

   Cash back is the exception. 80 of the 224 say in some form that cash is not refunded, that remedies are credit or replacement only, or that sales are final. Where refunds do appear, they are usually narrow: leads ordered but never delivered (several refund or credit the undelivered part of an order), billing errors, or money still held before delivery. 12 companies go further and say every sale is final, with no credits or replacements for any reason.

For most sellers, credit is the cleanest choice: a refund sends back money already spent on traffic, while credit keeps the buyer funded. It pairs naturally with buyers who fund a balance up front. The prepaid vs. invoiced buyers guide covers why.

Which reasons are accepted, and which are declined

The published policies draw the same line. A lead is returnable when something was wrong with the lead itself. It is not returnable when the lead was fine and the sale did not happen.

Reasons commonly accepted

• Bad contact details. Wrong, disconnected or fax numbers, invalid email, bad address. 96 companies. A few accept this only when both the phone and the email fail.
• Duplicates. The same consumer delivered twice. 65 companies. 26 tie a duplicate to a set lookback period, so a repeat from long ago counts as a new lead, and some count only duplicates of leads they themselves sold.
• Off criteria. The lead fails a filter the buyer chose, or is the wrong lead type or service. 63 companies.
• Out of area. The lead sits outside the geography the buyer set. 53 companies.
• Fake or spam. Fictitious names, bots, test submissions, solicitors, competitors testing the form, or a consumer who denies ever asking. 48 companies, and 16 accept a consumer who denies making the request or a submission that was not a genuine inquiry.
• Wrong person. Not the owner, a renter without the authority to decide, or not the decision maker. 13 companies.

Reasons that depend on the market

The longest policies add reasons tied to what the buyer is actually paying for. Counted across all 224 companies with terms:

Each turns a qualifying question into a return reason. If the buyer pays for an answer, decide in advance whether a wrong answer is returnable.

Reasons commonly declined

28 of the 224 spell out what they will not take back. The list is consistent:

• The prospect was not interested, changed their mind, or had a price or financing objection.
• The prospect bought from someone else, or another company reached them first.
• The lead did not convert, the job was lost, or an underwriter declined the applicant.
• Something on the buyer's side: slow follow-up, too few call attempts, or a filter the buyer never set. 9 companies name buyer follow-up specifically, and some require proof of a prompt first attempt before any return is reviewed.

Buyers will blame the leads when they do not close. A policy that names "did not convert" as not returnable settles that argument before it starts.

Failed criteria, unreachable, or the buyer's outcome

Most return disputes come from mixing up three situations. Sort every request into one before you answer it.

Failed criteria is the seller's responsibility. If the lead does not match the definition the buyer paid for, credit it.

Unreachable is the hard one, because it can be either side's fault. A real number nobody answers may mean a weak source, or a buyer who called once, hours later. The companies that accept it require a stated number of attempts over a stated period, with a log or recording as proof. Decide your position before the first lead, and keep a source sub ID on every lead so a pattern on one source is visible. The speed to lead guide covers what to agree with buyers about follow-up.

Buyer-side outcomes are not lead problems. The consumer was real, matched the criteria and could be reached. Naming these outcomes as not returnable stops a policy from turning into a guarantee of sales.

Windows, evidence, caps and how requests are made

• A window. 106 companies give a set window after delivery, and most of the policies that name reasons include one. Windows range from hours to weeks. Several say a lead not disputed in time is deemed valid, and a few set a shorter window for calls than for form leads.
• Review. 66 say requests are reviewed or approved before credit is issued, and several say the seller's decision is final. A few say they may call the consumer to check.
• Evidence. 30 ask for something with the request: the lead ID and a reason code, notes from the buyer's CRM, documents, or a call recording. A few require a recording before they accept "the consumer says they never asked".
• A place to ask. 32 take requests through a portal or dashboard, and a few through a single button on the lead. Others take them by email or support ticket.
• Exclusions. 20 make some products final sale, most often aged leads, discounted leads, or leads bought with promotional or bonus credit.
• Abuse. Several say a high return rate lowers a buyer's priority, triggers a review or can close the account.
• Calls are judged differently. 12 of the policies treat calls and live transfers by their own rules: billable only past a minimum duration or buffer, judged on the recording, or not returnable once connected.

Return caps

A return cap limits approved returns to a share of the leads a buyer bought in a period, whatever the reason. 8 of the 224 publish one, set per month, per rolling period, per order or per vertical, and one reviews live transfers individually instead of capping them. A cap protects your margin from a buyer who returns everything that does not close. Pair it with the three-way split above: the categories decide which requests count, and the cap limits how many. State it before the buyer funds, and say whether failed-criteria returns past the cap are still reviewed.

Patterns across the directory

Some markets publish far more than others

Companies that sell into several verticals count in each row.

Real estate and legal sellers publish the most detailed reasons, because their buyers pay for narrow facts such as "not listed" or "not already represented". Education, debt relief and lending publish the least, so a clear policy stands out there.

Sellers who state how they get paid also state their returns

Of the 82 companies that say buyers fund a prepaid account, 75 publish return terms, and so do 40 of the 42 that charge a card on file. Of the 298 that say nothing about how buyers pay, only 93 do. Clear funding and clear returns travel together: a credit needs a balance to land on.

Read the agreement, not the homepage

We found 18 companies whose return terms disagree with themselves. A product page promises replacements while the terms say all sales are final. A homepage says "or you don't pay" while the agreement says fees are non-refundable. A returns page gives one window and the FAQ another. When terms conflict, the agreement is what a dispute turns on, so keep one policy and link it everywhere.

Returns flow down to the supply side

Returns do not stop at the seller. Several networks that buy leads from publishers say they do not pay for leads their own buyers reject or return, or that they reverse the payout when it happens. If you resell, mirror your buyer terms in your vendor terms, so a return you accept can be passed back to its source. See how to broker leads.

Write it before the first lead

Kyle's rule for new sellers: the return policy exists before the first lead is sold, and every buyer sees it before they fund. Written after the first dispute, it reads as a reaction to that buyer.

1. Define a valid lead

   List the fields and answers a lead must have to count: the lead type, the area, and the qualifiers the buyer is paying for. Everything else in the policy is measured against this definition.

2. List what you accept

   Start with the reasons most policies share: bad contact details, duplicates, out of area, off criteria and fake submissions. Add the reasons specific to your market, and define a duplicate by a lookback period.

3. List what you decline

   Name the outcome reasons outright: not interested, changed mind, bought elsewhere, no sale, and buyer-side delays. Decide now how you treat a prospect who never answered, and what proof of attempts you require.

4. Choose the remedy

   Credit to the buyer's balance is the simplest. Say whether cash refunds are ever given, and when, and which products are final sale.

5. Set the window and the cap

   Give a set window after delivery, and say that undisputed leads are deemed valid when it closes. Decide whether returns are capped as a share of what the buyer bought.

6. Say how to request one

   One channel, the lead ID, the reason, and any evidence you need. Say who reviews it and how the buyer hears back.

7. Send it before the buyer funds

   Walk through it on the first call, alongside what a realistic contact rate looks like. Setting expectations then is far easier than arguing about them later.

Keep a source sub ID on every lead. When returns cluster on one source, you want to see it and cut it, not average it into everyone else's leads.

A return policy template

Replace each bracket with your own terms.

How returns fit with Juiced

Juiced uses wallet billing. Buyers add funds before leads arrive and are charged when each lead is delivered. When you approve a return, the amount is credited back to the buyer's wallet, which is the most common remedy in published policies. The buyer stays funded and keeps receiving leads, and you never send money back out.

Other pieces line up with a written policy:

• Fields and filters define a valid lead. You set the fields on each lead type, and buyers set their own filters and caps. "Off criteria" then means something you can check against the buyer's settings.
• Delivery records settle arrival disputes. Each delivery attempt keeps its response code and timing, so whether and when a lead reached the buyer is on record. See real-time delivery.
• Repeat submissions are caught early. With ping post, repeat submissions are caught at the ping stage, before a buyer is charged for them.

Juiced does not verify, scrub or screen leads for compliance. The checks behind each accepted reason, and the decision to approve a return, stay with you.

Frequently asked