Key Takeaways
- Scenario 12 is pickleball court OTP at 14:40 — not mini-golf 16:20, go-kart 15:00, trampoline 16:40, ice-rink 18:10, wax T-30, brow-tint T-25, or microblading T-80.
- A 14:40 gate PIN that waits behind a “we have a court” 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 court OTPs drain.
- Canary the desk SIM at 14:20, not at last night’s booking job.
Summary
Scenario 12 is a pickleball pack: court PIN at 14:40, waiver codes after, waitlist 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 90-row “we have a court” file that starts at 14:10 will make the 14:40 gate code look like the radio is dead.
Not a CodeCanyon “salon OTP” pack. Device meters apply — Twilio vs Android SMS gateway.
Key takeaways
- Scenario 12 is pickleball court OTP at 14:40 — not mini-golf 16:20, go-kart 15:00, trampoline 16:40, ice-rink 18:10, wax T-30, brow-tint T-25, or microblading T-80.
- A 14:40 gate PIN that waits behind a “we have a court” 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 court OTPs drain.
- Canary the desk SIM at 14:20, 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 14:50. Players queue at the gate from 14:25. Merch still wants a waitlist CSV.
Free (300 SMS lifetime) is a rehearsal club. Developer is 25,000 SMS per year.
Core scenario guidance
14:40 is pickleball OTP, not mini-golf 16:20. Timezone is the club, not the franchise HQ.
Court OTP lanes
| Lane | When | Typical fail |
|---|---|---|
| 14:40 court PIN | Club local, before first heat | Phone in a locked paddle cage after lunch |
| Waiver / guest code | After PIN depth is low | Merged into the merch blast |
| Staff OTP | Transactional, own pool | Dumped onto the court radio |
| Waitlist / merch | Held until last court DLR | Released at 14:10 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 14:00–17:00 on-call for court waves, not only weekday admin.
Operations
14:20 canary. Abort: hold waitlist, keep staff OTP, skip a second “all courts” 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 14:20 canary is green and OTP depth drains before merch. Delay if the desk phone sleeps in the paddle cage. If handsets are forbidden, CPaaS for staff OTP.
Checklist
- Desk SIM paired through lunch.
- 14:20 canary.
- Spare live before 14:40.
- Staff OTP isolated.
- Waitlist held.
- Airtime before 14:00.
- Battery exemptions.
- Club locale.
- Court-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 lunch lock on USB is an outage at 14:40. 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|waiver). 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.
14:20 pickleball drill
Canary. Fire one court 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
