Key Takeaways
- Scenario 192 is table-tennis table OTP at 18:20 — not badminton 19:10, squash 17:45, pickleball 14:40, padel 19:20, or bowling 20:00.
- An 18:20 door PIN that waits behind a “league night” CSV looks like the gateway is down.
- 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 merch and waitlist until table OTPs drain.
- Canary the desk SIM at 18:00, not at last night’s booking job.
Summary
Scenario 192 is a table-tennis pack: table PIN at 18:20, 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 50-row “league night” file that starts at 18:00 will make the 18:20 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 192 is table-tennis table OTP at 18:20 — not badminton 19:10, squash 17:45, pickleball 14:40, padel 19:20, or bowling 20:00.
- An 18:20 door PIN that waits behind a “league night” CSV looks like the gateway is down.
- 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 merch and waitlist until table OTPs drain.
- Canary the desk SIM at 18:00, not at last night’s booking job.
Related reading
OTP and 2FA SMS on Android, scheduled SMS campaigns, how an Android SMS gateway works, Android connectivity docs.
Context
First heat is 18:30. Players queue at the door from 18:05. Merch still wants a waitlist CSV.
Free (300 SMS lifetime) is a rehearsal club. Developer is 25,000 SMS per year.
Core scenario guidance
18:20 is table-tennis OTP, not badminton 19:10 or squash 17:45. Timezone is the club, not the franchise HQ.
Table-tennis OTP lanes
| Lane | When | Typical fail |
|---|---|---|
| 18:20 table PIN | Club local, before first heat | Phone in a locked bat drawer after dinner |
| 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 17:50 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 17:45–21:00 on-call for table waves, not only weekday admin.
Operations
18:00 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 18:00 canary is green and OTP depth drains before merch. Delay if the desk phone sleeps in the bat drawer. If handsets are forbidden, CPaaS for staff OTP.
Checklist
- Desk SIM paired through dinner.
- 18:00 canary.
- Spare live before 18:20.
- Staff OTP isolated.
- Waitlist held.
- Airtime before 17:45.
- Battery exemptions.
- Club locale.
- Table-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 dinner lock on USB is an outage at 18:20. Watch DLR, not booking 200s.
Deep dive: scaling and failure modes
Two-site clubs 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.
18:00 ping-pong 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
