Key Takeaways
- Scenario 1543 is wine-dinner / tasting-seating auto-reply — not patio weather, bakery tickets, crew COVER, loyalty POINTS, delivery DELAY, catering, or ghost brands.
- A “we seated you at flight 2” text is logistics. A “join the cellar club” list is marketing. Split SIMs.
- PAIR / LATE / RELEASE keywords belong on the sommelier 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 on the list?” 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 1543 is wine-dinner and tasting-seating auto-reply. The book owns the flight. The Android texts PAIR when the next pour is ready. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If STOP on “flight 2 is seated” also kills the cellar-club list because you stored one dump, you will lose the guests who still book pairings.
Wine-dinner seating
Bind PAIR to covers booked on the tasting flight only. Auto-reply and STOP · restaurant templates. Inbound: Developer Center. Industry context: GSMA.
Keyword map
| Keyword | Number | Action | Do not |
|---|---|---|---|
| PAIR / LATE / RELEASE | Sommelier Android | Patch the flight | Treat RELEASE as cellar STOP |
| STOP | Cellar-club promo | Persist unsubscribe | Kill tonight’s seating texts unless asked |
| (any) | Reservations OTP | None | Attach a PAIR bot |
PAIR is not STOP
Expire PAIR after service. Two-way SMS. Doze will sit on PAIR until the pour is cold. 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 sommelier phone at the pass. Failover · setup. Cap pings per cover.
Security
A tasting booking is not cellar-club consent. Trust Center · OTP.
Checklist
- Seating vs promo vs OTP labeled.
- PAIR expiry after service.
- STOP scopes documented.
- Ping cap per cover.
- 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
