Key Takeaways
- Scenario 212 is GitHub Actions prod APPROVE vs HOLD at 21:15 — not Snowflake RESUME, Terraform APPLY, PCI QSA-IN, DNS CUT, or secrets ROTATE.
- A YES that never lands is a workflow still waiting and a change window that already opened.
- 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 lifecycle drip until APPROVE replies drain.
- Canary the ops SIM at 20:55, not at last night’s nudge job.
Summary
Scenario 212 is GitHub Actions prod intake: outbound APPROVE, inbound APPROVE or HOLD on the same run_id, lifecycle drip held until replies land. 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 the workflow is green and HOLD never parsed, you opened a change window. You did not get consent.
Not a CodeCanyon “SaaS inbox” pack. Device meters apply — Twilio vs Android SMS gateway.
Key takeaways
- Scenario 212 is GitHub Actions prod APPROVE vs HOLD at 21:15 — not Snowflake RESUME, Terraform APPLY, PCI QSA-IN, DNS CUT, or secrets ROTATE.
- A YES that never lands is a workflow still waiting and a change window that already opened.
- 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 lifecycle drip until APPROVE replies drain.
- Canary the ops SIM at 20:55, not at last night’s nudge job.
Related reading
two-way SMS inbox, how an Android SMS gateway works, security and trust, GitHub reviewing deployments.
Context
Deploy window is 21:15. On-call needs a delivered prompt by 21:05. Growth still wants a drip CSV.
Free (300 SMS lifetime) is a rehearsal tenant. Developer is 25,000 SMS per year.
Core scenario guidance
21:15 is APPROVE/HOLD, not Terraform APPLY or Snowflake RESUME. Timezone is on-call, not the vendor HQ.
Actions inbox roles
| Role | When | Typical fail |
|---|---|---|
| APPROVE prompt | On-call local, before deploy | Phone in a locked cage after night shift |
| APPROVE / HOLD parse | Same run_id same night | Treated as STOP on the drip lane |
| Staff OTP | Transactional, own pool | Dumped onto the deploy radio |
| Lifecycle drip | Held until last APPROVE DLR | Released at 20:40 into ops SMS |
Cost and ownership
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. The on-call spare is a billed device. Unparsed HOLD retries burn airtime.
Name a 20:30–00:00 on-call for deploy nights, not only weekday growth.
Operations
20:55 canary. Abort: hold drip, keep staff OTP, skip a second “all admins” blast. Do not treat HOLD as STOP.
Security and compliance
Short tokens. No workflow YAML in SMS. Authenticate inbox webhooks. Drip lists are promotional.
Decision guide
Ship when 20:55 canary parses APPROVE/HOLD and DLR is watched. Delay if the phone sleeps in the cage. If handsets are forbidden, CPaaS for staff OTP.
Checklist
- Ops SIM paired before 20:30.
- 20:55 canary.
- Inbox webhook live.
- Staff OTP isolated.
- Drip held.
- Airtime before 20:30.
- Battery exemptions.
- On-call locale.
- Deploy-night owner named.
- Device cap includes spare.
Next steps
Review device and SMS volume pricing, device setup, SMS API documentation.
Deep dive: production hardening
Nightly OEM killers are an outage at 21:05. Watch inbound parse, not only outbound 200s.
Deep dive: scaling and failure modes
Multi-region deploy weeks add devices before inventing a hidden unlimited-handset SKU. Raise OEM ceilings; fair-use remains.
Deep dive: integration discipline
Idempotency on run_id + kind (prompt|approve|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.
20:55 APPROVE drill
Canary. Prompt a staff SIM. Confirm APPROVE parses. Hold drip during the wave.
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
