How to Forward Calls to Another Number on iPhone
iPhone call forwarding via Settings > Apps > Phone > Call Forwarding: Apple GSM steps, Dual SIM line picks, carrier codes, pass/fail tests, and coverage gaps.
Is it right for you?
Your checks are saved on this device only — they reset if you clear browser data or switch devices.
Quick answer
“How to forward calls to another number on iPhone” is unconditional diversion of inbound cellular voice. Apple documents the path as Settings → Apps → Phone → Call Forwarding, then Forward To for the destination [Apple Support: Set up call forwarding, checked 2026-10-25].
AT&T device articles for recent iPhones match the same Settings → Apps → Phone → Call Forwarding toggle and Forward To field [AT&T iPhone Call Forwarding, checked 2026-10-25].
Step checklist with pass/fail
| Step | Action | Pass | Fail / fix |
|---|---|---|---|
| 1 | Leave Airplane Mode off; confirm cellular bars | Carrier name visible | Wi-Fi only → move or wait; Apple says you must be in cellular range |
| 2 | Settings → Apps → Phone → Call Forwarding | Call Forwarding row opens | Missing on CDMA → use carrier portal/codes, not this menu |
| 3 | Dual SIM: pick the correct line | Line label matches the DID you want diverted | Wrong line still rings → configure each SIM separately |
| 4 | Enable → Forward To → full number → Back | Status bar shows Call Forwarding icon | No icon → setting never committed; retry on cellular |
| 5 | Second-phone test call to the iPhone number | Destination rings; iPhone usually does not | iPhone still rings → forwarding off or wrong line |
| 6 | Disable when finished | Icon gone; iPhone answers again | Stuck divert → carrier deactivate code (see the deactivate-codes guide on this site) |
Apple also warns that unexpected links asking you to enable call forwarding can be scams; ignore them and use Settings only [Apple call forwarding note].
What this setting does not move
The iPhone Call Forwarding switch redirects inbound cellular voice. It does not forward SMS, iMessage, RCS, FaceTime, WhatsApp, or other app calls. Plan a separate coverage path for those channels.
Immediate (unconditional) forwarding usually sends the call straight to the destination so the original iPhone never rings. That is different from transfer on a live answered call; for desk-phone handoff see office phone transfer.
Carrier codes when the menu is missing
Verizon wireless documents keypad codes such as *72 + 10-digit number to forward all calls and *73 to cancel (confirm on your account’s support article before dialing). Conditional no-answer style codes differ by carrier.
Apple states conditional forwarding (busy / not in service) must be set up with the carrier when supported. Do not reuse another network’s code without checking.
Hosted business numbers often divert in the PBX or carrier admin portal instead of the handset. Use the carrier or PBX admin tools for portal-side divert options.
Dual SIM and travel notes
Forwarding is per line. Configuring the personal eSIM does nothing to the work line. If both should divert, repeat the checklist twice.
Roaming can change whether the carrier accepts a handset forward request. If the toggle reverts, try again on the home network or set the divert in the carrier account portal.
Android users following a parallel runbook should use the Android forwarding guide on this site rather than pasting iPhone screenshots.
Unconditional vs conditional forwarding
Apple’s Call Forwarding toggle is unconditional: every inbound cellular voice call to that line diverts to the Forward To number while the feature is on. Conditional behavior (busy, no answer, unreachable) is not configured in that same iPhone menu. Apple’s guide tells you to contact the carrier when you need those rules.
Why this matters for a small office: if you only want overflow when the handset is busy, handset unconditional forward is the wrong tool. Use the carrier’s conditional codes or the PBX / hosted voice admin instead. Mixing both (handset always-forward plus PBX queue) creates loops that are hard to debug after hours.
Quick decision: need “always send my personal line to the front desk” → iPhone Call Forwarding. Need “ring me first, then overflow” → carrier conditional or business cloud PBX. For hosted DIDs, configure divert in the cloud admin rather than only on the handset.
Test wording for your runbook: place a call from a second phone while Forwarding is on; pass if only the destination rings. Place another call after you toggle it off; pass if the iPhone rings again. Log the timestamp and both numbers so support tickets are not guesswork.
Business scenarios and coverage gaps
Owner on vacation: forward the work eSIM to a colleague’s mobile or a shared desk phone. Confirm the destination can answer during your timezone hours, and turn the feature off on the first day back before the morning rush.
Storefront + warehouse: forward the published storefront DID to the warehouse lead’s line during receiving windows only. Put a calendar reminder to disable; forgotten forwards are a top cause of “customers say we never pick up” tickets.
On-call rotation: do not use a personal iPhone unconditional forward as a permanent on-call router. Prefer a hunt group or schedule-aware IVR so the divert target changes without touching Settings every week. Template ideas: phone tree template.
Coverage gap checklist: SMS and iMessage stay on the original Apple ID; FaceTime Audio is not the same as cellular voice forward; WhatsApp and other OTT apps need their own linked-device plan. Tell callers which channel still works if the voice divert is active.
Legal or compliance call recording: forwarding to a third party does not automatically inherit your recording disclosure. If your industry requires two-party consent language, update the destination side’s greeting, not only the iPhone toggle.
Troubleshooting when the toggle fails
No Call Forwarding row: confirm the line is GSM-style for this feature, cellular (not Wi-Fi only) is up, and you are looking under Settings → Apps → Phone. Older screenshots that skip Apps are outdated. CDMA-style accounts often hide the row; use the carrier portal or keypad codes instead.
Toggle flips back off: common on roaming, weak signal, or when the carrier rejects the forward registration. Retry on the home network with bars visible. If it still reverts, set the divert in the carrier account tools and treat the handset menu as display-only.
Icon shows but calls still ring the iPhone: wrong Dual SIM line, destination typed without country or area code when required, or a delay before the network finishes registering. Wait a minute, re-open the menu to confirm the number, then retest from a second phone.
Destination rings once then drops: destination may be blocking unknown callers, have its own forward loop, or be out of service. Call the destination directly first. Loops (A forwards to B, B forwards to A) should be cleared before you blame the iPhone.
Scam texts that say “tap to enable call forwarding”: Apple warns that unexpected links asking you to enable forwarding can be social engineering. Ignore them; only use Settings on the device you hold.
Carrier code reference (verify before dialing)
Keypad codes differ by carrier and plan. Examples often cited in U.S. consumer docs include *72 + destination to register unconditional forward and *73 to cancel on some Verizon wireless lines; other carriers publish *21*number# style GSM codes. Always open your own carrier’s support article for your account type before dialing, because MVNOs and business plans diverge.
After any code, still run the second-phone test. A voice prompt that says “call forwarding on” is not enough if the destination is wrong. To clear a stuck divert when the menu will not open, use the documented deactivate path or the carrier app; see the deactivate-codes sister page when the menu will not clear.
Business / PBX numbers: the published customer number may never hit the iPhone. Changing Call Forwarding on a personal handset will not move a Twilio, RingCentral, or PRI DID. Change divert rules in that admin console instead, then keep the iPhone as a personal overflow only if you intend that.
International travel: some carriers disable handset forward while roaming or charge the divert leg as two calls (inbound to you, outbound to destination). Check the roaming FAQ before you rely on forward for a multi-week trip; a temporary cloud number may be cheaper and clearer.
Related handoff paths
If the job is moving a live answered call on a desk phone, that is not Call Forwarding. Use your PBX attended-transfer feature or the sister office-phone transfer guide on this site.
Android fleet runbooks should not paste iOS screenshots. Keep a platform-specific pass/fail row and point techs at the Android forwarding guide on this site.
Choosing a destination number for overflow (mobile vs IVR vs answering service): agree with finance and ops what rings after hours before you publish the DID on the website.
FAQ
Where did Settings → Phone go?
On current iOS builds the Phone app settings sit one level deeper under Apps. Screenshots that jump straight from Settings into Phone are usually from older iOS.
Can I forward only when I do not answer?
That behavior is a carrier feature (busy / unanswered divert), not the all-calls toggle in the Phone settings screen. Ask the carrier which codes they still honor.
Why does Apple warn about some call-forwarding links?
Random texts or emails that urge a divert change are often phishing. Open Settings yourself; do not follow unsolicited deep links.
Is this the same as a mid-call handoff?
No. The Phone settings switch sends new ringing calls elsewhere. Once you have already answered, moving that conversation is a transfer workflow (iPhone call transfer).