Key Takeaways
- Scenario 1940 is a workspace-transfer confirm inbox: inbound YES completes the handoff — never SMS the transfer token. Not export dump, SAML ACS, or seat-revoke.
- A YES that never lands is a stuck owner and a workspace nobody can bill.
- Do not SMS the token, the billing email, or the new owner hash. Short confirm + ticket link.
- Console OTP stays on another device.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free: 1 device / 300 SMS lifetime / 300 contacts. Developer: 25,000 SMS per year.
Android SMS gateway scenario 1940 is an ownership desk. Outbound asks “transfer workspace? Reply YES.” Inbound YES flips the owner. Export dumps and SAML ACS codes are the wrong list.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Two-way inbox · Developer Center. GSMA.
Transfer, not export
One outbound, one inbound match. Map the reply to the transfer ticket, not a ZIP dump.
If YES arrived and you had already emailed the token, you handed the workspace to whoever held the SMS.
YES vs portal OTP
| Lane | Body | Inbox use | Device |
|---|---|---|---|
| Confirm | YES / NO | Owner flip | Inbox modem |
| Console OTP | Digits | Auth | Dedicated |
| Transfer token | Do not SMS | — | — |
Caps: 2 / 5 / 15.
Never SMS the token
Signed console only. Inbox. REST: PHP, C#. MCP wraps REST.
No workspace ids
Short confirm. Ticket id in the webhook, not the body.
Devices and airtime
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free: 300 lifetime. Developer: 25,000 SMS per year. Pricing.
Inbox desk
Doze exempt for inbound. Doze · Setup.
Transfer ids
Log ticket + inbound, not the token in chat. Rotate keys. Not a CodeCanyon SaaS pack.
Inbox or ticket
If you will not parse YES, do not start the transfer over SMS.
Checklist
- YES matcher with expiry.
- No token in templates.
- OTP on another device.
- Webhook signatures.
- Inbox modem charging.
Next steps
Send a staff transfer; prove YES flips owner and NO does not leak a token. Downloads · Docs.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- two-way SMS inboxReplies on your SIM
- OTP and 2FA SMS on AndroidAuthentication flows
- SMS webhook integrationInbound and status events
- SMS auto-reply and STOP keywordsOpt-out and keywords
