How to Write Call Quality Criteria Buyers and Publishers Accept

Every pay-per-call campaign lives or dies on a single, fragile agreement: what counts as a good call. When advertisers and publishers define that standard differently, the result is predictable. Publishers send traffic, calls get rejected, invoices get disputed, and trust erodes until the campaign quietly dies. The fix is not more arguing. It is a written set of call quality criteria that both sides understand, can verify, and are willing to live with.

This article breaks down how to write call quality criteria buyers and publishers both accept. You will learn how to translate business rules into measurable call standards, decide what can be checked automatically versus manually, build transparency into the process, adjust criteria without breaking live campaigns, and use dispute data to catch misalignment early. The goal is not perfection on day one. It is a shared, testable definition of quality that keeps calls flowing and revenue growing for both sides.

Start With Business Rules, Not Guesswork

Most call quality disputes do not start with bad intentions. They start with vague language. An advertiser says they want "qualified leads," and a publisher interprets that as anyone who stays on the line for 60 seconds. Three weeks later, the advertiser is rejecting 40 percent of calls and the publisher is threatening to walk. The root cause is that no one translated the advertiser's actual business rules into call-level criteria.

Begin by asking the advertiser a simple question: what makes a call worth paying for? The answer usually falls into a few buckets. Service area matters: a plumber in Dallas does not want calls from Houston. Job size matters: a roofing company may not want tire-kickers asking about a single missing shingle. Timing matters: after-hours calls may be fine for emergency services but useless for a dental office. Intent matters: a caller asking about billing is not a sales lead. And eligibility matters: in regulated verticals like insurance, the caller must meet basic qualification rules before the call has value.

Write these rules down in plain language first, before you touch a tracking platform. A useful exercise is to complete this sentence for each rule: "A call is not payable if the caller ___." That forces specificity. "A call is not payable if the caller is outside our service ZIP codes" is testable. "A call is not payable if the caller is unqualified" is not. For a deeper look at how this qualification logic drives campaign performance, see our guide on how pay per call services drive quality leads.

Turn Rules Into Criteria That Can Be Verified

Once the business rules are clear, the next step is deciding how each one will be verified. This is where many criteria documents fall apart. They list rules that sound reasonable but cannot be checked consistently, so rejections become subjective and disputes become personal. Every criterion you write should have a named verification method attached to it.

Verification generally falls into three categories. The first is automatic verification, where the platform or telephony data can confirm the criterion without human review. Service area can be checked against the caller's area code or geographic data. Call duration can be measured precisely. Repeat caller status can be flagged automatically. Time of day and day of week are always available. The second category is interactive verification, where an IVR prompt or qualifying question captures the answer before the call connects. Job size, service type, and basic eligibility can often be handled this way. The third category is manual review, where a human listens to a recording or reads a disposition and makes a judgment. This is the most expensive and most disputed method, so use it sparingly.

A practical framework for assigning verification methods looks like this:

• Automatic: geography, call duration, time of call, repeat caller status, duplicate detection.
• Interactive (IVR or qualifying questions): service type, job size range, eligibility flags, language preference.
• Manual review: nuanced intent judgments, complaint calls, edge cases that automated rules cannot capture.

For each criterion, write down the verification method next to it. If you cannot name a method, the criterion is not ready. This single discipline eliminates most of the ambiguity that fuels disputes. It also makes publisher applications far easier to evaluate, because publishers can see exactly what they are committing to before they opt in.

Make Criteria Visible Before Publishers Apply

Transparency is not a courtesy. It is a performance lever. Publishers who understand the acceptance criteria up front will self-select into campaigns they can actually deliver on, and they will route traffic accordingly. Publishers who discover the criteria only after a batch of rejections will feel tricked, even if the advertiser acted in good faith. The difference between those two outcomes is whether the criteria were visible at the application stage.

When you write call quality criteria, treat them as part of the campaign offer, not as an internal document. Publishers should see the service area, the qualifying questions, the minimum call duration, the payout rules, and the rejection reasons in the same place they see the payout rate. This is especially important in regulated verticals. A publisher sending calls into a Medicare campaign, for example, needs to know eligibility rules before generating a single call. Marketplaces that connect agents with consumers, such as MedicareLeads, illustrate why clear qualification standards matter: the value of the lead depends entirely on whether the caller meets the plan's eligibility and intent requirements.

Visibility also improves the quality of publisher applications. When criteria are explicit, publishers who cannot meet them simply do not apply. That reduces wasted onboarding time on both sides and raises the average quality of the publishers who do opt in. The practical rule is simple: if a criterion will be used to reject a call, it must be visible to the publisher before the campaign goes live. Anything less creates a structural dispute.

Build a Process for Adjusting Criteria Mid-Campaign

Criteria will change. Advertisers learn that a certain ZIP code produces poor close rates, or that calls under 90 seconds rarely convert, or that a new qualifying question filters out too many good leads. The question is not whether criteria will evolve, but whether the process for changing them is orderly or chaotic. Chaotic changes are the most common cause of publisher revolt, because retroactive rejections feel like moving the goalposts.

Establish a written change process with clear rules. A workable version has four steps. First, any proposed change is documented with the reason and the expected effect on call volume and acceptance rate. Second, the change is communicated to active publishers with a defined notice period, typically one to two weeks for material changes. Third, the change applies only to calls generated after the effective date, never retroactively. Fourth, the first period under the new criteria is monitored closely so both sides can see whether the change had the intended effect. For minor administrative clarifications, a shorter notice period is fine, but the no-retroactive-rejection rule should never be broken.

There is one more discipline that separates mature programs from reactive ones: test before you roll out. If an advertiser wants to add a new qualifying question, run it on a subset of traffic first and compare acceptance rates and close rates against the control group. If the new question improves quality without crushing volume, roll it out. If it kills volume, you have learned that cheaply. This test-and-learn approach keeps criteria aligned with real outcomes instead of assumptions.

Track Dispute and Reversal Rates as Early Warning Signals

The healthiest signal of criteria misalignment is not a complaint. It is a pattern in the dispute data. When publishers dispute rejections frequently, or when reversal rates climb, the criteria are usually either unclear, unverifiable, or misaligned with what the advertiser actually values. Treat these metrics as a dashboard, not as a legal file.

Several numbers are worth watching monthly. The rejection rate by criterion tells you which rules are doing the most work and which may be too aggressive. The dispute rate tells you how often publishers disagree with rejections. The reversal rate, meaning disputes that were upheld, tells you how often the original rejection was wrong or poorly documented. A high reversal rate is a direct signal that either the criterion is ambiguous or the verification method is unreliable. Repeat-caller and duplicate rates reveal traffic quality issues that may be better solved with publisher coaching than with rejection.

The most useful benchmark is trend, not absolute level. A rejection rate that jumps from 10 percent to 25 percent after a criteria change is a signal to investigate. A dispute rate that stays flat while volume doubles is a sign the criteria are holding up under pressure. Review these numbers with publishers openly, not as an accusation but as a shared diagnostic. When both sides look at the same data, the conversation shifts from blame to calibration.

Write the Criteria Document So It Survives Contact With Reality

A criteria document that lives only in a slide deck will not survive the first month of a live campaign. The version that works is short, specific, and operational. It should state each criterion, the verification method, the rejection reason code, and the notice process for changes. It should also include worked examples. A sample call that passes and a sample call that fails, described in plain language, do more to align expectations than any amount of policy language.

Keep the document in a place both sides can access, and version it. When criteria change, the version number and effective date change with them. This sounds bureaucratic, but it prevents the most corrosive dispute of all: the argument over what the rules were at the time the call happened. A versioned, timestamped criteria document settles that argument in seconds.

Finally, assign ownership. Someone on the advertiser side should be accountable for criteria design and someone on the publisher side should be accountable for communicating changes and collecting feedback. Programs without clear owners drift toward either over-rejection or unchecked volume, and both outcomes destroy margin. The platform itself should support this discipline. Tools like real-time call filtering, quality-based pricing, and detailed reporting make it far easier to write criteria that both sides can see, test, and trust, which is exactly the foundation a durable pay-per-call program is built on.

Writing call quality criteria that buyers and publishers both accept is ultimately an exercise in clarity. Translate business rules into testable standards, attach a verification method to every rule, make the criteria visible before publishers apply, change them through a documented process with no retroactive rejections, and watch dispute and reversal rates for early warning signs. Do that, and the argument over what counts as a good call stops being a monthly crisis and becomes a shared operating standard that both sides can build on.