ZROtext owner workspace
Your phones and messages
Follow your phones and message activity, with the next action close at hand.
Sign in
Use your verified owner account to manage gateway devices.
Need to register or verify your email? Open account setup.
Forgot your password?
Request a one-hour reset code for your owner account. We will send instructions if that address is registered.
Enter a reset token
Your next step
Continue setup
Checking saved progress with this server…
Continue setupOn your phone
Start the connection
Phone approved. Choose the SIM and required permissions in the app, then press Start connection.
The app retrieves its approved device identity. There is no device ID or stream address to enter.
Phone connected · Line approval recorded
Setup progress is confirmed by this server. Carrier testing remains a separate, deliberate action.
Phones
Updates and status details
Fleet observations are loading.
While this tab is visible, device and message updates arrive over a live same-origin event stream and lists refresh within a few seconds of a server-side change. If that stream cannot connect, updates fall back to a 15-second snapshot refresh. A list pauses while you browse older entries, focus a row, or open message events. Use Refresh to return to its latest entries.
Approval permits a phone to connect. A displayed authenticated socket lease is a server observation that can lag a dropped connection by up to 90 seconds. It does not prove SMS permission, SIM service, or dispatch readiness. Check the gateway app on the phone before a controlled test.
Pending counts accepted, queued and claimed messages; in flight counts submitting and submitted messages. These server states can include work awaiting expiry reconciliation. Counts stop at 1,000+ per category. Check the snapshot time and message timeline for unknown or final outcomes.
Android reports describe selected SIM availability, SMS permission and airplane mode at the shown receipt time. Fresh reports explain local blockers to check on the phone. Saved reports become historical after the freshness window, even with automatic refresh paused. No reported blockers does not prove carrier readiness or delivery. Check the message timeline for actual callback evidence.
Message summary
Loading authoritative metadata…
Submitted today (UTC)
Loading…
Waiting or claimed
Loading…
Submitting / awaiting receipt
Loading…
Summary scope and definitions
Submitted today counts complete sent-callback evidence received by the writer; delivery is separate. Waiting counts accepted, queued and claimed states. Claimed work may already hold a grant; this is not ungranted queue depth. In progress counts submitting and submitted states. Counts cover the selected scope and UTC day.
Recent activity
View activity- Loading recent writer metadata…
Line tools
Use the guided flow to add a phone, or manage existing browser approval keys and SMS lines.
Manage SMS lines and approval keysMessage activity
Message history shows server states and device events from controlled tests. A delivery callback does not prove the recipient read a message.
Outbound writer metadata only. Recipient values are unavailable in this feed. All/Inbound filters require a scoped unified feed and are unavailable; inbound UUID history and webhook replay remain below. Sealed conversation content is not available here.
Account settings
Authenticator and recovery · Export or erase account data · Subscription setup
Manage your authenticator and recovery codes on the account setup page.
Create your SMS approval key and activate phone lines on the SMS lines page.
Invite device-status observers for your team on the team seats page.
Change password
Changing or resetting your password signs out every session and revokes your API keys. Sign in again and reissue keys used by integrations.
Active sessions
Review up to 50 active sessions. Revoking other sessions keeps this one active. Your API keys keep working unless you also tick the box below; a key minted from a stolen session cannot be told apart from your own, so only tick it if you suspect misuse.
Connect a phone
Pair a phone
Keep this page and the gateway app open together. Create a five-minute, one-use pairing code, then use it on the phone. You will compare both devices before approving access.
- Name this phone. Choose a name you will recognize in your device list.
- Connect in the gateway app. Scan in a supported gateway app, or enter the details manually.
- Compare and approve. Check the comparison code and fingerprint on your phone against this page.
Scan with your phone
Scan in a supported gateway app, or enter the details manually.
Enter pairing details manually
Use these three values in the gateway app. Check that the server address is the one you intended to use.
Keep the code and token private. Do not share a screenshot or put the token in a link. If you leave this page, the one-use token is cleared. Return to Continue setup to check the saved attempt before replacing it.
Need help?
If progress cannot be checked, contact your operator with reference PHONE-SETUP. Keep pairing tokens private.
After pairing: permissions, SIM and connection
- On the phone, review the gateway app's permission requests. If you denied a required permission, open the app's Android settings and choose whether to grant it; then return to the app.
- In the gateway app, select the active physical SIM you intend to use. Check airplane mode and network service on the phone.
- Open SMS lines, create the browser approval key and review the phone's declaration before activating a line.
- Check device status. Connected status alone does not prove that the phone can send or that a message was delivered.
Pairing adds a phone to this account. Permission choices, line approval and consent are separate steps; pairing does not authorize a real SMS test.
Opt-out review
Record your decision after reviewing a possible SMS withdrawal through your consent process. Both decisions leave the recipient blocked; neither establishes consent or resumes sending. Decisions are permanent. Only recipient metadata is shown, never SMS content.
Requests received elsewhere
Record an opt-out received by phone, email or another channel. This blocks new messages and cancels queued messages before they are authorized for sending. Sending already in progress may still finish.
API keys
Create a key for the current pilot API. messages:read reads message status; messages:send is limited to the private synthetic alpha route and its account and recipient allowlists. Other product APIs do not accept these keys yet.
Copy this key now. It is shown only once and cannot be recovered after you leave this page.
Inbound event history
Enter a message UUID you want to inspect. This pilot view shows event metadata only; it does not show SMS content or phone numbers.
Selected message:
Webhook delivery history
Choose an endpoint to inspect delivery and attempt metadata. This view does not show callback URLs, secrets, payloads or response bodies.
Line setup · step 1
Protect line approval
Keep access safe
Add an authenticator and save recovery codes before creating the browser's line approval key.
Add this secret to your authenticator. It is cleared when you leave this page.
Authenticator import details
Save these recovery codes somewhere you can reach if you lose your phone. Each works once.
Why this security step?
Line activations are approved with a signing key that stays in this browser. The server stores only its public key. Clearing this browser's site data removes the key; revoke it and create a new one if that happens.
If you need an authenticator or recovery code, finish account security setup first. Keep this browser available while you review and approve the phone's declaration.
Your lines
Review existing lines before creating another. A line identifies the SIM declaration you approved; it does not show the SIM's phone number.
Line setup · step 2
Approve this phone's SIM
Review the SIM reported by this phone. Approval does not send an SMS.
The phone must be connected and have a selected, active SIM. It signs a declaration; you check it and approve with your key. Selected SIM setup supports physical SIMs and eSIMs on Android 13 or later with a compatible gateway and server. Nothing here sends an SMS.
- Choose your paired phone. If it is missing, return to your phones and check its connection.
- The line identity is filled for you. Choose the supported phone setup, then review its declaration.
- Review the selected SIM and active subscription count before approving. If the phone reports a different SIM, correct its selection in the gateway app and request again.
Check the phone's declaration
- Selected subscription
- Active subscriptions
- Selected SIM type
Technical declaration
Android API level: . The selected SIM declaration is checked against this phone, line and current ceremony.
After activation, check phone status and Security & sessions. A connected phone alone does not prove carrier readiness or delivery.