How to set call buffer times by vertical
A call buffer, also called a minimum call duration, is the number of seconds a call must last before the buyer pays for it. Our glossary at https://paypercallstack.com/glossary/call-buffer defines the term and includes a calculator for payout times the share of calls that pass the buffer. This post goes further: when the clock starts, how a poorly set buffer trains publishers to stall, and how to set a number from your own converted talk time instead of a platform default.
The figures below are industry estimates published by other firms, read on November 15, 2026. They are not our measurements, not a billing standard, and not a quote. Your contract controls. This is general information for operators, not legal advice.
When the clock starts
The same 90-second setting can bill very different conversations, depending on when the timer begins.
Axel PR's billable-call guidelines, effective October 21, 2026, say the clock starts when the call connects to your line, and that hold time or a long phone tree on your side counts against you. Their September 9, 2026 explainer makes the same point: the buffer typically starts at connect, so time on hold is inside the window. That is Axel PR's written program, not a rule every network uses.
Elevarus, in a May 13, 2026 post by Shane McIntyre, measures the disqualifier gate from call connect, not from agent connect. They state that every 15 seconds of pre-agent IVR pushes that gate 15 seconds later. If the timer starts at connect, a 30-second menu and a 90-second agent conversation are not the same as 90 seconds of talk time.
Call tracking platforms usually let you set a buffer per buyer or per campaign, and choose whether the timer starts at connect or after an IVR. Check that setting, and check whether hold time counts, before you compare two offers. See https://paypercallstack.com/glossary/ivr and https://paypercallstack.com/guides/how-to-choose-call-tracking-software.
The publisher incentive
Elevarus argues that a buffer is not only a billing filter. It is an incentive you send publishers.
They define the disqualifier gate as the first moment the agent confirms the one thing that cannot be fixed, such as a health-question block on a final expense call, or service area and homeowner status on HVAC. Set the buffer below that gate, they say, and you bill for calls that were already going to fail. Set it above the gate, and you pay publishers to slow-walk the script: extra hold music, questions the IVR already asked, and a pause just before the meter runs out. They also say calls that bill at exactly your buffer plus three to five seconds, with those patterns repeating from the same source, are a stall-padding signature, not a randomly slow agent.
That is Elevarus's framework, not a finding we audited. The practical point is still useful: do not inherit a 60- or 90-second platform default across every campaign, and do not set the buffer from average call duration, which mixes qualified, failed, and padded calls into one number.
Published ranges by vertical
These ranges disagree, especially on Medicare and insurance. That disagreement is the point. Treat them as a starting map, then set your own number from recordings.
| Vertical | Published estimates | Source and date |
|---|---|---|
| Emergency plumbing | 45 to 60 seconds; 60 to 90 seconds | Elevarus, May 13, 2026; VeloCalls, June 14, 2026 |
| Home services, general | 60 seconds; 60 to 90 seconds; 90 seconds | Axel PR program, Oct 21, 2026; GAT Media, Oct 2, 2026; VeloCalls, June 14, 2026 |
| HVAC | 90 to 150 seconds | Elevarus, May 13, 2026 |
| Scheduled plumbing | 90 seconds or more | Elevarus, May 13, 2026 |
| Pest control | 60 to 75 seconds | Elevarus, May 13, 2026 |
| Roofing, storm / retail | 75 to 120 seconds; 90 to 120 seconds | Elevarus, May 13, 2026 |
| Solar | 90 to 120 seconds | Elevarus, May 13, 2026 |
| Final expense | 50 to 60 seconds; 90 to 120 seconds | Elevarus, May 13, 2026; GAT Media, Oct 2, 2026 |
| Term life | 60 to 75 seconds | Elevarus, May 13, 2026 |
| ACA / health | 90 to 110 seconds; 90 to 120 seconds | Elevarus, May 13, 2026; GAT Media, Oct 2, 2026 |
| Medicare | 110 to 130 seconds, longer in AEP; 90 to 180 seconds; 180 to 240 seconds | Elevarus, May 13, 2026; GAT Media, Oct 2, 2026; VeloCalls, June 14, 2026 |
| Insurance, grouped | 90 seconds; 120 to 180 seconds | Axel PR program, Oct 21, 2026; VeloCalls, June 14, 2026 |
| Auto insurance | 60 to 120 seconds | GAT Media, Oct 2, 2026 |
| Legal and SSDI | 120 seconds; 120+ seconds; 180 to 240 seconds | Axel PR program (includes SSDI), Oct 21, 2026; GAT Media, Oct 2, 2026; VeloCalls legal intake, June 14, 2026 |
| Tax debt relief | 120 to 180 seconds | GAT Media, Oct 2, 2026 |
Industry estimates published by the cited firms as of the dates shown, read November 15, 2026. These are not our measurements, not payout quotes, and not a billing standard. Your contract controls.
How to set and validate your number
Two published methods, which can produce different results.
- Elevarus: Pull about 30 recent calls that closed and 30 that did not. Listen for the moment in the closed calls where the agent confirms the unfixable criterion. Check whether that timestamp falls before or after the lost calls dropped. Set the buffer just past that clean separation. Then pull a 30-day rejected-call report, bucket rejections by duration in five-second bins, and look for a spike between your buffer and your buffer plus 30 seconds. If rejections cluster there, they say the gate is inside the billable window. If rejections are spread evenly, they say the problem is traffic quality, not the buffer.
- VeloCalls, June 13, 2026, updated June 14, 2026: Pull the last 90 days of calls, filter to converted leads only, sort by talk time, and take the shortest call that actually converted. Set the threshold 15 to 20 seconds below that floor, so you do not exclude real converters. They also argue that a 30-second threshold is too low for most verticals.
Those two methods pull in opposite directions if your shortest converter sits near the gate. Document which method you used, test a change on one source or publisher first (Elevarus recommends two to three weeks, with payout held constant), and write the number into the publisher agreement instead of pointing at a network default.
After you pick a number, estimate what it does to revenue with the calculator at https://paypercallstack.com/glossary/call-buffer. Compare payout times the share of calls that pass the buffer, not the headline payout alone. That is your revenue per call. See https://paypercallstack.com/glossary/revenue-per-call.
Splits a single default misses
Elevarus warns against one buffer for mixed campaigns. Emergency plumbing, they say, often clears in 45 to 60 seconds because the gate is service area. Scheduled plumbing often needs 90 seconds or more because the gate includes scope and scheduling. HVAC with in-house dispatch can clear faster than HVAC that transfers to outsourced dispatch. Storm roofing and retail roofing have different claim-status and project-scope gates.
If you sell home services calls, start with https://paypercallstack.com/guides/home-services-pay-per-call. For insurance and benefits campaigns, see https://paypercallstack.com/guides/final-expense-pay-per-call, https://paypercallstack.com/guides/medicare-pay-per-call, and https://paypercallstack.com/guides/aca-health-insurance-pay-per-call. SSDI is grouped with legal at 120 seconds in Axel PR's October 21, 2026 program table; read https://paypercallstack.com/guides/ssdi-pay-per-call before you copy that grouping into a contract.
Intent, duplicates, and caps
Duration is not always the only rule. Axel PR's program, effective October 21, 2026, bills a short call if the caller asks for a quote, estimate, appointment, price, or callback before the buffer ends. Their September 9, 2026 explainer says many programs work that way, and that the reverse can also apply: a long call with no intent can still be disputed. That is program language, not a universal right. Read your agreement.
A buffer also sits next to duplicate-call windows and call caps. See https://paypercallstack.com/glossary/duplicate-call and https://paypercallstack.com/glossary/call-cap. Settle those terms at the same time you settle duration.
Primary sources
Elevarus, Shane McIntyre, Your Pay-Per-Call Buffer Isn't a Billing Setting, May 13, 2026: https://elevarus.com/pay-per-call-buffer-time-settings-by-vertical/. VeloCalls, How to Filter Junk and Duplicate Calls in Pay-Per-Call Campaigns, June 13, 2026, updated June 14, 2026: https://velocalls.com/blog/filter-junk-calls-pay-per-call-how-to. Axel PR Exclusive Calls, Billable Call Guidelines, effective October 21, 2026: https://axelpr.com/exclusive-calls/billable-call-guidelines. Axel PR, Billable Call Rules Explained, September 9, 2026: https://axelpr.com/insights/billable-call-rules-explained. GAT Media Group, Ghulam Abbas Tanveer, How Does Pay Per Call Work, October 2, 2026, typical US market ranges labeled October 2026: https://gatmediagroup.com/blog/how-does-pay-per-call-work/.
FAQ
Is there one standard buffer for insurance or home services?
No. Published estimates disagree. Axel PR's program uses 90 seconds for a wide insurance group and 60 seconds for home services. VeloCalls publishes 120 to 180 seconds for insurance and 90 seconds for general home services. Set yours from recordings and your contract, not from a single table.
When does the buffer clock start?
It depends on the platform and the contract. Axel PR's written rules start the clock when the call connects to your line, so hold time on your side counts. Elevarus measures the disqualifier gate from connect, and says IVR time pushes that gate later. Confirm whether your timer starts at connect or after the IVR.
Should emergency and scheduled plumbing use the same buffer?
Elevarus says no, because the gates are different: about 45 to 60 seconds for emergency service-area checks, and 90 seconds or more for scheduled scope and booking. A single campaign average can hide both problems.
How do I tell if publishers are stall-padding?
Elevarus looks for repeated patterns from the same source: extra hold music after connect, questions the IVR already captured, a pause just before the buffer, and bill durations clustered at the buffer plus three to five seconds. A slow agent, they say, is more randomly distributed.
Should I set the buffer from average call duration?
Elevarus advises against it, because the average mixes qualified, disqualified, and padded calls. They set the buffer just past the disqualifier gate. VeloCalls instead starts from the shortest converted call and sets the floor a little below that. Neither method uses a raw average.