Android SMS Gateway Scenario 896: SaaS onboarding two-way inbox in practice

Summary

Scenario 896 is the domain desk. One outbound transfer ask, YES or HOLD on the same thread, then push or park.Service pricing is based on device count and total SMS sent through the gateway. You need a working Android phone with a SIM and SMS credit from your mobile operator. Operator message costs are yours—we do not sell carrier SMS balance.

If changelog leaves at T-0 and YES is still inbound, you did not transfer. You announced a cutover nobody owned.

Not a CodeCanyon “SaaS SMS” pack. Device meters apply — Twilio vs Android SMS gateway.

Key takeaways

• Scenario 896 is domain-transfer YES vs HOLD on a two-way inbox — not HELP, CANCEL vs STOP, seat YES, card UPDATE, lockout, go-live, PAY/PLAN, key rotate, export READY, SSO DNS-OK, incident ACK/PAGE, sandbox ACCEPT, webhook replay, or SCIM bind.
• Reset OTP stays off the transfer inbox SIM.
• Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 300 SMS lifetime, 1 device. Developer is 25,000 SMS per year.
• Starter is 2 devices; the DNS spare still counts.
• YES after TTL must not push the nameservers; a late YES must not double-transfer.
• Changelog waits until the transfer window closes.

Related reading

two-way SMS, OTP and 2FA SMS, how an Android SMS gateway works, ICANN transfer policy.

Context

Registrars reply from a phone. YES must push once. Reset OTP still fires on a separate pool.

Free (300 SMS lifetime) is a rehearsal tenant. Developer is 25,000 SMS per year.

Core scenario guidance

One live ask per transfer_id. Late YES after TTL is a no-op plus a status text.

Hold changelog until the window closes. Locale is the admin’s billed timezone.

Domain inbox roles

Cost and ownership

Priced by devices and SMS send volume. You use your own phone and operator SMS credit. The DNS spare is a billed device. Asks burn airtime.

Name a weekday 14:00–18:00 hop owner for cutovers, not only marketing.

Operations

15:00 canary both radios after OEM updates. Abort: HOLD parks the transfer, keep OTP, skip changelog. Do not “TRANSFER all domains.”

Security and compliance

Authenticate inbound webhooks. No auth codes in SMS. Map YES only from the asked MSISDN.

Decision guide

Ship when 15:00 canary is green and late YES is a no-op. Delay if phones live in a closet after 17:00. If handsets are forbidden, CPaaS for OTP.

Checklist

• Primary + DNS spare paired.
• 15:00 canary.
• One ask per transfer_id.
• Late YES is no-op.
• YES pushes once.
• OTP isolated.
• Changelog held.
• Airtime before the window.
• Battery exemptions both OEMs.
• Device cap includes spare.

Next steps

Review device and SMS volume pricing, device setup, SMS API documentation.

Deep dive: production hardening

Cleaners pulling USB at lunch is an outage. No auto-reply echoing EPP codes. Watch inbound + DLR.

Deep dive: scaling and failure modes

Cutover weeks add devices before inventing a hidden unlimited-handset SKU. Raise OEM ceilings; fair-use remains.

Deep dive: integration discipline

Idempotency on transfer_id + kind (ask|yes|hold). MCP is a REST wrapper — live fields in Developer Center.

Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

15:20 transfer drill

Canary both radios. Reply YES; confirm one push. Reply YES after TTL; confirm no second transfer.