Key Takeaways
- An oyster ready text is that plate at that bar — not everyone who ever scanned the QR for a happy-hour punch card.
- STOP on the ready purpose must not kill the separate loyalty list.
- Free is 1 device, 300 SMS lifetime, and 300 contacts. Developer is 25,000 SMS per year. Platform price is devices plus send volume.
- POS OTP stays off the bar SIM.
- Idempotency is order-id plus plate-scan — dumped ice reprints the same ticket.
Summary
Scenario 1771 is restaurant auto-reply and STOP for a raw-bar oyster plate — not falafel wraps, not poke, not dim-sum steamers, not cruise buffets. Ticket print is a hint. Plate-scan when ice is packed is the join. Service pricing is devices plus SMS send volume. You bring the phones and operator credit. Free is 1 device, 300 SMS lifetime, and 300 contacts.
Starter allows 2 devices: bar dual-SIM plus a spare. Uncapped platform volume is not unlimited carrier SMS. Confirm payloads in Developer Center.
printed · plated · SMS
order + plate-scan — ice dump remakes once
A raw-bar ready is not a loyalty dump
Ready copy names the order and pickup window. Happy-hour blasts live elsewhere. Mixing them is how a guest STOPs the week the only dozen they waited on is actually on ice.
If POS fires “ready” when the ticket prints, the guest thinks shells are open. Join plate-scan. Suppress print-to-guest templates.
Oyster STOP matrix
| Event | SMS | Failure |
|---|---|---|
| Ticket print | None or “in queue” | “Ready” before ice |
| Plate-scan | Order + bar | Loyalty stuffed in |
| Ice dump remake | Once after new scan | Two ready texts |
| POS OTP | Auth pool | OTP on the bar radio |
Plate-scan vs ticket print
Persist order-id plus plate-scan. DLR. MCP wraps REST only.
Shuck is not auto-reply
The SMS is that plate. A menu upsell is marketing. FTC business guidance is not a reason to hide STOP behind a mignonette carousel.
Devices, volume, and airtime
Happy-hour peaks spike. We meter devices and platform sends. Free (1/300/300) is one bar proof.
Bar operations
Charge the bar chassis before first shuck. Setup, Downloads, pricing.
Decision guide
Ship when notice joins plate-scan. Delay if print texts “ready.” Not a CodeCanyon oyster pack.
Oyster checklist
- Plate-scan idempotency.
- Purpose-level STOP.
- HELP names bar and order.
- No allergen auto-reply.
- Developer Center fields confirmed.
Next steps
Scenario 1711 falafel, scenario 1411 poke.
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
