Key Takeaways
- Scenario 763 is pour-over / coffee-bar wait auto-reply — not oyster SHELL, dry-age AGE, hotel breakfast BRK, prix-fixe FIRE, 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 “pour-over ready in 6 minutes — reply POUR” text is bar logistics. A “join the coffee club” list is marketing. Split SIMs.
- POUR / LATE / SKIP keywords belong on the bar Android. Never bot the POS 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 coming?” loops. Each outbound spends operator credit.
- REST inbound fields live in Developer Center — not a CodeCanyon coffee plugin. MCP, if you use it, is only a REST wrapper.
Summary
Scenario 763 is pour-over coffee-bar wait auto-reply. The bar owns the bloom clock. The Android texts POUR when the cup is ready. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
If STOP on “pour-over ready in 6 minutes” also kills the coffee-club list because you stored one dump, you will lose regulars who still need the wait text.
Pour-over wait
Bind POUR to tickets still in bloom. Auto-reply and STOP · restaurant templates. Inbound: Developer Center. Industry context: GSMA.
Keyword map
| Keyword | Number | Action | Do not |
|---|---|---|---|
| POUR / LATE / SKIP | Bar Android | Patch the wait | Treat SKIP as coffee-club STOP |
| STOP | Coffee-club promo | Persist unsubscribe | Kill this cup’s texts unless asked |
| (any) | POS OTP | None | Attach a POUR bot |
POUR is not STOP
Expire POUR after pickup. Two-way SMS. Doze will sit on POUR until the cup is already 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 bar phone at the station. Failover · setup. Cap pings per ticket.
Security
A ticket name is not coffee-club consent. Trust Center · OTP.
Checklist
- Wait vs promo vs OTP labeled.
- POUR expiry after pickup.
- STOP scopes documented.
- Ping cap per ticket.
- 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
