Key Takeaways
- Scenario 432 is pool-hall table OTP at 17:15 — not darts 19:40, snooker 15:05, escape-room 11:20, or table-tennis 18:20.
- A 17:15 door PIN that waits behind a “league merch” CSV looks like the keypad is dead.
- 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 desk spare still counts.
- Hold gift-card and waitlist until table OTPs drain.
- Canary the desk SIM at 16:55, not at last night’s booking job.
Summary
Scenario 432 is a pool-hall pack: table PIN at 17:15, guest codes after, league merch held until OTPs 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.
A 20-row “league night” file that starts at 16:40 will make the 17:15 door code look like the radio is dead.
Not a CodeCanyon “salon OTP” pack. Device meters apply — Twilio vs Android SMS gateway.
Key takeaways
- Scenario 432 is pool-hall table OTP at 17:15 — not darts 19:40, snooker 15:05, escape-room 11:20, or table-tennis 18:20.
- A 17:15 door PIN that waits behind a “league merch” CSV looks like the keypad is dead.
- 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 desk spare still counts.
- Hold gift-card and waitlist until table OTPs drain.
- Canary the desk SIM at 16:55, not at last night’s booking job.
Related reading
OTP and 2FA SMS on Android, scheduled SMS campaigns, how an Android SMS gateway works, ICO PECR marketing rules.
Context
First frame is 17:25. Players queue at the door from 17:00. Retail still wants a waitlist CSV.
Free (300 SMS lifetime) is a rehearsal hall. Developer is 25,000 SMS per year.
Core scenario guidance
17:15 is pool-hall OTP, not darts 19:40 or snooker 15:05. Timezone is the hall, not the franchise HQ.
Pool-hall OTP lanes
| Lane | When | Typical fail |
|---|---|---|
| 17:15 table PIN | Hall local, before first frame | Phone in a locked cue rack after tea |
| Guest / late code | After PIN depth is low | Merged into the merch blast |
| Staff OTP | Transactional, own pool | Dumped onto the table radio |
| Waitlist / merch | Held until last table DLR | Released at 16:40 into auth SMS |
Cost and ownership
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. The desk spare is a billed device. Duplicate PINs burn airtime.
Name a 16:20–20:00 on-call for evening frames, not only weekday admin.
Operations
16:55 canary. Abort: hold waitlist, keep staff OTP, skip a second “all tables” blast. Do not “resend PINs.”
Security and compliance
Short codes. No full booking bodies in shared chat. Waitlist CSV is promotional — STOP still applies.
Decision guide
Ship when 16:55 canary is green and OTP depth drains before merch. Delay if the desk phone sleeps in the cue rack. If handsets are forbidden, CPaaS for staff OTP.
Checklist
- Desk SIM paired through tea.
- 16:55 canary.
- Spare live before 17:15.
- Staff OTP isolated.
- Waitlist held.
- Airtime before 16:20.
- Battery exemptions.
- Hall locale.
- Frame-wave on-call named.
- Device cap includes spare.
Next steps
Review device and SMS volume pricing, device setup, SMS API documentation.
Deep dive: production hardening
A tea lock on USB is an outage at 17:15. Watch DLR, not booking 200s.
Deep dive: scaling and failure modes
Two-site halls add devices before inventing a hidden unlimited-handset SKU. Raise OEM ceilings; fair-use remains.
Deep dive: integration discipline
Idempotency on booking_id + kind (pin|guest). 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.
16:55 pool drill
Canary. Fire one table PIN. Confirm DLR before waitlist CSV. Hold merch during the wave.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- OTP and 2FA SMS on AndroidAuthentication flows
- multi-device and dual SIM routingCapacity and failover
- SMS delivery reports (DLR)Delivery status tracking
- SMS API documentationLive endpoint reference
