Does brunch SMS include carrier credit?

No. Priced by devices and SMS send volume. You use your own phone and operator SMS credit. The weekend host-stand prepaid is yours.

Can last-call specials auto-reply on the deposit OTP SIM?

No. Isolate reservation-deposit OTP from brunch holds and last-call promo so a 60-cover Sunday cannot starve payment codes.

Where must STOP work after 10pm?

On last-call and leftover-brunch marketing. A YES/NO hold can auto-reply; a cocktail blast cannot swallow opt-outs.

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

Key Takeaways

Brunch holds fire at 10:40: YES/NO auto-reply on the host SIM, STOP on that same radio.
Last-call cocktail blasts are late-night promo — quiet hours and STOP, never deposit OTP.
A Sunday brunch that loses the host phone is a floor problem, not a copy problem.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Brunch pings still bill platform volume plus the weekend SIM’s airtime.
Free is 300 SMS lifetime on one device — prove STOP on a weekday staff brunch first.
Developer Center owns live API parameters; this is the brunch/last-call floor plan.

Summary

Brunch turns at 11. A 10:40 hold, a YES/NO auto-reply, and STOP on the host SIM matter more than a last-call cocktail bot that hijacks the deposit OTP radio after 10pm. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.

If last-call specials and brunch deposits share a phone, Sunday morning will starve the payment code.

Brunch hold vs last-call vs deposit

Lane	Host SIM	STOP / auto-reply
10:40 brunch hold	Yes — short window	YES/NO; STOP honored
Last-call cocktails	Late-night promo only	STOP + quiet hours; no deposit bleed
Reservation deposit OTP	Never	No auto-reply, no last-call

Key takeaways

Brunch holds live on the host SIM with a tight morning window.
Last-call is promo and never shares deposit OTP.
A dead host phone at 11am is a floor failure.
Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Developer Center owns live API parameters.
Canary STOP on a weekday staff brunch before Sunday volume.

Context

Hosts use this brunch scenario to park 10:40 holds on the weekend SIM and keep last-call promo off the deposit OTP radio.

Radio reality still wins: offline phones and OEM killers break scenarios overnight.

Cross-link hub cornerstones instead of rewriting the product overview.

Keep examples conceptual until Developer Center confirms live request shapes.

Budget airtime for retries — failed loops still cost operator credit.

Core scenario guidance

Map 10:40 holds, last-call blasts, and deposit-OTP moments to named pools before the first Sunday brunch.

Separate configuration mistakes from radio failures during incidents.

Write acceptance criteria before seasonal or clinic-hour traffic.

Prefer gradual rollout with feature flags when automation is involved.

Cost and ownership

Model brunch as devices plus volume plus the weekend host-stand airtime. Free is 300 lifetime SMS — prove STOP midweek first.

Failed retries still burn credit during scenario experiments.

Assign who owns SIM top-ups and spare handsets.

Keep marketing spend out of OTP device pools.

Operations

Daily checks: pairing health, battery, queue depth, and DLR anomalies.

After OEM updates or SIM swaps, re-test the scenario path end to end.

Keep a spare charged device ready for failover drills.

Name an on-call owner before unattended sends go live.

Security and compliance

Protect API keys per environment; rotate after contractor access ends.

STOP and consent still apply on promotional scenario lanes.

Avoid logging full OTP bodies into shared chat.

Verify webhook signatures and TLS on every callback path.

Decision guide

Ship brunch auto-reply only when hold windows, last-call STOP, and deposit-OTP isolation are written.

Delay if you cannot explain offline-phone behavior during peak hours.

If zero phone ops is mandatory, evaluate CPaaS for that lane.

If local SIM economics matter, harden the Android path and monitor airtime.

Checklist

Scenario moments listed with owners.
OTP vs marketing isolation confirmed.
Spare device funded and paired.
Canary on staff numbers passed.
Developer Center checked if API-shaped.
Webhook/DLR monitoring ready.
Airtime budget includes retries.
On-call owner named.
Rollback path documented.
Hub cornerstone reviewed.

Next steps

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

Deep dive: production hardening

Canary on staff numbers before customer OTP.

Battery exemptions and OEM killers dominate overnight reliability.

Cross-link Setup, Pricing, Downloads, and Developer Center with keyword-rich anchors.

If zero phone ops is mandatory, evaluate CPaaS for that lane instead.

Webhook signature verification is non-negotiable for scenario automation.

Document who owns SIM top-ups for multi-site scenario rollouts.

Prefer honest latency expectations over marketing claims about global SLAs on SIM paths.

Scenario playbooks still bill by devices and SMS send volume. You bring the Android phone and operator SMS credit.

Developer Center owns live API parameters. Scenario blogs teach process and failure modes, not endpoint catalogs.

Ecommerce webhooks must verify signatures before they trigger SMS sends.

Clinic reminders need consent records and STOP handling even when messages feel transactional.

Logistics ETAs should degrade gracefully when devices go offline mid-route.

Edtech OTP spikes at exam windows — capacity plan devices before the semester starts.

Fintech OTP is high-stakes: isolate devices, rotate keys, and avoid logging full codes.

Real-estate nurture is promotional; keep it off OTP SIMs and honor quiet hours.

Restaurant reservation SMS still needs STOP on marketing lanes.

SaaS onboarding OTPs should canary on staff numbers before paid scale.

Field-service dispatch needs two-way inbox ownership so techs are not double-booked.

Marketplace seller alerts need multi-device failover when a single phone is the SPOF.

NGO outreach must separate fundraising blasts from operational alerts.

Appointment businesses live on reminder deliverability the morning of the visit.

Bulk CSV import needs validation before radio send; bad rows burn airtime.

Scheduled SMS must survive device sleep and timezone mistakes.

Auto-reply and STOP protect promotional lanes — never auto-reply into OTP threads.

Dual SIM routing fails when slot maps drift after reboot without re-pair.

Multi-device failover only helps if spare phones stay charged and paired.

MMS attachments inherit carrier size and APN limits.

USSD requests are carrier- and region-sensitive; treat timeouts as expected.

Contact lists need consent metadata stored with the number.

OTP priority queues fail when marketing blasts share the same device pool.

Spare charged devices matter more than brochure SLAs when phones send the SMS.

Airtime surprise bills happen when bulk loops ignore radio pace.

OTP and marketing must stay on separate lanes on every scenario.

Never claim unlimited free cloud SMS credits with no device or volume meter.

Name an on-call owner before unattended schedules go live.