Lead Distro AILead Distro AI
DocsBuyersReturns Flow

Returns Flow

How Lead Distro AI buyer returns work. Submit returns from the Partner Portal, accept/reject from your dashboard, auto-accept thresholds, return rate tracking, and FAQs.

Last updated:

What Are Lead Returns?

A return is a buyer's request to reverse a delivered lead — they're saying the lead was bad-quality, off-vertical, duplicate, or otherwise not what they paid for. If you accept the return, the lead's revenue is reversed in your P&L and the buyer is refunded (via wallet credit or invoice adjustment).

How Returns Flow Through the System

  • Buyer submits return from the Partner Portal with a reason (wrong number, no response, duplicate, bad data, not qualified, or other), optional details, and optional proof files.
  • Return appears in your dashboard — pending review.
  • You decide: accept (revenue reversed), reject (no change, return denied), or open a thread to negotiate.
  • If accepted: the lead's status flips to RETURNED, revenue is deducted from accrued spend (Net Terms) or refunded to wallet (prepaid), and your P&L reports update.

Return Reasons

ReasonMeaning
Wrong NumberThe phone number doesn't reach this person
No ResponseThe buyer tried to reach the lead and never got an answer. A common reason to require proof files
Duplicate LeadThe buyer already had this person from another source
Bad / Inaccurate DataFields are wrong, fake or incomplete
Not QualifiedThe lead doesn't meet the buyer's criteria
OtherAnything else. The buyer explains in Details

Return Policy and Required Details

Open a Destination, go to Partner Portal → Portal Settings, and set the return rules it sees when it asks for a return:

  • Return policy note: turn on Show return policy note and write it. It shows in a yellow box above the return form. Format it with bold, *italic*, bullet lists and numbered lists (up to 2,000 characters).
  • Require details: the Destination must explain each return before it can send it.
  • Minimum length: with Require details on, the explanation must be at least this many characters (1 to 1,000). Leave it blank to accept any text.

One set of rules covers lead, appointment and call returns, so you cannot set different rules per type. The portal shows a live character count, and a return that is too short is refused.

Proof Files on a Return

A Destination can attach proof to a lead or appointment return in the Partner Portal, such as screenshots of its call log or an export from its dialer or CRM. Files can be PNG, JPG, WEBP, PDF or CSV, up to 5 files of 4 MB each. Screenshots are shrunk before upload, so large ones still fit. Call returns do not take files.

  • Require proof for some reasons: in Partner Portal → Edit Settings, turn on Require proof files and pick the reasons that need it in For these reasons (for example No Response, or All reasons). For those reasons the Destination cannot send the return until it attaches at least one file. Every other reason keeps files optional.
  • See the files: open the return on the Returns page (a paperclip shows how many files it has) or on the lead's page. Screenshots open full size, PDFs and CSVs download. Links last 60 seconds, so the files are never public.
  • The Destination's view: the Partner Portal's Returns page lists the files each request was sent with.
  • Check proof with your AI: in Claude or another AI app connected to Lead Distro AI, ask it to review your pending returns. It finds them with list_returns and opens each file with get_return_attachment: it reads screenshots and PDFs itself and gets a CSV as text. Each file also comes with a download link that lasts 10 minutes. Approving or denying a return still happens on the Returns page.

Auto-Accept Thresholds

Configure auto-accept rules per buyer to reduce manual review. Common pattern: automatically accept returns submitted within 24 hours of delivery, leaving older returns for manual review. Strong return policy (always accept) signals confidence in lead quality and reduces buyer-side friction; tight return policy (manual review every time) protects revenue from abuse.

Return Rate Tracking

Each buyer's return rate (RETURNED / ACCEPTED) is a key quality metric in Reports. High return rate signals either lead-quality issues (your suppliers sending bad leads) or buyer-side intake problems (the buyer is rejecting good leads to lower their effective cost). Compare return rates across buyers and across suppliers to localize the issue.

Track return rate per supplier in Insights Drill-Down. A spiking return rate from one supplier means their lead quality dropped — investigate before the issue compounds across multiple buyers. A spiking return rate from one buyer (across multiple suppliers) means the buyer's intake standards changed — talk to them.

Frequently Asked Questions

How do buyers submit returns in Lead Distro AI?
From the Partner Portal — open the lead, click Submit Return, pick a reason and add details (required when you turn on Require details in Portal Settings). The return appears in your dashboard as 'pending review' for accept/reject. Auto-accept rules can skip the review step for fast-cycle returns.
Can buyers attach proof, like call-log screenshots, to a return request?
Yes. In the Partner Portal's return form a Destination can attach up to 5 files (PNG, JPG, WEBP, PDF or CSV, 4 MB each). You see them when you review the return. To make proof mandatory for a reason such as No Response, open the Destination, go to Partner Portal → Edit Settings, turn on Require proof files, and pick that reason in For these reasons.
Can my AI read the proof files on a return?
Yes. With Lead Distro AI connected to Claude or another AI app, the get_return_attachment tool hands the AI the files on a return: it sees screenshots and PDFs and reads a CSV as text. Each file also has a download link that works for 10 minutes. The AI can tell you whether the proof backs up the return, but approving or denying it stays on the Returns page.
What's a healthy return rate?
Industry typical: 3-8% depending on vertical. Below 3% suggests buyers might be too conservative (paying for marginal leads they could've returned); above 10% suggests quality or intake issues. The right number is vertical-specific — competitive verticals (legal, mortgage) tolerate higher returns than long-cycle B2B leads.
Can I configure auto-accept on returns?
Yes — set a threshold (e.g., 'auto-accept returns submitted within 24 hours of delivery'). Useful pattern: auto-accept fast returns to reduce review friction, manually review slower returns where the buyer had time to convert the lead and may be reversing only because conversion failed. Configure per-buyer.
What happens to revenue and cost when a return is accepted?
Revenue: deducted from the buyer's accrued spend (Net Terms) or refunded to the wallet (prepaid). Cost: depends on supplier cost mode. For Fixed cost, cost stays — you still paid the supplier even though revenue reversed. For Revenue Share, cost reverses proportionally (75% of $0 = $0). For Variable Meta, cost stays (Meta spend already happened). The lead's profit becomes negative when revenue reverses but cost doesn't.
Can I dispute a return submission?
Yes — reject the return instead of accepting. The buyer sees their return was rejected with your reason. For high-stakes disputes, open a thread inside the return detail page to negotiate (e.g., partial credit, replacement lead). For chronic disputes with one buyer, this is a relationship issue — the integration provides the data, you handle the conversation.
Do returned leads count in P&L?
Returned leads (RETURNED status) have their revenue reversed in Profit calculations. P&L by default shows net revenue (post-returns). Toggle to gross revenue (pre-returns) in Reports if needed for sales conversations. Cost stays attributed to the lead regardless of return — that's a sunk cost in most supplier cost modes.

If you have any questions, send us an email at support@leaddistro.ai