Key Takeaways
- Scenario 1003 is prix-fixe / tasting fire-time auto-reply — not staff-meal MEAL, late-night NIGHT, kids-party CAKE, last-call LAST, brunch SEAT, allergy NUTOK, food-truck HERE, private dining, wine flights, patio weather, bakery tickets, crew COVER, loyalty POINTS, delivery DELAY, catering, or ghost brands.
- A “course 3 fires in 8 minutes — reply FIRE” text is kitchen logistics. A “join the tasting club” list is marketing. Split SIMs.
- FIRE / HOLD / SKIP keywords belong on the tasting Android. Never bot the reservation-app OTP phone.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free is 1 / 300 / 300. Developer is 25,000 SMS per year.
- Cap “still seated?” loops. Each outbound spends operator credit.
- REST inbound fields live in Developer Center — not a CodeCanyon tasting plugin. MCP, if you use it, is only a REST wrapper.
Summary
Scenario 1003 is prix-fixe tasting fire-time auto-reply. The pass owns the course clock. The Android texts FIRE when course 3 is about to leave. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If STOP on “course 3 fires in 8 minutes” also kills the tasting-club list because you stored one dump, you will lose regulars who still book the menu.
Prix-fixe fire time
Bind FIRE to tables still on the tasting. Auto-reply and STOP · restaurant templates. Inbound: Developer Center. Industry context: GSMA.
Keyword map
| Keyword | Number | Action | Do not |
|---|---|---|---|
| FIRE / HOLD / SKIP | Tasting Android | Patch the course clock | Treat SKIP as tasting-club STOP |
| STOP | Tasting-club promo | Persist unsubscribe | Kill tonight’s course texts unless asked |
| (any) | Reservations OTP | None | Attach a FIRE bot |
FIRE is not STOP
Expire FIRE after the last course. Two-way SMS. Doze will sit on FIRE until the pass is already plated. Doze.
Cost
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free: 1 device, 300 SMS lifetime, 300 contacts. Developer: 25,000 SMS per year. Paid plans uncap platform volume; devices still meter. Pricing.
Ops
Charge the tasting phone at the pass. Failover · setup. Cap pings per table.
Security
A tasting booking is not tasting-club consent. Trust Center · OTP.
Checklist
- Course vs promo vs OTP labeled.
- FIRE expiry after last course.
- STOP scopes documented.
- Ping cap per table.
- Airtime owner named.
Next steps
Transactional SMS · SMS API documentation.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS auto-reply and STOP keywordsOpt-out and keywords
- two-way SMS inboxReplies on your SIM
- SMS gateway use casesReal-world jobs
- SMS API documentationLive endpoint reference
