Android SMS Gateway Scenario 619: Restaurants auto-reply and STOP in practice

Summary

Restaurant STOP in scenario 619 is allergen and 86-list holds: ticket notes, pass alerts, optional “allergy-safe” mailing. Unlike dinner-rush ACK, franchise HQ, ghost kitchen, catering, staff roster, waitlist, vendor dock, banquet BEO, courier dispatch, or wine club, this list is kitchen risk — not covers.

Service pricing is devices plus SMS send volume. You bring the Android phone and operator SMS credit. Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year. Starter, Professional, and Business list Unlimited SMS as platform send volume; devices and airtime stay metered.

An 86-list that doubles as a guest CRM is how you text a peanut-allergic diner a brunch coupon. Keep the pass SIM boring.

Key takeaways

• Allergen-hold STOP is a kitchen list: “86 peanuts on 14” is ops — a brunch coupon on the same SIM is not.
• Guest allergy notes can share an ops SIM. Marketing cannot share reservation OTP.
• Optional “join our allergy-safe list” still needs STOP. Ticket-level holds are a different lane.
• Service pricing is devices plus SMS send volume. You bring the phone and operator credit.
• Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year.
• Test STOP after a Saturday 86-list flush, not only on a Tuesday lunch special.

Related reading

Start from SMS auto-reply and STOP keywords, pair in the device setup guide, confirm fields in SMS API documentation, and review FDA food-allergen notes.

Context

Chefs land here after a Saturday 86 blast hit guests imported from the POS. Reservation OTP cannot share that pass burst.

Core scenario guidance

Scope ticket holds to staff and ticket ids. Map STOP to optional guest lists. Do not auto-reply coupon copy into an allergen question. Keep reservation OTP on another device.

Canary STOP after the Saturday flush. MCP wraps REST. Developer Center owns fields.

Cost and ownership

Devices + volume + hold ACK airtime. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing on one pass tablet.

Operations

Daily last-seen, battery, keyword fail, guest numbers leaking into 86 CSV. After SIM reseat, one staff STOP. On-call before unattended Saturday peaks.

Security and compliance

Allergy notes are sensitive health-adjacent data. Encrypt at rest. Do not keep them as a marketing CRM. Verify webhooks if a POS fires the SMS.

Decision guide

Ship when ticket-only holds, STOP on optional lists, and OTP isolation exist. Delay if POS guests can land in the 86 CSV. If zero phone ops is mandatory, evaluate CPaaS for that slice.

Checklist

• Ticket ids on holds.
• STOP on optional lists.
• OTP isolated.
• No POS guest merge.
• Spare paired.

Next steps

Return to Android SMS gateway app, compare device and SMS volume pricing, open device setup, and confirm APIs in SMS API documentation.

Deep dive: production hardening

Auto-reply must never ACK a STOP with a brunch coupon. Dual-SIM pass tablets fail when the keyword slot swaps after reboot. Battery exemptions dominate overnight closets.

Deep dive: scaling and failure modes

Scale is tickets times holds, not lifetime guest CRM. Never claim unlimited free cloud SMS credits with no device or volume meter.

Deep dive: integration discipline

Developer Center owns live API parameters. Persist ticket id and mute. MCP is a REST wrapper. If zero phone ops is mandatory, evaluate CPaaS. You bring the Android phone and operator credit.