Call forwarding goes straight to voicemail: causes and fixes
Forwarded calls jumping to voicemail? Start with DND and spam blockers, then fix ring timers and voicemail races. A clean, step-by-step checklist you can run today.
Telecom engineering and support at CallFlow (ALERTSIO LLC)

Most of the time, when call forwarding goes straight to voicemail, the destination phone can’t ring because of Do Not Disturb, blocked unknown callers, no signal, or the phone is off. The next most common cause is a voicemail race: your platform rings the target, but the mobile carrier’s voicemail answers faster than your ring timer. First, turn off DND and call filters on the destination phone. Then set your platform’s ring time to about 20 to 25 seconds so a person can answer before any voicemail does.
Start here when call forwarding goes straight to voicemail
Two things cause most “forwarded calls go to voicemail” problems. First, the destination device can’t or won’t ring. On iPhone, Focus or Silence Unknown Callers may block it. On Android, Do Not Disturb or a spam filter may send it to voicemail. Weak signal, airplane mode, or a powered-off phone does the same.
Second, there’s a voicemail race. Your platform rings the target for a set time. The mobile carrier’s voicemail has its own timeout, often near 20 seconds. If your ring leg (the ring time for one target) is too long, carrier voicemail may grab the call before your next target gets a turn. If it’s too short, a real person can’t pick up in time.
Expect the destination device to ring out loud for about 20 to 25 seconds, giving a person time to answer, and for no voicemail to answer until you choose to overflow.
A clean checklist to stop voicemail pickup
Turn off Do Not Disturb/Focus on the destination phone. On iPhone, open Settings > Focus and turn it off. On Android, open Settings > Notifications > Do Not Disturb and turn it off.
Disable Silence/Block Unknown Callers and any call screening. On iPhone, Settings > Phone > Silence Unknown Callers > Off. On Android, open the Phone app settings, turn off “Block unknown/private numbers,” and turn off “Caller ID & spam” for now.
Turn off third-party call filter apps during tests. Your mobile provider’s call-blocking app, and tools such as Truecaller or Hiya, can intercept forwards. Disable them until you confirm normal ringing.
Reboot the destination device and check signal. Power it off and on. Verify cellular bars or Wi-Fi Calling are stable. If dual-SIM, make sure the correct line is active for calls.
Make a direct call to the destination number. Bypass the forward. If a direct call won’t ring or goes to voicemail, fix that first with the mobile operator.
Increase your platform’s ring time for each target to about 20–25 seconds. Avoid very short legs like 10–15 seconds. That’s too quick for a human to answer and often too close to the carrier’s voicemail delay.
Avoid simultaneous ringing of multiple mobiles if any has fast voicemail. Use sequential (priority) routing so only one mobile rings at a time. A single fast voicemail can steal the call. If you must use simultaneous ring, include a SIP softphone (an app that takes calls over the internet) or a browser agent (a phone in your browser) that has no carrier voicemail. See the setup details in Simultaneous ring vs priority routing.
Check time-of-day windows for each target. Make sure the target is “open” during your test, with the right time zone. If you use per-target hours, widen them while you test to avoid silent skips. More tips in per-target call windows.
Remove per-target caps temporarily. If you have daily or concurrent caps, lift them during testing. A hit cap can overflow to voicemail or to the next rule before any phone rings.
Check the destination phone’s own carrier forwarding settings. Conditional forwarding (CFNRY for no answer, CFB for busy) may be active and pointing to voicemail. Turn those off in handset settings or in your carrier app.
Use carrier star codes if your operator supports them. In some countries and on some operators, *72 enables unconditional forwarding and *73 cancels it. Codes vary by operator and country (US, India, Philippines, Thailand, Bangladesh, Pakistan). Some carriers use on-screen menus or USSD (short carrier codes you dial like *#). Check your operator’s guide, set the right mode, and test again.
Make one change at a time and test. Place a controlled test call after each change and note the outcome in your live logs. If a change helps, keep it. If not, revert and try the next step. A short, repeatable test plan helps — you can borrow steps from our test call forwarding checklist.
In a good test, a call to your forwarding number rings your target device for 20–25 seconds, a person can answer, and voicemail only takes over when you intend it to. If a direct call to the destination number still goes to voicemail too fast after steps 1–5, contact the mobile operator to adjust the voicemail delay or clear hidden conditional forwarding.
Fix voicemail races with proper ring timers
- 0 s – 5 sQueue hold music
- 5 s – 19 sMobile A rings
- 19 sOverflow to B
- 19 s – 39 sAgent B (browser) rings
- 20 sMobile voicemail ~20s
- 39 s – 60 sPlatform voicemail
Think of it as a race between your ring timer and the mobile carrier’s voicemail. Many mobiles answer voicemail near 20 seconds. If you let a mobile ring past that, its voicemail can grab the call and end the hunt path (the order your system tries numbers). If you cut the ring too short, a human misses it.
Set each ring leg (the ring time for one target) long enough for a person to reach the phone, but short of the known voicemail pickup when you can. In practice, 20 to 25 seconds works. If a specific mobile’s voicemail is very fast, trim that leg to 18–19 seconds and let the next device take a turn.
Prefer sequential routing over simultaneous ringing of several mobiles. One fast voicemail in a group can steal the call from every other target. If you need parallel reach, include SIP phones or browser agents that don’t have carrier voicemail.
Add a short entry queue with hold music (about 3–5 seconds) before the first ring. This keeps the caller engaged while your first target registers, wakes the app, or reconnects to data. If no one answers after your set of targets, let your queue or platform voicemail take over. Do it on a timer you control, not when carrier voicemail decides.
In testing, your call should ring Target A for about 18–20 seconds, then overflow to Target B before any mobile voicemail. It should reach voicemail only after your full path has tried live devices.
Conditional vs unconditional forwarding: pick the right mode
Unconditional forwarding (often called “call forward all”) sends every call to the forward, no matter what. Conditional forwarding sends calls only when the line is busy, not answered, or unreachable. Those conditions are often labeled CFB (busy), CFNRY (no reply), and CFU (unconditional) in device menus.
Double-forwarding can create loops or instant voicemail. For example, your platform forwards to a mobile, but that mobile has CFNRY to its own voicemail at 20 seconds. If your platform’s timer is longer, the mobile voicemail will win the race and the path stops. If the destination also forwards back to another number that forwards again, you can get stuck in a loop.
Use conditional forwarding when radio coverage is spotty or the first phone is shared. Send the first attempt to the mobile. On no-answer, overflow to a SIP desk phone or a browser agent. Avoid conditional forwarding on the destination line if you can manage all conditions on your platform instead. That way, you decide exactly when to overflow, queue, or take voicemail.
Star codes and conditional modes vary by operator and country. In the US, many carriers use *72/*73 for unconditional on/off. In India, the Philippines, Thailand, Bangladesh, and Pakistan, the codes differ. Some carriers use on-screen menus or USSD (short carrier codes). Make one change at a time, then place a test call to confirm the new mode.
Aim for one clean forward path with no loops, no unexpected second hops, and voicemail only when your platform sends it there.
Phone and app settings that block or silence callers
On iPhone, check three places. First, Settings > Focus > Do Not Disturb. Turn it off while you test. Second, Settings > Phone > Silence Unknown Callers. Turn it off so new callers ring. Third, Settings > Phone > Blocked Contacts. Make sure your test number isn’t on the list.
On Android, check the system Do Not Disturb under Settings > Notifications. Then open the Phone app’s settings and look for blocked callers or unknown/private number blocking. Some Android builds have “Call Screening” or “Spam and Call Screen.” Turn those off during tests so forwarded calls aren’t screened to voicemail.
Third-party filter apps can intercept forwards. Your mobile provider’s call-blocking app, and tools like Truecaller or Hiya, can silence a call. Disable them for now. Re-enable once you confirm clean ringing.
If you use a SIP softphone (an app that takes calls over the internet) or a browser agent (a phone in your browser), make sure the app is registered and allowed to ring. Check that laptop volume is up, the headset is selected, and the browser tab is active. On dual-SIM phones, confirm the correct SIM handles voice calls. Turn Wi-Fi Calling on or off as you intend.
When you call from an unrecognized test number, the phone should ring out loud for about 20–25 seconds with no “spam likely” screen and no instant voicemail.
Schedules, caps, and queues that send calls to voicemail
Routing rules can skip ringing even when a phone is fine. Closed time windows are the classic case. If the target is outside its schedule, the platform may send the call to voicemail or try the next route at once. Check each target’s hours and make sure time zones match the agent’s local time, especially for teams in the US, India, the Philippines, Thailand, Bangladesh, and Pakistan. As noted in step 8, widen per-target hours during testing to rule out silent skips.
Per-target caps can also cause overflows. A hit daily cap means no more calls for that target until the next day. A concurrent cap of zero or one can block new calls during long talks. Lift these caps during troubleshooting so you don’t confuse cap behavior with voicemail pickup.
If you use a queue, confirm its timeout and overflow target. A very short queue that dumps to voicemail after a few seconds looks like “won’t ring, goes to voicemail.” Give the queue a reasonable wait with hold music. Then overflow to your next targets, and only land in voicemail at the end.
For teams across countries, confirm local holidays and off-hours windows. A US holiday window might overlap a normal workday in Asia, and vice versa. Align windows to the agent’s time zone to avoid silent skips.
Your call should flow through open windows, hit live targets within caps, wait in queue only as long as you set, and reach voicemail only on your chosen overflow.
Prove where it fails using live logs and one change at a time
Run two tests. First, call the destination number directly. Let it ring and time it. Note whether a person answers or the carrier’s voicemail picks up, and when. Second, call your forwarding number and compare. If the direct call rings 22 seconds but the forwarded call cuts at 15, the issue is likely your platform’s ring timer or routing path. If both hit voicemail at 20 seconds, the destination carrier’s voicemail delay is winning.
Use live call logs to see which step answered. Look for timestamps per step, the total ring duration, and the final answer party. If the answer party is “voicemail” at the destination leg, you know carrier voicemail won. If answer happens on the platform before your full path, check for a queue or an IVR (a phone menu) sending to voicemail. For log tips, see call logs and call detail records (CDRs).
One short aside: on CallFlow you can watch real-time call logs while you test, adjust ring timers, switch between simultaneous and priority routing, and see the next call behave as expected.
If forwards still jump to voicemail after device fixes and ring-timer tuning, contact your operator. Ask them to check line-side conditional forwarding and the voicemail delay on the destination number. In some cases they can extend the delay or clear hidden CFNRY/CFB settings.
Line up your next tests and close the loop
- Pick one destination phone and make it clean: DND off, filters off, direct calls ring 20–25 seconds.
- Set your first ring leg to 18–20 seconds. Then overflow to a second device that has no carrier voicemail (SIP or browser).
- Add a short 3–5 second queue ahead of the first ring if your app or SIP takes a moment to register.
- Place five test calls and write down ring times and who answered. Adjust only one knob between calls.
If you need a platform that lets you set per-target ring times, switch between simultaneous and priority routing, use schedules, caps, queues, and IVR, and watch live logs while you test, you can try CallFlow with a prepaid wallet — register. If you have a complex case or need help reading your logs, reach out via our contact form.
Frequently asked questions
Why do forwarded calls go directly to voicemail instead of ringing?
Most often the destination phone can’t or won’t ring: Do Not Disturb, Silence Unknown Callers, a spam filter, no signal, airplane mode, or a powered-off device. Another common cause is a voicemail race: the carrier’s voicemail answers faster than your platform’s ring leg, so voicemail grabs the call before a live target can pick up.
How do I stop my iPhone from sending forwarded calls to voicemail?
Turn off Focus/Do Not Disturb and Silence Unknown Callers while you test. Check Settings > Phone > Blocked Contacts to make sure the forwarded number isn’t blocked. Reboot the phone and confirm cellular or Wi‑Fi Calling signal. Then increase your forwarding platform’s ring leg to about 20–25 seconds and run a direct test call to the handset.
Why do calls ring once and then go to voicemail when forwarded?
One ring then voicemail usually means either the phone is set to forward to voicemail on no-answer, or the carrier voicemail is answering almost immediately. If your platform’s ring leg is too short, a person can’t answer before the carrier voicemail triggers. Disable handset conditional forwarding, lengthen the platform ring leg to 20–25 seconds, and test again.
Can Silence Unknown Callers or spam filters cause forwarding to voicemail?
Yes. Silence Unknown Callers on iPhone and Android call‑screening or spam filters can send forwarded calls straight to voicemail. Third-party apps that screen calls can also intercept forwards. Turn those features and apps off during testing, make a direct call to the destination number, and verify it rings before blaming the forwarding path.
What ring time should I set to avoid voicemail pickup?
Set each ring leg (how long a target rings) to about 20–25 seconds so a person can answer before carrier voicemail typically answers. If a specific mobile has very fast voicemail, trim that leg to 18–19 seconds and let the next target take the overflow. Use sequential routing or add a SIP/browser agent to avoid one fast voicemail stealing the call.
Do carrier star codes work for turning call forwarding on and off?
Sometimes. Some operators provide star codes (for example, common patterns like *72/*73 in some markets) or USSD menus to enable or cancel forwarding, but codes vary by country and operator. If your handset or carrier app supports those codes, use them to change conditional or unconditional forwarding, then place a test call to confirm behavior.
From the team
CallFlow Engineering TeamTelecom 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 →