What Should a Pay-Per-Call or Lead Return Policy Include? A Buyer's Guide to Credits and Disputes

What is a call or lead return policy?

A return policy (also called a credit, refund or dispute policy) is the part of a pay-per-call or pay-per-lead agreement that defines when a delivered call or lead does not count, and how the buyer gets the money back. It is the other half of the billable-call definition: the billable rule says what you pay for, and the return policy says what you can take back after the fact.

In practice the credit usually goes back to your account balance rather than to your bank. Axel PR's billable-call guidelines (effective October 21, 2026) say approved credits "go back to your balance." Callers.io's buyer terms (accessed November 10, 2026) go further: credits "have no cash value, may not be redeemed for cash" and "may expire twelve (12) months after purchase unless otherwise required by law." If you prepay, read that clause as closely as the price.

Which calls and leads are usually creditable?

Across the public policies we reviewed, the same core reasons appear again and again. Wording and proof requirements vary, so treat this as a starting list for your contract, not an industry standard:

• Wrong number or disconnected number. eLocal credits a call when the caller "is looking for a specific person, provider, or business by name" and realizes it is the wrong number. PingCalls credits "disconnected or wrong numbers."
• Duplicates. The same caller or lead delivered again within a set window (see the table below for how much that window varies).
• Outside your geography. eLocal credits calls from outside your account ZIP code list; Axel PR credits "callers outside the service area or licensed states you defined."
• Not a prospect. eLocal treats job seekers as invalid calls; Axel PR credits "solicitors, vendors, recruiters, job seekers, and other businesses selling to you," plus existing customers calling about work already booked.
• Spam, robocalls or non-human traffic. Callers.io lists "non-human or spam call" as a return reason.
• Wrong vertical or misroute. Callers.io lists "wrong vertical or obvious misroute."
• Calls that end before the billable threshold with no intent shown. Axel PR credits "calls that drop before the buffer time with no intent established."
• For web leads: invalid contact data. eLocal treats "a lead without valid contact information" as invalid. boberdoo says its most common standard refund reasons include non-working phone numbers, low-quality leads and reaching an answering machine (August 4, 2021).

What is usually not creditable?

The exclusions matter as much as the inclusions, and they are where most disputes are lost. Common ones in published terms:

• Sales outcomes. PingCalls says "no answer, not interested, price shoppers, and capacity reasons are not returnable." Callers.io excludes disputes based on the buyer's "dissatisfaction with a Call outcome or conversion."
• Calls you did not answer. eLocal treats a call that rang for 10 or more seconds as billable even if the customer hangs up, and also bills calls the buyer declines or hangs up. Axel PR says calls that ring during your posted hours are billable "whether or not you answer, including calls that go to voicemail."
• Calls you worked anyway. eLocal denies wrong-number and out-of-area credits if the call "develops into a valid sales opportunity," such as setting an appointment or a callback commitment.
• Call handling. eLocal says credit will not be provided if the call is answered "in an unprofessional manner."
• Late claims. Every policy we reviewed has a filing deadline; after it passes, the dispute option may simply disappear from the dashboard (eLocal).

How long do you have to dispute a call or lead?

Published windows vary widely, as the comparison below shows. A 72-hour window and a 7-day window lead to very different outcomes if your team only reviews recordings once a week, so match the dispute window to how often you actually audit calls, or negotiate the window to match your audit cycle.

How are duplicates defined, and why does the window matter?

"Duplicate" sounds simple but every policy above defines it differently: by phone number (Axel PR), by caller and service need (eLocal), only if the earlier call converted (Callers.io), or by a window agreed per account (PingCalls). eLocal also limits duplicates to calls received through eLocal: "If you receive additional calls from the same caller through another lead provider, these are not eligible for credit."

Ask three questions. Is a duplicate matched on phone number, on caller plus product, or on a converted earlier call? Does the window start at the first call or at the first billed call? And are duplicates removed automatically or only when you file? eLocal says it will "automatically credit you for the duplicate call" from the same number, but a spouse calling about the same job from another phone has to be flagged by hand. In Ringba, the call details report includes Duplicate and Previously Connected columns, which help both sides check a duplicate claim against the same data.

What evidence decides a dispute?

For calls, the recording. eLocal says calls "are evaluated based on the recorded conversation that takes place, we do not take into account any new information discovered after the call," and that most credit requests are declined because the stated reason does not match what is heard on the recording. Axel PR says credit requests "are reviewed against the recording, not against memory."

Call-tracking platforms build the workflow around that evidence. Ringba's Call Disputes feature (announced August 17, 2018) lets a buyer submit a Call Void request from reporting with an "Adjustment Amount" and "Dispute Reason"; the administrator sees the call details and recording and can approve the full amount, approve a partial amount or deny, and a denied buyer can dispute again. For leads, boberdoo lets sellers decide per buyer whether refunds can be requested, set a "Refund Days Look Back" window, customize refund reasons, and even configure partial refunds (its example: 80% of the original value).

Recording itself has legal rules. Federal law (18 U.S.C. 2511(2)(d)) allows a recording when one party to the call consents, but some states require everyone's consent: Florida's statute (934.03(2)(d)) makes interception lawful "when all of the parties to the communication have given prior consent." Agree in writing who plays the recording notice. eLocal, for example, says a recording consent message is played before calls are transferred to the buyer. Have counsel confirm the setup for the states you buy in.

Do returns fix a consent problem?

No. A credit refunds the price of a lead; it does not change who placed the call or sent the text. If a lead arrives without a valid TrustedForm certificate or Jornaya LeadiD, or the consent language does not name your company, the safer move is to reject it before you dial, not to work it and ask for a credit later. Put "missing or invalid consent certificate" on the list of automatic rejection or return reasons, and check the certificate at delivery.

Returns can also hide a seller-side problem. boberdoo warns resellers about the "refund chain": when leads are resold, refunds have to flow back to the original vendor, and its Admin Returns Report exists to track which vendor owes which refund. If a vendor resells leads, ask how returns are reconciled with its own sources.

Return policy checklist: what to get in writing

• The full list of creditable reasons, with the evidence each one needs (recording, delivery record, ZIP, earlier call ID).
• The exclusions, especially no-answer calls, buyer hang-ups and "not interested" outcomes.
• The filing window in hours or days, when it starts (delivery, billing or appearance in the dashboard), and whether business days count.
• The duplicate rule: what is matched, how long the window is, whether it covers other campaigns or sources, and whether it is applied automatically.
• The billable threshold the returns are measured against, and whether intent can make a short call billable.
• Who reviews disputes, the response time, and whether a denied claim can be re-reviewed or escalated.
• How credits are paid: account balance or cash, partial credits, and whether credits expire.
• Who records calls, who plays the recording notice, and how long recordings and lead records are kept.
• How consent failures are handled: rejected at delivery, credited, or both.
• Reporting: a regular list of returns by reason, so you and the vendor can fix the source instead of arguing call by call.

How MGM ScaleCraft handles credits and disputes

We sell exclusive, TCPA-documented pay-per-call and pay-per-lead traffic to insurance, mortgage/HELOC, home-services and financial buyers. As our site and compliance overview state:

• A transparent credit and dispute SLA: a 72-hour credit window for verifiable wrong numbers, out-of-footprint transfers or sub-threshold call durations, documented through Ringba and Retreaver dispute logs.
• A weekly partner-facing quality report with a dispute path.
• Call recordings reviewed on a sampled basis and shared on request.
• A TrustedForm certificate or Jornaya LeadiD on every lead.

Review your credit terms in a partner briefing

If you are comparing vendors, rewriting a billable-call definition or seeing too many disputes, book a partner briefing and we will walk through credit reasons, windows, duplicate rules and evidence against your current program. For pricing context by vertical, see Cost Per Call in 2026. For the questions to ask before you sign, see our due diligence checklist.

FAQs