Call RoutingNovember 19, 20267 min read

Ring timeout settings: how long to ring and what happens next

Use 15–25s per target and a 30–60s queue, then overflow to a backup or voicemail. This guide gives concrete ring timers and a clean, loop‑free call path.

CallFlow Engineering Team

Telecom engineering and support at CallFlow (ALERTSIO LLC)

Ring timeout settings: how long to ring and what happens next – Call Routing article from the CallFlow blog

Set each target to 15–25 seconds, let a queue hold for 30–60 seconds, then overflow for 15–20 seconds, and end in voicemail after 20–30 seconds. After each timer, move straight to the next step without looping back. Also avoid personal voicemail picking up early. Follow the steps below and you’ll have a clean, tested call chain with clear ring timeout settings in about 20 minutes.

Use these starting points and tune by what you see in your logs and test calls:

  • Targets (single phones or small ring groups, a set of phones that ring together): 15–25 seconds.
  • Queues (a holding step with hold music that rings available agents): 30–60 seconds.
  • Overflow targets (on-call mobiles or a second team): 15–20 seconds.
  • Final voicemail: 20–30 seconds.

These windows match how people answer and how mobile carriers cut to voicemail. Most mobiles flip to voicemail around 20–30 seconds. Landlines and SIP phones (internet phones registered to an app or a PBX, your office phone system) can ring longer. If you let a mobile ring 30+ seconds, you risk its personal voicemail answering before your platform can overflow. That’s the “voicemail race” you want to avoid.

We’ll carry one setup through the article. A service business routes its main number to a primary ring group, then a short queue, then an on-call mobile, then voicemail. We’ll pin numbers to each step so you can copy them and adjust.

Why do calls hit voicemail too soon?

A voicemail race is when the agent’s personal voicemail answers before your platform times out and overflows. The caller hears personal voicemail, and your routing stops right there. You never reach the next step.

Carriers and devices set their own limits. Many mobiles jump to voicemail at 20–30 seconds, and some networks don’t let you extend that. Even where a star code exists to change ring time, it often caps at 30 seconds and may not apply to forwarded business calls.

You can fix the parts you control:

  • Shorten the per-target ring so your platform moves on before personal voicemail answers.
  • Put a short queue in front to smooth short delays and avoid long rings on a single phone.
  • Add a one-digit IVR (interactive voice response, a menu that asks the caller to press a key) before forwarding to external mobiles. Personal voicemail can’t press a key, so it won’t steal the call. See the setup ideas in this voicemail-race fix.

Set per-target ring time and stop voicemail races

Start at 18–22 seconds for mobiles to beat voicemail; go up to 25 seconds for landlines or SIP/browser agents if they’re at a desk or logged into an app.

For each leg, set a hard cap. Don’t let any one target ring longer than its timer. If a phone often answers later than 22 seconds, it probably isn’t a reliable first target—move it to overflow.

SIP or browser agents answer faster when the person is active in the app. They also don’t have personal voicemail races. If your team sits at a PC, prefer SIP/browser during staffed hours and keep mobiles for overflow.

Simultaneous vs sequential ring

Simultaneous ring calls several targets at once. You get faster answers, but you raise the risk of a voicemail race when any mobile in the mix cuts to voicemail. If you must ring mobiles at the same time, keep each per-target timer short (15–18 seconds) or insert a one-digit IVR before that step. Another guardrail is to put mobiles as a second step after a queue or primary desk phones. For setup tips, see simultaneous ring basics.

Sequential or priority routing calls one target or group, then moves on. Order targets by who is likeliest to answer. Cap each leg to avoid long waits. A classic order is SIP/browser agents first, then desk phones, then mobiles.

Queue timeout and overflow without loops

A queue is a holding step that plays hold music and offers calls to available agents. The queue timeout is the max time a caller can wait in that step before moving on.

Start at 30–45 seconds for small teams. You can push to 60 seconds if you truly staff a queue during peak hours and know agents free up often. Tie your choice to a service target like “80% answered in 20 seconds.” If you can’t hit that, use a shorter queue and overflow faster.

Set a clear overflow order and never loop. A safe pattern is: queue -> overflow team -> final voicemail. Don’t send the caller back to the same queue or ring group that just failed. Loops create endless ringing and hangups. If you need a second pass, use a different team or an IVR branch. More on patterns in queue timeout and overflow.

Chain overflow: a clean order that answers more calls

Here’s the running example with specific timers you can copy, then tune:

  1. Main number -> Primary ring group: 20 seconds. This group can be your SIP/browser agents or front-desk landlines. Twenty seconds allows four rings and fits most human answer behavior.

  2. Primary ring group -> Queue: 45 seconds. Hold music plays while the system offers the call to any agent who frees up. If you often clear the queue in under 30 seconds, drop the timer to 30–35 seconds to speed up the path.

  3. Queue -> Overflow on-call mobile: 15 seconds. Keep overflow to mobiles short to avoid a voicemail race. If you must use simultaneous ring on two mobiles, cap each at 15 seconds.

  4. Overflow mobile -> Voicemail: 25 seconds. Use your business voicemail here, not a personal mailbox.

Where to place an IVR: If you need a front-door menu (“Press 1 for sales, 2 for service”), put it before the primary ring group. If your only goal is to stop personal voicemail from answering on mobiles, insert a one-digit IVR right before the overflow mobiles. That adds little delay and blocks external voicemail pickup.

Account for whisper time. A whisper is a brief audio message your agent hears before they answer (“New lead from Google Ads”). It adds a second or two; subtract that from the per-target timer so you still beat mobile voicemail.

If you use CallFlow, you can set per-target ring timers, queue timeouts, overflow order, and a simple one-digit IVR in one place. Numbers route over multiple redundant carriers, and you pay from a prepaid wallet with no contract.

Illustrative example

Main to group, queue, overflow, voicemailDiagram of Main to group, queue, overflow, voicemail. Steps: Caller; Main number; Primary group (20s); Queue (45s); On-call mobile (15s); Business VM (25s); End. Connections: Caller to Main number; Main number to Primary group; Primary group to Queue (20s no answer); Queue to On-call mobile (45s no agent); On-call mobile to Business VM (15s no answer); Business VM to End (save message).20s no answer45s no agent15s no answersave messageCallerMain numberPrimary group20sQueue45sOn-call mobile15sBusiness VM25sEnd
Illustrative exampleMain to group, queue, overflow, voicemail Clean timers prevent voicemail races and loops.

Country and device notes that change ring limits

Mobile voicemail behavior varies by carrier and region. Many mobiles cap ring time near 20–30 seconds. Some carriers let you tweak it a little with a star code, but many don’t, and those settings often don’t apply to forwarded business calls. Don’t rely on handset settings for your routing. Control timers in your platform instead.

When forwarding across borders (for example, US callers to agents in India, the Philippines, Thailand, Bangladesh, or Pakistan), network latency slightly delays answer signals. Keep per-target timers shorter on mobiles in the destination country, and prefer SIP or browser agents during staffed hours. If your overflow goes to an international mobile, aim for 15–18 seconds on that leg to beat local voicemail.

If you buy a number in one country and forward to another, test both directions at peak times. Some paths ring longer before the far-end network sends a busy or no-answer signal. Your queue absorbs small delays, but your per-target timers should still be tight enough to avoid voicemail pickup.

Test your timers end to end (5-minute checklist)

  • Call your main number from two test phones: one mobile and one landline or VoIP (internet calling). Start a stopwatch on connect. This catches caller-side differences.
  • Time the primary ring group. You should hear 20 seconds of ringing, then the music or prompt for the queue within ±2 seconds. Note the actual time.
  • Stay on the line. The queue should hold for 45 seconds, then move to overflow. Listen for the ringback to stop and start on schedule.
  • Let the overflow mobile ring. It should ring 15 seconds, then your business voicemail should play. Confirm no personal voicemail picked up early.
  • Check your call logs. Each step should show a clear end state (ringing, answered, no answer, or busy), with durations close to your timers. If you see the same step repeated, you’ve created a loop—fix the path. Use this test call checklist to keep a record. (If your phone system shows SIP codes, ringing usually appears as provisional responses and timeouts as a busy or no-answer.)

What “good” looks like: each step hands off within two seconds of your target; no repeated steps or loops; final voicemail only after every step runs. If a step often runs long, shorten that timer by a few seconds or move that target later in the order. If mobiles keep grabbing calls with personal voicemail, add a one-digit IVR before that step or cut the mobile timer to 15–18 seconds. For more overflow patterns, see queue timeout and overflow.

Put these timers in place today

You can get a number and build this chain in CallFlow in minutes, with usage-based billing from a prepaid wallet. Create an account at CallFlow or contact our team for help tuning your timers.

Frequently asked questions

How many rings should I set before voicemail?

Set individual targets to ring for about 15–25 seconds (roughly three to five rings). Start around 20 seconds for primary desk phones or SIP/browser agents, and keep mobiles at the lower end (15–18s) to avoid personal voicemail. For final voicemail, allow 20–30 seconds so callers can leave a message. Make each leg a hard cap so the system moves to the next step on timeout.

What is a good no‑answer timeout for a call queue?

For small teams, use a queue timeout of 30–45 seconds; increase to 60 seconds only if agents reliably free up within that window. The queue timer should reflect how often agents answer: shorter when you miss service targets, longer when you commonly clear waits. After the queue times out, overflow immediately to the next target rather than returning to the same queue.

Can I make my phone ring longer before carrier voicemail answers?

Often you cannot reliably extend how long a mobile rings because carriers and handsets control voicemail cut‑over. The practical fix is to shorten your per‑target timers and use a queue or a brief IVR before forwarding to mobiles. That keeps the platform in control and prevents personal voicemail from stealing calls instead of trying to force the carrier to delay voicemail.

Does simultaneous ring require shorter timeouts than sequential?

Yes. With simultaneous ring, any one mobile’s voicemail can win the race, so cap per‑target timers shorter—around 15–18 seconds for mobiles—unless all targets are SIP/browser or desk phones. For sequential routing you can use slightly longer legs (20–25s for desk phones) because only one target faces voicemail at a time. Another option is to put mobiles after a queue or IVR.

Will longer ring time hurt answer rate or increase spam flags?

Longer ring times can lower answer rates because callers drop or personal voicemail answers instead of a live agent. It won’t directly change spam scoring from networks, but repeated long unanswered calls can look like poor routing in your logs and increase drops. Keep per‑target timers tight and use a short queue to raise live answers and reduce voicemail races.

How do I stop overflow loops in my call routing?

Design a strict overflow chain and use hard caps on each leg: primary group → queue → overflow team → final voicemail. Never send a timed‑out call back to the same group that just failed. If you need a second pass, route to a different team or an IVR branch. Test end‑to‑end and check logs so you see any unintended back‑routes, and fix them promptly.

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 →