Most pay-per-meeting disputes start the same way. A rep books a meeting, the client reviews it, and the answer comes back “not qualified.” Then the argument begins.

Having reviewed a lot of these, I can say the disputes rarely come from bad calls. The rep usually had a real conversation with a real prospect. The fight happens because the two sides never agreed, in writing, on two things: what counts as a qualified meeting, and what proof has to exist before a payout is released.

Take a recent case. The client’s rep said the call had no issues. When we reviewed the recording, the prospect had described two manual processes that the client’s product was built to replace, so the pain was there. But a second problem surfaced that nobody had flagged. The client’s rep had been targeting a software family the product does not integrate with. The client’s criteria said “decision-maker in the target industry” and said nothing about the platform. So both sides could read the same call and reach opposite conclusions. The dispute stalled for weeks, and the meeting was never paid or rejected cleanly.

Neither side was acting in bad faith. The gap was in the paperwork. Both problems, the missing platform criterion and the lack of a clear proof standard, should have been settled before the first dial.

Here is what I now put in front of every client before a campaign goes live. It fits on one page, and both sides sign it.

Ideal buyer. Job title and industry, stated together. A correct title in the wrong industry is not a match, and neither is the reverse. Agree on this explicitly.

Hard disqualifiers. Anything that makes a meeting worthless to the client regardless of how good the call was. Integration requirements, company size floors, geography, and existing contracts with a competitor are common ones. If a prospect fails a disqualifier, the meeting does not count. Write that down.

Definition of a qualified meeting. For example: a decision-maker or a named influencer attends, states a problem the offer addresses, and agrees to a next step with a date. Vague language like “good conversation” will be argued about forever.

Required proof. Decide the exact evidence up front: a recording or transcript with a timestamp where the qualifying point is made, attendee titles, the CRM note, and the booking confirmation. If something is not in the proof pack, it does not count. Reps should know this before they dial, not after a dispute.

Review window and tie-breaks. Set a deadline for the client to dispute a meeting, usually a few business days, and name who makes the final call when the two sides disagree. Without this, every disagreement becomes an open-ended negotiation.

The other habit that prevents disputes is checking early. When we review a meeting within a day, while the call is fresh and the transcript is easy to pull, the discussion stays short. When we wait three weeks, everyone is working from memory and the arguments get expensive.

The payout structure matters less than most people think. A higher rate per meeting does not fix a vague definition. A clear one-page definition, a proof standard, and a review deadline will prevent most of the fights I see, and they cost nothing to write.

If you run or buy pay-per-meeting programs, write the definition before the first call, not after the first dispute.