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

Summary

Restaurant STOP in scenario 1819 is the church basement supper: potluck pickup windows, honor STOP even after the social-hour bell. Unlike dinner rush, franchise HQ, ghost kitchen, catering, staff roster, waitlist, vendor dock, banquet BEO, courier, wine club, allergen/86, last-call bar, stadium suite, hotel in-room dining, commissary bake, campus dining, food-truck park, airport F&B, cinema concession, ski-lodge cafeteria, marina galley, zoo cafe, museum cafe, theme-park kiosk, bowling snack bar, arcade snack, golf halfway house, convention hall, ferry-terminal snack, or racetrack concession, this lane is a parish clock, not a photo finish.

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.

A social-hour bell is not consent. Honor STOP. Send the pickup window only. Keep the pie auction off the radio.

Key takeaways

• Church-supper SMS is potluck pickup windows — honor STOP even when the social-hour bell just rang.
• Auto-reply must not re-offer the pie auction after STOP.
• Keep member-portal OTP off the kitchen tablet that dumps supper nags.
• Service pricing is devices plus SMS send volume. You bring the Android phone and operator credit.
• Free is 1 device, 300 SMS lifetime, 300 contacts. Developer is 25,000 SMS per year.
• Weather cancellations are still promotional if they push food. Suppress when STOP is on file.

Related reading

Start from SMS auto-reply and STOP keywords, compare device and SMS volume pricing, open two-way SMS inbox, and review CTIA messaging principles.

Context

Parish kitchens land here after a weather-cancel blast re-offered food to STOP’d members, or after auto-reply echoed the pie auction. Member OTP cannot share that tablet.

Core scenario guidance

Honor STOP before radio. Template: event + pickup window. Drop upsells. Isolate OTP.

Canary a staff kitchen after OS updates. MCP wraps REST. Developer Center owns fields.

Cost and ownership

Devices + volume + operator airtime on every retry. Developer is 25,000 SMS per year. Free (1 / 300 / 300) proves pairing, not a parish kitchen.

Operations

Daily last-seen, battery, STOP diffs vs calendar. After a weather template change, one staff canary. On-call before unattended Wednesday suppers.

Security and compliance

Member mobiles are PII. Encrypt at rest. Never log STOP replies as marketing consent. Verify TLS on every callback.

Decision guide

Ship when STOP, window templates, and OTP isolation exist. Delay if a cancel can still nag STOP’d members. If zero phone ops is mandatory, evaluate CPaaS for that slice.

Checklist

• Honor STOP after the bell.
• No pie-auction upsell after STOP.
• Deduplicate event ids.
• OTP isolated.
• Spare paired.

Next steps

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

Deep dive: production hardening

STOP before radio is non-negotiable. A weather-cancel send still spends airtime. Battery exemptions dominate Wednesday nights.

Deep dive: scaling and failure modes

Scale is events times windows, not a blast of the directory. Never claim unlimited free cloud SMS credits with no device or volume meter.

Deep dive: integration discipline

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