Picture a mass tort campaign — Camp Lejeune, high payout, competitive keyword bids — with an IVR that asks four questions before anyone answers: injury type, exposure location, diagnosis timeline, and whether the caller has already filed. Textbook qualification, and every one of those prompts is another place for a caller to hang up.
The questions come fast once callers start dropping. How deep is too deep? Should I use voice prompts or keypad? Do I really need to ask all that upfront? IVR design looks simple until you're watching callers drop at menu two and wondering if maybe you overthought the whole thing.
This FAQ covers the questions lead buyers commonly ask before building (or rebuilding) an IVR menu. No theory. Just the answers that affect whether callers convert or hang up.
What You Need to Know First
IVR design for pay-per-call is different from corporate phone systems. You're not trying to deflect callers to save agent labor. You're trying to qualify callers fast and route them to buyers who will pay. Every second matters. Every extra button press costs money.
The core tension: buyers want qualified calls (so they don't waste time on junk), but aggressive IVR qualification kills volume. The operators who win find the minimum viable qualification that buyers will accept — and nothing more.
If you need the metrics vocabulary used to judge an IVR (answer rate, RPC and the rest), the call analytics metrics glossary defines it.
Menu Depth and Structure
How many IVR menu levels should I use?
One. Two maximum for high-value verticals like mass tort or Medicare where qualification directly affects payout.
Each level is another prompt to sit through and another chance to hang up, and the losses stack. Every button press costs you callers who would have converted. Some of those callers are your best leads — the busy homeowner with a broken AC who doesn't have patience for four qualification questions.
Move routing complexity to the backend. Caller ID area code, time of day, buyer capacity, caller history — all of this can inform routing without asking the caller. Keep the caller-facing menu minimal.
What if my buyers require multiple qualification data points?
Ask yourself: does the buyer need this before the call starts, or can the agent capture it in the first 30 seconds?
Example for HVAC pay-per-call:
| Requirement | IVR capture | Agent capture |
|---|---|---|
| Service type (HVAC vs plumbing) | Yes — affects routing | No |
| Homeowner vs renter | No | Yes — first question |
| System age | No | Yes — discovery question |
| Emergency vs scheduled | Maybe — affects payout | Maybe |
Homeowner status is a buyer requirement that doesn't change routing. The agent asks "Do you own or rent?" in the first sentence. Takes 5 seconds. Adding an IVR menu for it costs you callers.
If a buyer insists on pre-call data that doesn't affect routing, push back. Show them your own abandonment numbers by menu level. Most buyers would rather get more calls with agent-captured qualification than fewer calls with IVR-captured qualification. The ones who won't budge? You might be selling to the wrong buyer.
Should I offer a "press 0 for operator" option?
Yes. Callers who press 0 are telling you your menu doesn't match their need. That's valuable signal.
Route 0-pressers to your overflow queue or a discovery agent. Track why they're pressing 0 — if it's the same reason repeatedly, your menu has a gap. Maybe you're running HVAC and plumbing but callers keep asking about electrical. Add electrical or stop advertising to electrical searchers.
Hiding the 0 option doesn't make callers more patient. It makes them hang up. Better to route an unqualified call to a discovery agent than lose the caller entirely. The discovery agent can qualify in 30 seconds and either route appropriately or politely end the call.
Prompt Wording and Length
How long should my IVR greeting be?
Under 8 seconds from pickup to first option.
Every second of greeting is a second a caller can hang up. Cut the company history, award mentions, and verbose compliance disclaimers. Get to the choice fast.
Good format:
Thanks for calling [Company]. For [service] press 1, [other service] press 2, or stay on the line.
Seven seconds. Done.
If you include a recording disclosure ("this call may be recorded"), keep it to one short sentence up front and move on. Recording-consent rules vary by state, so have counsel confirm the wording for the states you take calls from.
(Pro tip: text-to-speech voices in 2026 sound good enough. Don't let waiting on a studio recording session hold this up for two weeks. Generate the audio today, deploy it, iterate if needed.)
How do I word options to avoid confusion?
Lead with the action, not the department.
Bad: "For our residential services division, press 1. For commercial accounts, press 2."
Good: "For home repair, press 1. For business accounts, press 2."
Callers think in terms of what they want, not your org chart. "Home repair" is clearer than "residential services division" — and shorter.
For service-type routing:
Bad: "For HVAC-related inquiries, press 1."
Good: "For heating and cooling, press 1."
"HVAC" is industry jargon. Plenty of callers don't know the acronym. "Heating and cooling" is closer to what they typed into Google.
Should I mention pricing or promotions in the IVR?
No. Every second of IVR greeting is abandonment risk. Save the pitch for the agent.
Exception: if you're running a time-limited promotion and it's genuinely the reason most callers are calling (like Medicare AEP enrollment deadlines), a 3-second mention can work. But don't read a paragraph about your 24-month financing options while callers wait to talk to someone.
DTMF vs Speech Recognition (NLU)
Should I use DTMF keypad input or speech recognition?
DTMF for routing decisions. Speech recognition for optional convenience.
DTMF (the touch-tone beeps) is highly reliable across phone types and environments — landlines, cell phones, VoIP, speakerphone, driving in traffic. It's 60-year-old technology and it works.
Speech recognition is far less forgiving in real deployments. Accents degrade it. Background noise degrades it. Mumbling degrades it. Speakerphone is a disaster. Every recognition error means a caller gets misrouted or asked to repeat themselves.
A misrouted call costs more than the seconds saved by voice input. Use speech for low-stakes confirmations if you want ("please say yes or no to confirm"), but route with keypad.
What about AI-powered conversational IVR?
Not ready for most verticals. Not yet. (And yes, I know that's an unpopular opinion in 2026.)
The promise: callers say what they need in natural language, and the AI routes appropriately. The reality: edge cases break it constantly. "I need someone to fix my AC" works. "Yeah so my unit, the one outside, it's making this noise like grrrr" might not.
Conversational IVR works for simple intents in controlled environments. It's not there yet for pay-per-call where routing errors directly cost money. It's improving fast, but for a campaign you care about, keypad routing is still the safer choice. See our AI vs human call qualification comparison for the current math.
Qualification Gating
Can I qualify callers without forcing multiple menu levels?
Yes. Front-load your highest-signal qualification question at menu one — service type, intent, or emergency vs scheduled — then use backend logic for everything else.
Caller ID area code can often stand in for a zip prompt. Time of day handles hours-based routing automatically. Your call logs can flag repeat callers by caller ID without asking.
One menu with smart backend routing beats three menus with dumb routing every time. You get the qualification signal without the abandonment tax.
What's the best single qualification question to ask?
The question that changes routing.
For HVAC/plumbing/electrical multi-service:
"For heating and cooling press 1, plumbing press 2, electrical press 3."
This routes to the correct buyer pool. Everything else can wait.
For legal intake with multiple case types:
"If you've been injured in an auto accident, press 1. For all other matters, press 2."
Auto PI and general PI often have different buyers. One question, correct routing.
For Medicare during AEP:
"For Medicare Advantage, press 1. For Medicare Supplement, press 2."
MA buyers and Medigap buyers are different in most networks. Route correctly and let the agent handle remaining qualification.
The question nobody should ask first: "Please enter your zip code." Zip matters for local routing, but caller ID area code often covers it. If you must collect zip, make it optional — "enter your zip code or press pound to skip."
Strong opinion: I think the obsession with pre-call qualification is mostly cope. Buyers who demand four-question IVRs are usually optimizing for their comfort, not their close rate. Strong closers often prefer volume with agent-side filtering.
Should I gate unqualified callers out of the IVR entirely?
Rarely. Soft gating works better — route likely-unqualified callers to a lower-tier buyer or discovery queue. Let a human confirm they're unqualified. The caller who "presses 2 for renter" might actually be house-sitting and calling about their parents' AC.
The exception: compliance-required gating. TCPA consent verification, age verification for regulated products, state licensing restrictions. If you legally can't serve them, gate them out. Otherwise, route and let humans handle exceptions.
Technical Configuration
What timeout should I set between prompts?
5-8 seconds before repeating. 15-20 seconds before escalating to an agent.
Too short (3 seconds) and you cut off slow responders — older demographics, callers distracted by the leak they're calling about. Too long (15 seconds of silence before the prompt repeats) feels broken. Test with real callers, not your internal team.
Should I enable barge-in (letting callers interrupt prompts)?
Yes. Always.
Barge-in lets callers press 1 before the prompt finishes saying "...for service, press 1." Return callers don't need to hear the full menu. Impatient callers (most of them) want to press and go.
Without barge-in, callers mash the button repeatedly, get frustrated when nothing happens, and sometimes hang up thinking the system is broken.
Look for it in your platform's prompt settings and enable it. There's no good reason not to.
How do I handle callers who don't press anything?
Route them to an agent. Don't disconnect.
"No input" usually means one of three things: keypad issues, confusion about options, or deliberately waiting for a human. All three are callers worth keeping.
Configure: timeout at 15 seconds → route to agent queue. Don't replay the prompt more than once — if they didn't respond twice, they're not going to respond a third time.
Common Mistakes
Five common mistakes:
Copying a competitor's IVR without understanding why. That 4-level IVR works for them because they're running a different campaign with different buyer requirements.
Adding menus to "collect more data". Data your buyers don't use is abandonment you're paying for.
Using industry jargon in prompts. Many callers don't know what "HVAC" or "intake" means. Use the words they use.
Setting timeouts too short. 3 seconds isn't enough. Real callers are distracted or holding a phone in one hand and a mop in the other.
Never testing with real callers. Your team knows the menu. Test with people who don't. (It's annoying to recruit test callers, so you skip it, and then you wonder why abandonment is high.)
IVR Design FAQ: Quick Answers
How many IVR menu levels should I use?
One. Two maximum for high-value verticals like mass tort or Medicare where qualification directly affects payout. Every extra menu level is another place for a caller to hang up, and the losses stack. Move routing complexity to the backend and keep caller-facing menus minimal.
Should I use DTMF keypad input or speech recognition?
DTMF for routing decisions, speech recognition for optional convenience. DTMF is highly reliable across phone types and environments, while accents, background noise and speakerphone degrade speech recognition fast. A misrouted call costs more than the seconds saved by voice input. Use speech for low-stakes confirmations if you want, but route with keypad.
How long should my IVR greeting be?
Aim for under 8 seconds from pickup to first option. Cut the company history, award mentions and verbose disclaimers, then get straight to the choice: thank the caller, name the options and offer a stay-on-the-line default.
Can I qualify callers without forcing multiple menu levels?
Yes. Front-load your highest-signal qualification question at menu one — service type, intent, or emergency vs scheduled — then use backend logic for everything else. Caller ID area code can often stand in for a zip prompt, and time of day handles hours-based routing automatically. One menu with smart backend routing beats three menus with dumb routing every time.
Try VeloCalls for Your Vertical
Call tracking and routing platform for HVAC, plumbing, roofing, PI lawyers, Medicare brokers, and insurance. Smart routing, real-time bidding, visual IVR builder, AI conversation intelligence. Per-minute pricing — Managed starts at 4¢/min, BYOC at 2¢/min, both drop as you scale.