SMS & OTP

Sign-up, login, a payment confirmation — many flows stop at a one-time code sent by SMS. A cloud phone has no SIM, so that code never arrives and the test stalls. A SIM phone has a real, live SIM: send your app's code to its number and the text lands in your session, with the verification code already pulled out for you.

Pick a SIM phone

In the device picker, an eligible phone shows a SIM marker. Pick it and start a session as usual — it comes up locked down and ready to receive.

Receive a code

1. Open the Messages panel from the icon at the top-right of the session.
2. The panel shows the phone's own number, with its country code — send your app's OTP or 2FA code to that number.
3. Each text appears as it arrives, newest first. The verification code is detected and shown on its own, with a one-tap Copy button — paste it straight into the app.

Receive-only, by design

The phone can only receive SMS. It can't send texts, can't place calls (incoming calls are turned away automatically), and the SIM carries no mobile data — the phone browses over Wi-Fi. These limits are locked on the device itself and can't be switched off, so the number stays a safe inbox for your test codes and nothing else.

In automated tests

You can read the same code from an Automate script, so OTP and 2FA steps run end-to-end in your suites — not only when someone is watching the screen. The script asks for the session's received messages and reads the code out of them, the same text you would see in the panel. See Automate.

Good to know

• The inbox is wiped at the start and end of every session, so one tester's codes never carry over to the next. Messages are shown to you live and aren't kept after the session ends.
• SIM / OTP runs on a real Android phone with a live SIM.
• The number to send to is always the one shown in the panel — read it there rather than assuming it.