Last month a plumbing publisher sent me a screenshot of their disputes dashboard. Thirty-four calls rejected in one week. Reason: "Did not meet 90-second minimum." Every one of those calls showed 92-98 seconds in their tracking platform.
The problem wasn't the calls. It was where the clock started.
Their IVR ran 18 seconds. Transfer hold averaged 12 seconds. By the time the caller heard a human voice, they were already 30 seconds into what their platform called the "call." The buyer counted from agent pickup. That 94-second call? 64 seconds of actual conversation. Rejected.
I've been burned by this exact problem — twice, actually, because apparently I don't learn the first time. This is the billable duration gap, and it bleeds publishers dry while everyone points fingers. You're generating legitimate calls. Callers are talking to agents. Deals are closing. But your invoice gets shredded because of 8 seconds nobody thought to measure.
Here's what I've learned after arguing with far too many buyer billing departments (and losing more than I'd like to admit). If you're running pay-per-call at any scale, this gap is probably costing you more than you realize.
Where Duration Actually Gets Measured
The first problem is definitional. "Call duration" means different things to different parties.
Your tracking platform typically starts the clock when the call enters the IVR or when your tracking number answers. That includes greeting prompts, menu navigation, hold time, and transfer attempts.
The buyer's system usually starts when their agent picks up. Some buyers start when the call enters their queue. A few count from when their system answers, but most don't.
The contract might specify something different from both. I've seen contracts that define "billable duration" as time from agent greeting to call termination, excluding hold and transfer. Others use "connected duration" which includes hold. The language matters.
You can have a 120-second call by your measurement and a 65-second call by theirs. Neither party is lying. The definitions just don't match.
Step one: read your contract. Actually read it. The whole thing. I know — nobody does this. Find the clause that defines minimum duration and what counts toward it. If it says "agent connected time" you're measuring the wrong thing. If it says "IVR entry to disconnect" you might be fine. Most problems start with assumptions. Our pay-per-call contract negotiation guide covers the key clauses to watch for.
I spent a frustrating week arguing with a buyer about duration discrepancies. Back and forth. "My data says X." "Our data says Y." Getting nowhere. Then someone on their team just... sent me the actual contract language. They were right. I'd been measuring wrong for three months. Three months! Expensive lesson in reading paperwork — and in not assuming I know what I signed.
The Four Places You Lose Seconds
Once you understand what counts, audit where time disappears before that measurement starts.
1. IVR Prompt Length
Your greeting and menu prompts run before the caller reaches anyone. Every second of "Thank you for calling. For service, press 1. For billing, press 2..." is a second the buyer doesn't count.
Industry data (and our own observations) suggests typical IVR greetings run 12-20 seconds. Add two menu levels and you're at 30-45 seconds before agent connection. On a 90-second minimum threshold, you've burned half your window. Half. Gone before anyone says hello.
The IVR abandonment study we ran earlier this year showed abandonment rates climbing 6 percentage points per menu level. But the duration problem is separate — even callers who don't abandon are spending precious seconds navigating prompts. Seconds that don't count toward your billable threshold.
Honestly, most IVRs I audit are bloated. People add menu options because it feels professional. "We have a sophisticated phone tree." No. You have a duration leak.
Audit step: Time your IVR. Call your own tracking number. Start a stopwatch when you hear the first word of the greeting. Stop when you'd normally hear "Please hold while we connect you" or the first ring to an agent. That number is your IVR overhead.
If it's over 15 seconds, you have optimization work to do.
2. Hold Queue Before Agent
After the IVR, callers often hit a hold queue. Music plays. Estimated wait times are announced. "Your call is important to us" repeats.
This time usually doesn't count toward billable duration in buyer contracts. The caller is waiting, not talking to anyone.
Average hold times in pay-per-call operations run 20-45 seconds during normal hours. During peak periods (think HVAC in August, plumbing emergencies Friday night), holds can stretch to 90+ seconds. Every second of hold is a second the caller isn't in billable conversation.
The math gets ugly. 15-second IVR plus 30-second hold equals 45 seconds before anyone picks up. On a 90-second minimum, your caller has 45 seconds of conversation time to meet threshold. Forty-five seconds. That's tight. Too tight for complex qualification. And good luck qualifying a PI case in under a minute.
3. Transfer Lag and Ring Timeout
Here's one most publishers miss entirely: the transfer itself eats time.
When your system connects a call to a buyer's number, several things happen:
- Your platform initiates the outbound leg
- The buyer's system receives the call
- Their system routes to an available agent
- The agent's phone rings
- The agent answers
Each step takes time. Typical transfer lag from "caller in queue" to "agent says hello" runs 8-15 seconds. If the buyer's ring timeout is set short (some use 15-20 seconds before abandoning), agents who don't answer instantly can cause the call to fail entirely.
I've seen campaigns where 12% of transferred calls were rejected as "too short" because the transfer took 11 seconds and the agent conversation only ran 82 seconds. Total call time: 93 seconds by the publisher's measure. Agent time: 82 seconds. Threshold: 90. Rejected. Maddening? Yes. Fixable? Also yes.
Audit step: Pull recordings of rejected calls. Listen for the actual moment the agent speaks. Time from that greeting to call end. That's your real billable duration — and it's probably shorter than your dashboard shows. (Fair warning: listening to your own rejected calls is not fun. But it's where the money is.)
4. Contract Threshold Mismatch
Sometimes the problem isn't timing at all. It's a mismatch between what you're sending and what the buyer actually wants.
Buyer A might take calls down to 60 seconds because they're running a quick-qualification funnel. Buyer B might need 120 seconds because they're doing full intake. If you're routing calls evenly and only tracking aggregate duration, you're sending short-qualification traffic to long-threshold buyers.
This shows up as rejections even when your overall duration numbers look fine. The specific calls hitting Buyer B are the wrong fit.
How to Actually Fix This
Now that you know where time leaks, here's how to close the gaps.
Cut Your IVR. Seriously Cut It.
I don't mean trim a few words. I mean rebuild from scratch with a 10-second ceiling. This is controversial — I've had clients push back hard. "But we need the menu options!" No. You need billable calls.
Current state (typical): "Thank you for calling [Company Name], your trusted source for [industry] since 1987. Your call may be monitored for quality assurance. For sales, press 1. For support, press 2. For billing, press 3. For all other inquiries, please stay on the line."
That's 18-22 seconds. Every call.
Fixed state: "[Company Name]. For service, press 1. For billing, press 2."
That's 4 seconds. You just recovered 15+ seconds of billable time on every call.
The longer version feels professional. The shorter version makes money. Buyers don't care about your founding year — nobody has ever said "I chose this plumber because their IVR mentioned they started in 1987." Move the routing logic to the backend:
- Use area code to detect geography instead of asking "Press 1 for Phoenix, press 2 for Tucson"
- Use time-of-day rules instead of asking "For emergency service, press 1"
- Use ANI lookup for returning callers instead of asking for account numbers
Every button press you eliminate is another 3-5 seconds of billing time recovered.
The VeloCalls visual IVR builder lets you see timing on each node before you publish changes. You can model the impact of collapsing menus without waiting for live data.
Buffer Your Duration Targets
If a buyer requires 90 seconds, don't target 90 seconds. Target 105-110.
This gives you margin for:
- Transfer lag variability (8-15 seconds depending on buyer load)
- Agent pickup speed (some agents answer faster than others)
- Measurement discrepancies between platforms
The buffer approach means fewer disputes, fewer rejections, and less time arguing over calls that were 88 seconds versus 90. Nobody wants to fight about 2 seconds. Build in margin so you don't have to.
Implementation: In your routing logic, weight buyers with lower thresholds more heavily when caller intent suggests shorter conversations. Price-shoppers who need a quick quote go to 60-second buyers. Callers with complex problems route to buyers who expect longer conversations.
Consider Warm Transfers
Cold transfers are faster but more disruptive — the caller repeats their problem, burning time. Warm transfers take 10-15 seconds upfront but the agent conversation starts faster because they have context. A 90-second warm-transferred call often accomplishes what takes 120 seconds cold.
The caveat: some buyers prefer cold transfers and have intake scripts that assume zero context. Ask before changing your method. I made this mistake once — switched a buyer to warm transfers without asking, thinking I was being helpful. They were not impressed. For setup specifics, see the warm transfer vs cold transfer guide.
Negotiate Duration Definitions
If your contract says "connected time" and you're hitting 85-88 seconds consistently, consider renegotiation.
What to propose:
- Lower threshold (85 instead of 90)
- Definition change (from agent pickup to IVR entry)
- Grace window (calls within 10% of threshold reviewed individually, not auto-rejected)
Some buyers won't budge. Fine — route elsewhere. Other buyers will negotiate, especially if you're sending volume and your qualification rate is strong. Worth asking. The worst they say is no.
Monitor Rejection Patterns in Real Time
Don't wait for invoice disputes. Track rejections as they happen.
Build a report that flags:
- Any call rejected within 10 seconds of threshold
- Repeat rejections from specific buyer accounts
- Rejection rate spikes by time of day or call source
When you see 15 rejections at 87-89 seconds from Buyer X in a single afternoon, something changed. Maybe their agent staffing dropped. Maybe they shortened their timeout. Maybe their threshold was always different than you thought and nobody noticed until now.
Catch patterns early. Fix before they compound into invoice disputes and awkward phone calls with account managers who used to like you.
JustAnalytics can feed rejection events into your attribution model if you're correlating call outcomes with traffic sources. A publisher might look good on volume but terrible on billable calls once you factor in duration rejects. I've seen sources with 40% rejection rates that looked profitable until someone ran the math.
Vertical-Specific Duration Thresholds
Different verticals have different baseline expectations.
HVAC and plumbing: 90-second minimums are standard. Service-need calls naturally run 2-3 minutes when callers describe the problem.
Legal intake (PI, mass tort): 120 seconds is common because qualification involves screening questions. Some buyers push to 180 seconds for complex case types.
Medicare Advantage: AEP campaigns often want 150-180 seconds for eligibility verification. OEP is shorter.
Home warranty / appliance: 60-90 seconds. Simpler qualification, so thresholds run lower.
The home services pay-per-call playbook covers vertical economics in more detail. If you're running click fraud detection via ClickzProtect for your paid sources, you can correlate traffic quality with downstream duration issues.
Building This Into Your Workflow
Duration management isn't a one-time fix. It's ongoing. Annoying, but ongoing.
Weekly: Review rejection rate by buyer. Any buyer above 10% rejection rate needs attention. See our call quality metrics dashboard guide for what to track.
Monthly: Audit IVR timing. Small changes accumulate. Someone adds a holiday greeting in December and forgets to remove it in February — happens more than you'd think. The IVR testing checklist walks through the full audit process.
Per buyer: Document threshold, start point definition, and acceptable variance. Put it in a spreadsheet. Update it when contracts renew. Your future self will thank you.
I've watched publishers lose $15K/month to duration rejections they thought were "small variances." Eight seconds multiplied by 500 calls multiplied by $30 payout is real money. Money that could have been yours.
Fix the gap. Measure what buyers measure. Build in buffers. Read your contracts before they read you.
Frequently Asked Questions
Why do buyers reject calls that seem long enough?
Duration measurement often starts at different points. Your platform might count from IVR entry, but the buyer's contract specifies time after agent connection. A call that shows 95 seconds on your dashboard might only register as 58 seconds of agent time once you subtract IVR prompts, hold queue, and transfer lag. Pull recordings and time the actual agent conversation — that's the number that matters for billing.
What is the typical minimum call duration for pay-per-call buyers?
Most buyers set minimums between 90 and 120 seconds of connected agent time. HVAC and plumbing typically run 90 seconds. Legal intake often requires 120 seconds because qualification takes longer. Medicare can push to 180 seconds during AEP when buyers want full eligibility verification. Always confirm the specific threshold in your buyer contract — assumptions here cost money.
How do I shorten my IVR without losing routing intelligence?
Move logic to the backend instead of asking callers. Use area code detection for geography, time-of-day rules for department routing, and caller history for returning customers. Every menu you collapse saves 8-15 seconds of pre-agent time. The goal is one button press maximum before the caller reaches a human — anything more eats into your billable window.
Should I negotiate longer transfer timeouts with buyers?
Yes, but frame it correctly. Buyers care about qualified conversations, not raw duration. Propose extending the ring timeout from 15 to 25 seconds with data showing your calls convert at higher rates when they actually connect. A buyer who drops 3-second faster gets fewer conversions — that's the argument that works. Bring call recordings showing qualified callers abandoning during short timeouts.
Try VeloCalls for Your Vertical
Pay-per-call platform built for HVAC, plumbing, roofing, PI lawyers, Medicare brokers, and insurance. Smart routing, real-time bidding, visual IVR builder, AI conversation intelligence — transcription, sentiment, summarization, and AMD. Per-minute pricing: Managed starts at 4¢/min, BYOC at 2¢/min, both drop as you scale through lifetime usage tiers.