You finished a job last Tuesday. That afternoon, three potential customers called your business number. None of them reached you. Your phone never rang.
You found out on Friday when someone texted: "tried calling, got some weird recording." Your call forwarding had silently broken. Three days. No alert. No notification. Just missed calls you'll never know about.
This guide covers every reason call forwarding stops working and exactly how to fix it — on iPhones, Android phones, AT&T, T-Mobile, Verizon, and VoIP lines. Plus, if you're tired of playing whack-a-mole with carrier codes, there's a setup at the end that removes the dependency entirely.
Why Call Forwarding Silently Breaks
The frustrating thing about call forwarding failures isn't just that they happen — it's that they give you zero warning. There's no notification. Your phone looks completely normal. The calls just quietly disappear.
Here are the most common triggers:
- Carrier account changes: Changing your plan, upgrading your device, or calling support to adjust billing. Any backend change on your carrier's side can silently reset conditional forwarding codes.
- SIM swaps and number ports: Moving your number to a new SIM or porting it between carriers clears forwarding settings completely.
- iOS updates: Apple's Live Voicemail feature (iOS 17+) re-enables itself or changes priority after some updates, intercepting calls before your forwarding code fires.
- WiFi calling toggles: Switching WiFi calling on or off changes how your phone handles incoming calls at the network level, which can interfere with conditional forwarding behavior.
- Number porting: If you transferred a number from one provider to another, forwarding rules set on the old provider don't carry over.
- Plan downgrades: Some lower-tier plans remove conditional forwarding as a feature without telling you.
The pattern is almost always the same: something changes on your carrier account, forwarding silently resets, and you don't find out until a customer mentions it.
iPhone-Specific Fixes
iPhones have a specific issue that causes call forwarding to fail without any error message.
Turn Off Live Voicemail First
If you're on an iPhone running iOS 17 or later, Live Voicemail is the most likely culprit. Apple's Live Voicemail feature intercepts unanswered calls and transcribes them locally on your device — and because it activates before your forwarding code fires, the call never gets a chance to forward.
To turn it off:
- Go to Settings → Phone
- Scroll down to Live Voicemail
- Toggle it off
Then re-enter your forwarding code and test immediately. For most businesses, this single step resolves the problem.
Check Your Call Forwarding Settings on iPhone
After disabling Live Voicemail, verify your forwarding code is still active. On iPhone, you can check your call forwarding status:
- Go to Settings → Phone → Call Forwarding
- Confirm the toggle is on and the forwarding number is correct
If the number looks correct but forwarding still doesn't work, deactivate it manually (##004# on AT&T/T-Mobile, or *73 on Verizon) then re-enter the activation code from scratch.
Focus Modes and Do Not Disturb
Focus modes, Do Not Disturb, and Screen Time settings affect how your iPhone handles incoming calls — but they don't prevent conditional forwarding from routing calls. If your forwarding is set up correctly but you're still not receiving transfers you expect to receive, check your Focus settings. A Focus mode set to block all calls except favorites will silence even forwarded calls that make it through to your device.
AT&T and T-Mobile Fixes (GSM Carriers)
AT&T, T-Mobile, and the MVNOs that run on their networks (Cricket, Boost, Metro, Mint, etc.) use the GSM MMI code system for conditional forwarding.
Deactivate and Reactivate the Code
The fastest fix is a clean reset:
- Deactivate everything: Dial
##004#and press call. You'll get a confirmation message. This clears all conditional forwarding rules at once. - Wait 30 seconds. (Carrier backend needs to clear the setting before you can reactivate.)
- Reactivate: Dial
**004*<your_nextphone_number>#and press call. Confirm the success message. - Test immediately: Call your business number from a different phone, let it ring without answering, and confirm the AI picks up.
If you'd rather your phone ring for a few seconds before forwarding kicks in, use the no-answer code instead: **61*<number>*11*20# (where 20 = 4 rings, each 5 seconds). To clear just the no-answer rule: ##61#.
GSM Code Reference
| Condition | Activate | Deactivate |
|---|---|---|
| All conditional (busy + no answer + unreachable) | **004*<number># | ##004# |
| No answer only | **61*<number>*11*<seconds># | ##61# |
| Busy only | **67*<number># | ##67# |
| Unreachable only | **62*<number># | ##62# |
Replace <number> with your NextPhone number, including the area code (e.g., **004*14155551234#).
VoLTE and Wi-Fi Calling Interaction
On some AT&T and T-Mobile plans, enabling Wi-Fi Calling changes how the network handles unanswered calls. If you turned on Wi-Fi Calling recently and forwarding broke around the same time, try toggling Wi-Fi Calling off (Settings → Phone → Wi-Fi Calling), then reset and reactivate your forwarding code.
Verizon Fixes
Verizon uses a different forwarding code family. The GSM codes (**61*, **004*) don't work on Verizon lines. If you've been entering those and getting errors, that's why.
Verizon Conditional Forwarding Codes
| Condition | Activate | Deactivate |
|---|---|---|
| No answer (forward if unanswered) | *71 <number> then call | *73 |
| Busy (forward if line is busy) | *90 <number> then call | *91 |
| All calls (unconditional) | *72 <number> then call | *73 |
For most business setups on Verizon, *71 is what you want: your phone rings normally, and if you don't pick up within a few rings, the call forwards to your NextPhone number where the AI answers.
Check in My Verizon App
Verizon also lets you manage call forwarding through the My Verizon app or website. If you're not sure whether your dial code went through, log in to My Verizon → Account → Device settings → Call Forwarding. This shows you exactly what's configured and lets you update it without dealing with codes.
Verizon Advanced Calling
If you have Verizon's Advanced Calling (HD Voice / VoLTE) enabled, forwarding behavior can change. Try toggling Advanced Calling off temporarily, re-entering your forwarding code, and testing. If it works, you can re-enable Advanced Calling afterward — in most cases, forwarding continues to function normally once it's been set while Advanced Calling is active.
VoIP Line Fixes (RingCentral, OpenPhone, Google Voice, Ooma, etc.)
If your business number is on a VoIP platform rather than a traditional carrier, dial codes don't apply. VoIP platforms manage call routing in their app or admin portal, not through MMI codes. Dialing **004*... on a VoIP line will either fail silently or produce a "not supported" error.
How to Find Your VoIP Provider's Forwarding Settings
Every major VoIP provider handles this differently:
- RingCentral: Admin Portal → Phone System → Users → [User] → Call Handling
- OpenPhone: Settings → Your phone number → Call Forwarding
- Google Voice: Settings (gear icon) → Calls → Forward calls to
- Ooma: My Ooma → Preferences → Call Forwarding
- Nextiva: NextOS admin portal → Users → Call Routing
If your VoIP platform isn't listed here, search "[provider name] call forwarding setup" in their help center — the setting is almost always under call routing, call handling, or number settings.
VoIP Forwarding vs Carrier Forwarding
One practical advantage of VoIP forwarding: you can see and edit it in a dashboard without memorizing codes. But VoIP forwarding has its own failure mode — if your internet goes down or the VoIP platform has an outage, forwarding stops working. Traditional carrier forwarding routes at the network level, so it works even without an internet connection on your device.
How to Test That Forwarding Is Actually Working
Testing forwarding seems obvious, but most people don't do it systematically enough to catch the edge cases.
The 4-Step Test
- Unconditional path: Call your business number from a different phone (a cell or a friend's phone — not your business line). Verify the AI or destination answers.
- No-answer path: Call your business number from a different phone and don't pick up your phone at all. Let it ring. Confirm it forwards after the configured delay.
- Busy path: Put your phone on an active call, then call your business number from a third phone. Confirm it forwards immediately instead of getting a busy signal.
- After-hours or time-based: If you have different routing by time, call during and outside business hours and confirm each routes correctly.
Re-run all four steps after any change: new phone, carrier account update, iOS update, or plan change. Set a monthly calendar reminder to test. Forwarding silently breaking for 2–4 weeks before a customer mentions it is common — across the 1,446,980+ calls our AI receptionist has answered, a non-trivial share involve businesses whose forwarding had been broken for days and they had no idea.
Checking What Code Is Active
On GSM carriers (AT&T, T-Mobile), you can query your current forwarding status:
- Check all conditional forwarding: Dial
*#004#— the network returns what's set for each condition (no answer, busy, unreachable) - Check no-answer only: Dial
*#61# - Check unconditional: Dial
*#21#
If the number shown doesn't match your NextPhone number, deactivate and re-enter the code.
Why Forwarding Keeps Breaking (The Structural Problem)
If you've fixed your forwarding only to have it break again a few weeks later, you're not doing anything wrong. Carrier-level call forwarding is a "set and remember to re-check it" system with no built-in reliability layer.
The fundamental issue: conditional forwarding is implemented differently by every carrier, behaves differently across device types and software versions, and has no monitoring or notification mechanism. When something breaks it, you find out from a customer — after however many calls have already been missed.
For a business getting 40–60 calls a month, even two or three days of silently broken forwarding can mean 8–15 missed calls. At a 20% booking rate for a typical home services job at $3,500 per project, that's real revenue sitting in a voicemail black hole. According to Invoca's research on home services businesses, 74.1% of calls to home services businesses already go unanswered under normal conditions. Broken forwarding makes an already fragile system worse.
The other problem: multiple numbers multiply the risk. If you're forwarding a main line, an after-hours number, and a Google Voice number into a single AI receptionist, any one of those three carrier legs can break independently — and they all fail silently.
A More Reliable Setup: AI Routing Without the Forwarding Dependency
If you're tired of debugging carrier codes, there's an architectural change worth understanding.
The traditional approach sends calls through a chain: your carrier → conditional forwarding code → destination. Every link in that chain can fail.
The approach that removes the fragility: your AI receptionist answers on its own dedicated number, and that number is what you forward everything into. From there, the AI handles routing based on what the caller actually needs — transferring to your cell for emergencies and sales calls, handling routine inquiries outright, and capturing messages for everything else.
This is the intelligent layer between your business number and your cell. The AI greets the caller, handles or qualifies the request, then transfers to whoever owns that call type — without relying on carrier forwarding codes that can silently reset.
The key difference: the AI never relies on your carrier's conditional forwarding to answer the call. It's always listening on its own number. You still forward your existing numbers into it using whichever codes your carrier supports, but if a forwarding leg breaks, the only thing that changes is that line stops routing — not that the whole system goes dark. You can set up a secondary forwarding line or port numbers in as needed.
Across the calls our system handles, the most common reasons people call — appointment booking, service questions, quote requests, status checks, hours and directions — are ones the AI resolves outright. Only a small fraction need a live transfer to your team. So even when a forwarding leg breaks temporarily, the impact is contained, and restoring it takes a straightforward setup rather than a full troubleshooting session.
NextPhone answers in under 5 seconds, resolves 90–95% of calls without human escalation, and maintains 99% positive caller sentiment across all industries. It connects to Clio and HubSpot natively and to 6,000+ other tools via Zapier, so a captured lead or booked appointment lands in your CRM without manual entry. For plumbers, HVAC contractors, and other field service businesses where the owner is hands-on during the day, this setup means not having to rely on fragile carrier codes — and not having to wonder whether forwarding is still working.
Start your free 7-day trial of NextPhone — forward your first line in minutes and confirm it's working with a test call before you walk away.
Frequently Asked Questions
Why does my call forwarding keep turning off?
Carrier conditional forwarding codes get reset by account-level changes — plan adjustments, SIM swaps, device upgrades, support interactions on your account, and sometimes iOS updates. On iPhones, Live Voicemail (iOS 17+) can re-enable itself after updates and silently intercept calls before forwarding fires. Set a monthly calendar reminder to test forwarding from a different phone. If it keeps breaking repeatedly with no account changes, contact your carrier directly — some plans exclude conditional forwarding or throttle it in ways that cause intermittent failures.
How do I know if my call forwarding is working right now?
On AT&T or T-Mobile, dial *#004# and press call — the network returns what's set for each conditional forward (no answer, busy, unreachable). On Verizon, check the My Verizon app under Call Forwarding. For VoIP lines, log into your provider's portal. The most reliable check is always a live test: call your business number from a different phone, let it ring without answering, and confirm it reaches your intended destination.
What's the difference between *72 and *004 for call forwarding?
*72 is Verizon/CDMA unconditional forwarding — it routes every call immediately, before your phone even rings. **004* is the GSM conditional code (AT&T, T-Mobile, and their MVNOs) that forwards only when you're busy, don't answer, or are unreachable. For most business setups, you want conditional forwarding: your phone rings first, and only if you don't pick up does the call route to the AI. Use *71 on Verizon for conditional no-answer forwarding, or **004*<number># on AT&T/T-Mobile for all-condition conditional forwarding in a single code.
Can I have multiple numbers forward to the same AI receptionist?
Yes. Your NextPhone number is just a standard phone number, so you can forward as many lines as you want into it — your main business line, an after-hours number, a Google Voice number, an old landline — and the AI handles all of them with the same training, hours, and routing rules. Each forwarding line is set up independently (each using its own carrier's codes or portal), but they all ring into the same AI.
Why does call forwarding work on WiFi but not on cellular?
If you use WiFi calling and have conditional forwarding set via dial code, the two systems can conflict. Carrier dial codes apply to the cellular network; WiFi calling routes the call differently. On some plans, the cellular conditional forwarding code doesn't apply to calls made over WiFi. Try disabling WiFi calling temporarily, re-activating your forwarding code, then re-enabling WiFi calling. If the issue persists, contact your carrier — some plans require you to set forwarding through the account portal rather than via dial code to cover both WiFi and cellular calls.
My forwarding code goes through but callers still hear "number not in service" — what's wrong?
This usually means the forwarding code activated successfully, but there's a configuration issue with the destination. Verify the destination number (your NextPhone number) is correct and able to accept calls. Check if there are any call screening or spam-filter settings on the destination line that might be blocking inbound forwarded calls. If you're using **61* with a ring-time parameter, confirm the *11* syntax is correct for your carrier — some carriers use a different parameter position. Re-enter the code with the full number including area code.
Don't Let Forwarding Failures Cost You Customers
Call forwarding is a single point of failure in your phone setup — and it fails silently. Most businesses don't find out until a customer mentions it.
The fix for any single carrier is usually straightforward: reset the code, check Live Voicemail on iPhone, look in the VoIP portal. But the deeper fix is a setup that doesn't depend on carrier codes functioning correctly at all times.
Forward your existing numbers into an AI receptionist that answers on its own dedicated line. The AI handles routine calls, routes emergencies to your cell, and captures leads around the clock — without relying on a carrier code that can quietly reset on a Tuesday afternoon.
Start your free 7-day trial of NextPhone today and stop losing customers to forwarding failures you'd never know happened.