I work with DuoPlus, so read the second entry with that in mind. I'm a growth marketing person, not a QA lead, but I end up walking through our own app's signup screen more often than I'd like. Every time a release touches the phone step, somebody asks "did the code actually arrive, and did the screen behave when it did?" This list is the stuff I've used or looked at for answering that. Ranked for one job only: testing an app you own.

I checked every vendor detail below on the vendor's own site or docs today. Where a page didn't say something, I left it out. No prices, because they change and I'd rather you look.

1. Firebase fictional phone numbers

If your app uses Firebase Authentication, start here. It's free in the sense that matters: the docs say you can set up fictional phone numbers in the Firebase console, test without sending a real SMS, without eating your quota, and run the same number again and again without getting throttled.

Good for: unit-ish and integration tests of the auth logic.
Not good for: knowing whether a real text reaches a real handset. Nothing is sent, which is the whole point, and also the gap.

2. DuoPlus cloud phone plus cloud number

https://www.duoplus.net

This one sits near the top for a different reason. Firebase tests your code; this tests the experience. A DuoPlus cloud phone is a real ARM Android device in the cloud (Android 10, 11, 12 and 15), each one its own isolated device environment, and you open it in a browser, the desktop client or the mobile app. The cloud phone has no SIM, so for the SMS step I use a DuoPlus cloud number that receives the verification text. I type the code into our app on the actual device and watch what the screen does.

Where it fits best, in my experience:

  • Regional checks. You can pick from local environments in 150+ countries/regions, and set the proxy/region per device. Our signup copy and number formatting differ by market, and this is where those bugs show up.
  • Keeping a long-term fixed test device. One independent cloud phone per test scenario, separate data and login state, and it stays put. I don't rebuild a "logged-out, fresh install" phone every sprint.
  • Handover. When I'm done, I share the device with a developer in one click and they pick it up already in the state I left it, no re-login.
  • Bulk work: install, uninstall and launch our build across a batch of devices at once. There's an API and root if your test cases need either. Billing is per minute, which suits twenty-minute check sessions.

Honest drawbacks: it's Android only, so your iOS signup flow needs something else. And it's a manual-ish tool at heart. You can script it through the API, but if you just want an assertion in CI that a code arrived, a pure SMS testing API (below) is less setup.

If you want to try it, this is our invite link: https://www.duoplus.net/share/market

3. Mailosaur SMS testing

Mailosaur is the one I'd hand to a QA engineer who lives in Playwright. Their page pitches end-to-end SMS testing for OTP and MFA flows, an API that works with Cypress, Playwright and Selenium, and dedicated numbers across supported regions, without phones or live SIMs. There are team permissions too.

Good for: automated tests that assert the message content and timing.
Weak spot for me: it tells you the SMS arrived; it doesn't show you the Android screen your user sees.

4. Twilio test credentials

Not a test-number product so much as a safety net while you build. Twilio's test credentials come with "magic" inputs. +15005550006 behaves as a valid, available number; +15005550009 behaves as one that can't receive SMS. Handy for checking your error handling without sending anything.

Good for: backend code paths and failure cases.
Not good for: end-to-end. It's simulated.

5. Telnyx phone numbers

If your team wants real numbers you control through an API, Telnyx is worth a look. You search, reserve and buy numbers through their REST APIs and SDKs; they say they hold carrier licenses in 30+ countries, and you can send text messages from the portal or API.

Feels like: infrastructure. Great if you have someone who enjoys telecom config. Overkill if you only need a code once a week.

6. Plivo virtual numbers

Similar territory. Plivo sells local, mobile and toll-free numbers in more than 50 countries through API and console, and their mobile numbers send and receive SMS and MMS.

Good for: teams already on Plivo for sending, who want a receiving number in the same account.

How I'd actually combine them

Fictional numbers or magic numbers in CI. A real receiving number for the scheduled end-to-end run. And once per release, someone (often me, honestly) opens a real Android device in the target market and walks through the screen with a real code. That last part is where DuoPlus earns its slot on my list.

One rule I keep: only point any of this at apps you own or are paid to test. That's what it's for.