Call RoutingNovember 18, 202610 min read

Screening IVR for pay‑per‑call: prequalify and route buyers

Build a short screening IVR that asks 1–3 qualifying questions, then routes only good calls to buyers by windows, caps, and priority, with clean overflow paths.

CallFlow Engineering Team

Telecom engineering and support at CallFlow (ALERTSIO LLC)

Screening IVR for pay‑per‑call: prequalify and route buyers – Call Routing article from the CallFlow blog

You build a screening IVR for pay-per-call by asking one to three keypad questions. Send only the “yes” path into a buyer router that uses priority, open-hour windows, and caps. Set a short overflow chain—next buyer, then a brief queue, then voicemail—so good calls don’t die on hold. You’ll end with a working menu that prequalifies callers and routes them to the right buyers in about an hour, including tests.

Pick the 1–3 questions that qualify your calls

One to three questions is the sweet spot. It gives you enough signal to filter junk without scaring off real buyers. Each extra prompt costs callers, so keep the full menu under about 30 seconds.

Use DTMF (keypad press, where the caller taps 1, 2, 3) instead of speech. It works better on noisy mobile lines and across accents in the US, India, the Philippines, Thailand, Bangladesh, and Pakistan. Keep options clear and short. Never use jargon like “policyholder of record” when “the person on the policy” does the job.

Aim your questions at:

  • Intent: new vs existing customer.
  • Eligibility: homeowner vs renter, age bracket, loan amount band.
  • Urgency: ready today vs later.

Pick answers that route to real paths. Avoid dead ends like “Press 3 for information” if you have nowhere useful to send them. If you run more than one language, ask for language first, then keep the main path short. For example, start with “For English press 1, Hindi 2” as the very first message.

Example screening menus you can copy

Home services (HVAC, plumbing, roofing)

  • Greeting: “Thanks for calling. To check service options, answer two quick questions.”
  • Q1 intent: “Press 1 if this is a new service request. Press 2 if you have an existing work order.”
  • Q2 urgency (if new): “Press 1 if you need service today. Press 2 for another day.”
  • Paths:
    • New + Today = Qualified. Send to router.
    • New + Later = Maybe. Route to lower-priority buyer or queue.
    • Existing = Not Qualified for pay-per-call. Send to info line or end.
  • Neutral wording: Do not say “priority service” on 1; it biases the answer.
  • Confirm high value: After “New + Today”, add “You selected service today, press 1 to confirm.”

Insurance (auto, health, home)

  • Greeting: “We’ll ask up to two questions to connect you.”
  • Q1 intent: “Press 1 for a new quote. Press 2 about an existing policy.”
  • Q2 eligibility (if new): “Press 1 if the policy is for you. Press 2 if you’re calling for someone else.”
  • Paths:
    • New + Me = Qualified. Router.
    • New + Someone else = Maybe. Route to a separate buyer who takes third-party calls.
    • Existing = Not Qualified. Send to carrier info IVR or voicemail with “we can’t service policy support.”
  • Call whisper (a brief message the buyer hears before connect): “New auto quote, caller is the primary.”

Finance (personal loans, debt relief)

  • Greeting: “Two quick questions to connect you.”
  • Q1 intent: “Press 1 to apply. Press 2 to check an existing application.”
  • Q2 eligibility (if apply): “Press 1 if your monthly income is above [local currency amount], press 2 if below.”
  • Paths:
    • Apply + Above = Qualified. Router.
    • Apply + Below = Not Qualified or Maybe (some buyers have lower thresholds). Route as set.
    • Existing = Not Qualified. Info line or end.

Keep the tone flat. Do not hint that one button gets a faster agent. You can pass context to the buyer with a whisper message like “New borrower, income above threshold” without adding time to the caller’s path.

For prompt writing craft, see IVR prompt best practices.

Example call path: 2-question IVR to buyers with windows and caps

2-question screen to buyers with overflowDiagram of 2-question screen to buyers with overflow. Steps: Caller; Campaign number (Local or toll-free); Screen IVR (Q1 Intent, Q2 Urgency); Buyer router (Priority + windows + caps); Buyer A (20s); Buyer B (20s); Queue (30s hold); Voicemail; Not qualified. Connections: Caller to Campaign number; Campaign number to Screen IVR; Screen IVR to Buyer router (Q1=New,Q2=Today); Screen IVR to Not qualified (Not qualified); Buyer router to Buyer A (try 20s); Buyer A to Buyer B (no answer); Buyer B to Queue (no answer); Queue to Voicemail (timeout).Q1=New,Q2=TodayNot qualifiedtry 20sno answerno answertimeoutCallerCampaign numberLocal or toll-freeScreen IVRQ1 Intent, Q2 UrgencyBuyer routerPriority + windows + capsNot qualifiedBuyer A20sBuyer B20sQueue30s holdVoicemail
Illustrative example2-question screen to buyers with overflow Qualified callers try Buyer A then B, then queue, then voicemail.

Use this pattern for a home services campaign in three states. Callers who press 1 (new) then 1 (ready today) go to the Qualified path. The router applies buyer priority, per-target call windows (their open hours), and daily or concurrent caps. If Buyer A does not answer in 20 seconds, or is capped or closed, try Buyer B for 20 seconds. Then put the caller in a short 30-second queue, and finally send them to voicemail.

Handle geography in the router with caller-state rules. Avoid asking for ZIP in the IVR. It slows the caller and is hard to validate by keypad.

Route by buyer windows, caps, and priority

Set per-target call windows (the hours the buyer takes calls, in their time zone). This blocks after-hours connects and keeps your billable calls aligned with buyer agreements. If you buy traffic across time zones, windows prevent a 9 a.m. caller in Manila from hitting a US buyer who opens at 9 a.m. Pacific.

Add caps. Daily caps limit how many calls a buyer takes per day. Concurrent caps limit how many simultaneous calls ring or connect for that buyer at once. When a cap is hit, the path should fall to the next buyer, then queue, then voicemail. Caps also protect you during spikes from over-delivery penalties.

Define priority order with a ring timer for each buyer, typically 15–25 seconds. The timer should be long enough to reach a live agent, but not so long that callers wait through dead air. If you run SIP (internet phone) or browser agents, and your team is in India, the Philippines, Thailand, Bangladesh, or Pakistan, add a couple of seconds to cover internet latency.

Spell out what happens when buyers do not answer or are capped:

  • Try Buyer A for 20 seconds.
  • If no answer or capped, try Buyer B for 20 seconds.
  • If both fail or are closed, place in a short queue for 30 seconds with hold music and a short message.
  • If still no answer, send to voicemail.

This usually breaks in two places. One, missing an overflow branch, so calls loop or drop. Two, very long ring timers that trap callers with no progress. Keep timers tight and always have the next step defined.

See more on setting buyer hours in per-target call windows.

What to do with unqualified, after-hours, or no-answer calls

Use the IVR to queue or send to voicemail based on time of day. During daytime, a 30-second queue can save calls when agents step away. At night or on weekends, skip the queue and play voicemail right away.

Write a clear voicemail prompt that sets a callback expectation: “Sorry we missed you. Leave your name, number, and ZIP. We’ll call you back within one business day.” Keep it under 12 seconds so more callers leave a message.

Send “Not Qualified” callers to a polite end or to a recorded info line. For example, if “existing customer” calls are not billable, say “We can’t help with policy support on this line. Please contact your insurer directly,” then end the call. Do not route them to buyers.

Use duplicate-caller suppression to handle repeats from the same number in a short window. Send them to a non-billable path or back to the info line instead of re-billing. For tactics, see duplicate call suppression.

Apply short-call filtering in your own reporting. Set a threshold, for example 10–20 seconds of talk time, and do not count shorter calls as billable. This protects buyers and keeps your optimization honest.

Build it step-by-step (in any call routing platform)

You can set up a screening IVR for pay-per-call with this flow on most platforms. In CallFlow, the same steps map to numbers, IVR, routers, buyers, queue, and voicemail.

  1. Get a campaign number and point it to an IVR.
  • Buy a local or toll-free number from your platform wallet and assign it to the campaign. Point the number’s destination to a new IVR (interactive voice response, the automated keypad menu).
  • If you serve more than one language, provision one number per language or add language selection as Q0.
  1. Create the IVR with 1–3 qualifying questions.
  • Record short prompts or use text-to-speech. Use DTMF (keypad presses) only. Avoid free-form speech.
  • Keep the total prompt time under about 30 seconds. Do not stack more than three inputs.
  1. Put language first if you need it.
  • “For English press 1, Hindi 2.” Then go straight to the main path. Do not repeat every message in both languages.
  1. Send the Qualified branch to a buyer router.
  • Qualified = your highest-value answer set (for our running example, New + Today).
  • Map all other answers to Maybe or Not Qualified now, so nothing dead-ends.
  1. Send Not Qualified to voicemail or end.
  • Use a polite message and hang up, or a short info line. Do not ring buyers.
  1. Add buyers (targets) to the router with endpoints and priorities.
  • For each buyer, add their phone number, SIP endpoint (internet phone), or browser agent. Set the priority order you want.
  • Turn on call whisper if your platform supports it. Keep it under two seconds: “New lead, urgent today.”
  1. Set ring timers, about 15–25 seconds per target.
  • Start at 20 seconds for each buyer. If you route across borders to SIP or browser agents, add a couple of seconds to account for network delay.
  • Keep the total ring time before queue under a minute.
  1. Set per-target call windows in each buyer’s local time zone.
  • Enter open hours and days. Block connects outside those windows. If the caller hits a closed buyer, they should fall to the next buyer automatically.
  • If your platform lets you, display windows in the buyer’s own time zone to avoid mistakes. See per-target call windows.
  1. Add daily and concurrent caps per buyer.
  • Daily: how many calls max per day. Concurrent: how many at once.
  • When a cap is reached, the path should try the next buyer.
  1. Define overflow: next buyer → queue → voicemail.
  • After the last buyer, add a short queue (30 seconds) with hold music and a brief “Please stay on the line” message.
  • After the queue timeout, send to voicemail.
  1. Enable call recording if you and your buyers need it.
  • Recording helps with QA and disputes. Check local laws on call recording and add a notice in the greeting if required in your country.
  1. Test each path end-to-end.
  • Call from your phone. Press each menu path. Confirm Q1+Q2 go to the right buyer and that ring timers behave as set.
  • Trigger after-hours and cap scenarios with test settings. Confirm the router falls to the next buyer, then queue, then voicemail.
  1. Validate duplicate and short-call handling.
  • Call twice from the same number within your suppression window. Make sure the second call routes to the non-billable path.
  • Verify your reporting excludes short calls under your threshold.

For a broader campaign setup checklist, see pay-per-call setup.

Test, measure, and tune without hurting conversion

Watch three numbers in your live logs: IVR completion rate, answer rate, and short-call rate. IVR completion rate is how many callers finish the menu and hit the router. Answer rate is how many connect to a buyer or agent. Short-call rate is how many connect but bail out fast.

If IVR drop-offs are high, shorten prompts or remove one question. Put your highest-disqualify question first so unqualified callers exit fast. Keep eligibility before intent when that makes sense—for debt relief, ask about total debt or income before interest in applying. Use neutral wording so you do not steer callers.

Adjust buyer priorities and windows monthly. If Buyer B outperforms Buyer A on answer rate and hold time, bump B up or give B a longer first shot. Rebalance caps if one buyer runs out by noon while others sit idle.

For cross-border teams on SIP or browser agents, test latency. Place calls from the markets you buy traffic in. If you hear long post-dial silence, trim ring timers for each hop and add a short queue message so callers know the call is working. Keep the whole chain tight—buyers A and B at 20 seconds each, queue 30 seconds, then voicemail.

A short aside if you want this without extra tools: CallFlow gives you US toll-free and local numbers, IVRs, buyer routers with priority, per-target windows and caps, queue with hold music, voicemail, call recording, and buyer whispers out of the box. You pay from a prepaid wallet with no monthly subscription.

Ship your menu and watch it for a week

Go live during business hours. Sit in the real-time log on day one. If you see many “New + Today” calls hitting voicemail, shorten ring timers or add a backup buyer. If too many callers hit the Maybe path, split that traffic with lower priority and track buyer acceptance.

If you need a platform that makes this build fast, you can register and try it with a small wallet top-up at callflow.solutions/register. Or message our team at /contact if you want help modeling your windows, caps, and overflow.

Frequently asked questions

How many IVR options before performance drops?

One to three keypad questions is the sweet spot. That gives enough signal to filter junk without scaring off callers. Keep the whole menu under about 30 seconds. Each extra prompt lowers completion rates and adds cost. If you need more detail, collect language first, then ask no more than two qualifying questions that send callers to real buyer paths.

Should I use voice recognition or DTMF for screening?

Use DTMF (keypad presses). It works more reliably on noisy mobile lines and across accents in the US, India, the Philippines, Thailand, Bangladesh, and Pakistan. Speech recognition can fail on poor connections or with heavy accent variety, which kills conversion. Keep prompts short, use clear numbers, and avoid free-form speech inputs for screening.

Can I record a consent or disclaimer inside the IVR?

Yes. You can play a recorded prompt that asks for confirmation and capture the call with CallFlow’s call recording feature. Record the short consent prompt and then require a DTMF confirmation (for example, press 1 to agree). Store the recorded file and the IVR action in your campaign logs for auditing and buyer requirements.

Does a screening IVR reduce payout because of call duration thresholds?

A screening IVR doesn’t automatically change buyer payouts. Many buyers or contracts use short-call filters in reporting (for example, ignore calls under a set talk time). CallFlow provides call recording and reporting so you can apply a short-call threshold in your analytics and exclude sub-threshold calls from billable reports, protecting buyers and your campaign integrity.

How do I handle state‑based routing along with IVR screening?

Do the geographic routing in the buyer router, not by asking callers to enter ZIP codes. Use caller-state rules (Caller ID lookup) to send the IVR’s qualified paths to the correct buyer group for that state. Combine state rules with per-target windows and caps so callers only hit buyers who are open and under their daily or concurrent limits.

What’s the best fallback: queue first or voicemail first?

Use a short queue first during business hours, then voicemail after a short hold. During the day, a 20–30 second queue with hold music saves real calls; if the queue times out, send to voicemail. Outside buyer hours, skip the queue and go straight to voicemail. Configure overflow as: next buyer, short queue, then voicemail.

From the team

CallFlow Engineering Team

Telecom engineering and support at CallFlow (ALERTSIO LLC)

The engineers and support staff who build and operate CallFlow's call-routing platform. We write from what we see running inbound routing for pay-per-call marketers, agencies and small businesses every day: routing rules, carrier behaviour, spam flags, and the configuration mistakes that quietly cost calls.

Ready to get started with CallFlow?

No subscription. Transparent usage billing. Per-number spam scores. Built for scale.

Create Free Account →