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

Summary

Scenario 1436 is a feature-flag cutover: prompt SHIP or HOLD at 16:00, parse only those verbs, launch CSV held until replies drain. 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 traffic already flipped and the on-call texted HOLD into a full queue, you did not pause. You split-brained the flag.

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

Key takeaways

• Scenario 1436 is feature-flag SHIP vs HOLD — not HELP, CANCEL/STOP, teammate YES, card UPDATE, lockout, go-live, PAY/PLAN, API-key, export, SSO DNS, incident ACK, sandbox, webhook replay, SCIM, domain, IP allowlist, maintenance, data-residency, SAML ROTATE, DSR START, MFA RESET, pentest YES, or TAX-ID CONFIRM.
• A 16:00 flag that reads HOLD after traffic already flipped is an outage, not a cautious ops choice.
• 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 on-call spare still counts.
• Hold product-launch CSV until SHIP/HOLD drains.
• Canary the inbox SIM at 15:50, not at Monday’s weekly digest.

Related reading

two-way SMS inbox, OTP and 2FA SMS, how an Android SMS gateway works, Martin Fowler on feature toggles.

Context

Canary traffic is 5% at 15:40. Full ship is 16:05. Growth still wants a changelog CSV.

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

Core scenario guidance

16:00 is SHIP/HOLD, not go-live YES. Timezone is on-call, not the vendor HQ.

Flag inbox roles

Cost and ownership

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

Name a 15:30–17:30 on-call for flag afternoons, not only weekday support.

Operations

15:50 canary. Abort: hold launch CSV, keep login OTP, skip a second “all admins” blast. Do not “resend tenants.”

Security and compliance

Short verbs. No flag keys in SMS. Authenticate webhook hooks. Launch lists are promotional.

Decision guide

Ship when 15:50 canary is green and SHIP/HOLD parse is exact. Delay if the inbox phone sleeps after 15:00. If handsets are forbidden, CPaaS for login OTP.

Checklist

• Inbox SIM paired overnight.
• 15:50 canary.
• SHIP/HOLD only — no OK.
• Login OTP isolated.
• Launch CSV held.
• Airtime before 15:30.
• Battery exemptions.
• On-call locale.
• Flag-afternoon on-call named.
• Device cap includes spare.

Next steps

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

Deep dive: production hardening

Facilities killing USB at 15:10 is an outage at 16:00. Watch inbound keywords, not flag-service 200s.

Deep dive: scaling and failure modes

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

Deep dive: integration discipline

Idempotency on flag_id + env + kind (prompt|ship|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:50 flag drill

Canary. Send HOLD from a staff SIM; confirm traffic stays at 5%. Hold launch CSV during the wave.