If you searched “how to receive text messages from another phone number,” you’re probably trying to solve something practical.
Maybe you have a work number you don’t want to carry on a second phone. Maybe you’re switching devices and don’t want to miss verification texts. Or maybe you have an older number tied to important accounts and you’re trying to keep access while you transition.
Here’s the key: this topic sounds simple, but it can mean a few different things. Once you pick the right scenario, the solution becomes much easier.
Most people mean one of these:
-
You want to receive texts for the same phone number on more than one device.
Example: your main number should ring and text on your phone and your smartwatch/tablet.
-
You want to receive texts sent to a second number you own.
Example: you have a work number, old number, or business number and want to see those texts on your main phone.
-
You want to receive texts without having the original phone nearby.
Example: you left your phone at home but still want your number’s texts on another device.
-
You’re trying to receive texts for a number you don’t own or manage.
If that’s the goal, pause. Receiving someone else’s messages without permission is unethical and may be illegal. The methods below are for numbers you own or manage with consent (like a work line or a family device under clear rules).
Now let’s walk through the most reliable methods.
If you want the most reliable setup, match the method to your real goal:
- Same number on multiple devices → Carrier multi-device service (Method 1)
- Receive texts for a second number you own on one phone → Dual SIM/eSIM (Method 4)
- Receive iPhone SMS on iPad/Mac → Apple Text Message Forwarding (Method 2)
- Access a secondary number from anywhere → Cloud inbox / virtual number (Method 3)
- Temporary transition / copying messages → Forward from a phone you control (Method 5)
If your goal is to receive texts for the same number on multiple devices, your carrier is often the most reliable path because it’s built for that exact use case.
Examples (U.S. carriers, names vary):
- T-Mobile DIGITS
- Verizon Number Share
- AT&T NumberSync
These services are meant to let you use one mobile number across multiple compatible devices, depending on the plan and device type.
- Your main number can appear across connected devices
- Calls and texts may work even when your phone isn’t right next to you (depending on setup)
- Eligible devices and plans vary
- Short codes / OTP verification texts can behave differently (more on that below)
- Check your carrier account for multi-device / number sharing options
- Link the second device (or carrier app/web client) to your main line
- Test a normal SMS, then test a short-code/OTP if you rely on those
If you’re using a smartwatch or tablet from the same carrier ecosystem, this method is often the cleanest.
If you don’t actually need another phone number involved—and you just want your iPhone’s SMS to appear on other Apple devices—Apple’s Text Message Forwarding is usually the easiest option.
- Lets your iPhone forward SMS/MMS (and in many setups, RCS) to devices like a Mac or iPad signed into the same Apple account
- It doesn’t forward texts to a different phone number
- It’s designed for your Apple device ecosystem
- On your iPhone, go to Settings
- Tap Messages
- Tap Text Message Forwarding
- Enable the devices you want to receive texts on (Mac/iPad)
If you’re fully Apple-based, this is a great “no extra service” option.
Sometimes you don’t need to “share” a carrier number at all. You just need a number whose texts you can read from anywhere (phone, tablet, laptop).
A common example is a cloud inbox like Google Voice (availability varies by region):
- You receive texts inside the app or on the web
- Many services expect you to read texts in the app/web rather than forwarding inbound texts to another phone number
- A secondary number you want accessible everywhere
- A work/project number where a cloud inbox is more convenient than a second SIM
- Some services reject VoIP numbers for verification
- Short-code messages can be inconsistent depending on the platform and sender
If your main goal is “this second number should be accessible anywhere,” a cloud inbox can be a strong fit.
If you own the second number and want to receive its texts on your main phone, the most reliable solution is often the most direct one:
Put that number on your phone as a second line.
If your phone supports Dual SIM or eSIM, you may be able to:
- Keep your personal number as your primary line
- Add your work/old number as a second line
- Receive texts to both numbers normally (no forwarding required)
- No syncing delays
- No forwarding app to break in the background
- Texts arrive like normal because they are normal
- Your device must support dual SIM/eSIM
- Your carrier must support eSIM for your plan
- You may need to choose which line is used for data and which line is used for outbound texts
If reliability matters most, this is often better than any forwarding workaround.
If you still have the original phone that receives texts, you can sometimes set up auto-forwarding from that device to another destination.
This can help if:
- You’re transitioning off an old phone
- You want messages copied to email
- You’re temporarily using a spare device
But it’s fragile because:
- The original phone must stay on, connected, and allowed to run the forwarding process
- Battery optimization can break forwarding on Android
- Some message types (like short codes) may not forward cleanly
If you choose this method, keep expectations realistic and test it regularly.
If you’re doing this mainly for verification codes, here’s the honest truth:
OTP and short-code messages can behave differently across methods.
Common issues:
- Codes show up on the primary device but not the secondary
- Messages arrive delayed
- Messages appear in the source inbox but don’t forward outward
If OTP reliability is your top priority, the most stable options are:
- Dual SIM/eSIM (Method 4)
- Carrier multi-device services (Method 1), depending on carrier and setup
- Reading messages directly inside the platform that owns the number (cloud inbox apps)
Sometimes. It usually requires a carrier multi-device feature or a supported ecosystem setup. In many cases, it’s easier to use a carrier service or move the number to dual SIM/eSIM.
Some forwarding setups exist, but many platforms don’t support forwarding inbound texts to a linked number anymore. It’s often more reliable to receive texts directly through carrier multi-device features, dual SIM/eSIM, or a cloud inbox.
Yes. Text Message Forwarding is designed for that. It’s a same-account setup rather than “forward to another phone number.”
If you no longer control the number or SIM, the safest path is account recovery: update your 2FA number, contact your carrier, and move critical accounts off the old number. Avoid trying to “receive texts” for a number you don’t control.
Sometimes parents search this topic because they’re trying to keep up with safety concerns and important messages on a child’s device.
If your goal is family safety, do it transparently, with clear consent and rules. A parental control solution like NexSpy can help parents build safer routines on a managed device, rather than relying on unreliable forwarding workarounds.
If you want the most reliable approach, match the method to your real goal:
- Same number on multiple devices → Use a carrier multi-device feature
- Receive texts for a second number you own → Use dual SIM/eSIM if possible, or a cloud inbox
- Receive iPhone SMS on iPad/Mac → Use Apple Text Message Forwarding
- Forwarding from a phone you control → Useful for transitions, but test it and expect limitations