Pay-Per-Call Dispute and Credit Policy: What It Should Cover and How to File

A fair pay-per-call credit policy tells you which calls you can dispute, how long you have to file, what proof is required, and how quickly you'll be paid back. Before you sign with any vendor, get those four answers in writing. After that, filing a dispute is mostly a matter of organized evidence.

This explainer sits inside our pay-per-call quality and compliance guide. It's written to work with any vendor, so use it as a yardstick for the terms you're offered. On RankLocal's side, one fact is public: RankLocal bills only qualifying calls over 60 seconds. This page doesn't describe its credit terms, so ask for the current terms when you apply.

Billing rules versus credit rules

These two get confused, so separate them.

• Billing rules decide whether a call is billable in the first place. A minimum duration is the common one. A call under the threshold never appears on your invoice. See what a billable call is.
• Credit rules cover calls that were billed but shouldn't have been, or that fall under an agreed exception. You ask for money back through a dispute.

Strong billing rules mean fewer disputes. A vendor who bills only calls over a clear minimum, and who filters repeats, hands you less to argue about. Weak billing rules put more weight on the credit policy.

What a fair credit policy should cover

Use this as a checklist when you read a contract.

Don't expect every policy to be generous. Some vendors are strict about what counts. That's their right, as long as the rules are plain and you agree to them in advance.

Reasons that usually qualify, and reasons that usually don't

Policies differ, but the same categories tend to show up.

Often creditable:

• Calls that were billed but fall below the billing minimum.
• Duplicate billing of the same caller within the repeat window, which is the job of duplicate caller filtering.
• Calls for a service you don't offer, when your service list is on file with the vendor.
• Calls from outside your agreed territory.
• Spam, robocalls, sales calls, or other non-homeowner traffic.
• Technical failures such as a connection that dropped before anyone spoke.

Often not creditable:

• A valid call that didn't book.
• A caller who wanted a price and went elsewhere.
• A call you missed or answered poorly.
• A job that was too small or too large for you, if you didn't set limits upfront.

The last group is the reason to write down your preferences before you start. If you only want roof replacements, say so in the agreement. A vendor can't be held to a rule it never agreed to.

How to file a dispute, step by step

This process works with any vendor. Adjust for the portal or email address they use.

1. Read the policy first. Note the window and the evidence required. Mark the deadline on your calendar.
2. Pull the call record. Get the call ID, caller number, date and time, duration, and the number that was dialed.
3. Get the evidence. Save the recording if you have access to one. If you took notes, copy them in. If recording laws in your state apply to what you captured, check with an attorney.
4. State the reason in the vendor's words. Use their category, such as "outside service area" or "duplicate caller." That helps their team match your claim to a rule.
5. Submit in writing. Use the portal or email so you have a record. One message per batch is fine if the format allows.
6. Keep a log. Track the date you filed, the reference number, the response date, and the outcome.
7. Follow up on the promised timeline. If nothing comes back, reply on the same thread.
8. Escalate if needed. Use the appeal path in your contract. Stay factual and cite the clause.

A sample dispute message

"Please review the following calls from the March invoice for credit. Call ID 10482, 3/4 at 2:15 pm, caller outside our agreed service area per our territory list (caller gave a zip code in another county). Recording attached. Call ID 10497, 3/5 at 9:40 am, same caller number as 10482, billed twice within the repeat window. Please confirm receipt and expected response date."

The IDs and dates in that example are made up. The shape is what matters: specific, short, tied to a rule.

Evidence that makes a dispute stick

Weak disputes say "these were bad calls." Strong ones show a pattern against a clause.

• A spreadsheet with the flagged calls, a reason for each, and the cost.
• Recordings that show what happened on the call.
• Timestamps that line up with the vendor's own log.
• Your service area and service list on file, so the vendor can see the mismatch.

The how-to on spotting fake pay-per-call leads covers the checks that produce this evidence. If you aren't recording calls yourself, call tracking for contractors is the usual way to start.

Warning signs in a policy

Be careful when you see:

• No written policy at all.
• A filing window so short you couldn't finish a weekly review.
• "All sales are final" language with no exceptions.
• Credits paid only as future leads at the vendor's pricing.
• No access to call logs or recordings, which makes your claim hard to prove.
• A rule that disputes reset your contract or void your terms.

None of these automatically means a vendor is dishonest. They do tell you how much risk you're carrying. The 15-point vendor audit puts credit terms in context with everything else, and questions to ask a lead generation company gives you wording for the sales call.

How credit policy compares across lead models

The same idea shows up in every lead source, with different details.

• On shared lead marketplaces, contractors commonly report that they must dispute leads within a set time and that the marketplace decides. Housecall Pro's overview of Angi notes leads can be shared among contractors, which is a reason duplicate and competition issues come up.
• On Google Local Services Ads, a dispute process exists and leads are charged per lead. Check Google's current help pages for the rules.
• On pay-per-call, the call itself is the unit, so duration, location and repeat rules do most of the work.

For more on how exclusive and shared leads differ, see exclusive vs shared leads.

What disputes can't fix

A dispute recovers money on a call that shouldn't have counted. It doesn't fix a source that sends mediocre but technically valid calls. If a vendor passes every dispute test and your cost per job is still too high, the answer is a different source, a better intake process, or both. Track cost per job so you can tell the difference.

If you want a model where the billing rule does some of the quality work upfront, RankLocal sends exclusive inbound homeowner calls and bills only qualifying calls over 60 seconds. You can see how it works on the pay-per-call page.

Frequently asked questions

What should a pay-per-call credit policy cover?

It should say which call types qualify for a credit, how long you have to file, what evidence you need, how fast the vendor responds, and how the credit is paid. If any of those are missing, ask before you sign.

How long do I have to dispute a call?

It depends on the vendor and your contract. Many policies use a short window, so check yours and file as soon as you spot a problem.

Can I dispute a call just because it didn't turn into a job?

Usually not. Most policies credit calls that fail a defined standard, such as wrong service, outside the area, or too short, and not calls that were valid but didn't close.

Does RankLocal credit bad calls?

RankLocal bills only qualifying calls over 60 seconds. For anything beyond that, ask for the current terms when you apply.