Key Takeaways
- A BBQ ready text is that wrap at that window — not everyone who ever scanned the QR for a brisket 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 window SIM.
- Idempotency is order-id plus wrap-scan — restock reprints the same ticket.
Summary
Scenario 1831 is restaurant auto-reply and STOP for a BBQ pit window — not oyster bars, not falafel, not hawker stalls, not food trucks already covered. Ticket print is a hint. Wrap-scan when butcher paper is taped 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: window dual-SIM plus a spare. Uncapped platform volume is not unlimited carrier SMS. Confirm payloads in Developer Center.
printed · wrapped · SMS
order + wrap-scan — restock remakes once
A pit ready is not a loyalty dump
Ready copy names the order and pickup window. Punch-card blasts live elsewhere. Mixing them is how a guest STOPs the week the only brisket they waited on is actually wrapped.
If POS fires “ready” when the ticket prints, the guest thinks the pit pulled. Join wrap-scan. Suppress print-to-guest templates.
BBQ STOP matrix
| Event | SMS | Failure |
|---|---|---|
| Ticket print | None or “in queue” | “Ready” before wrap |
| Wrap-scan | Order + window | Loyalty stuffed in |
| Restock remake | Once after new scan | Two ready texts |
| POS OTP | Auth pool | OTP on the window radio |
Wrap-scan vs ticket print
Persist order-id plus wrap-scan. DLR. MCP wraps REST only.
Sauce is not auto-reply
The SMS is that wrap. A menu upsell is marketing. FTC business guidance is not a reason to hide STOP behind a sauce carousel.
Devices, volume, and airtime
Lunch sell-outs spike. We meter devices and platform sends. Free (1/300/300) is one window proof.
Pit operations
Charge the window chassis before first pull. Setup, Downloads, pricing.
Decision guide
Ship when notice joins wrap-scan. Delay if print texts “ready.” Not a CodeCanyon BBQ pack.
Pit checklist
- Wrap-scan idempotency.
- Purpose-level STOP.
- HELP names window and order.
- No allergen auto-reply.
- Developer Center fields confirmed.
Next steps
Scenario 1771 oyster, scenario 1711 falafel.
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
