How the restaurant SMS waitlist works
Guests join your restaurant’s public waitlist from a link or QR code, then wait nearby instead of crowding the doorway. The host sees each party in one live queue, updates its status and sends a table-ready text when a table opens. No guest app or pager is required.
The 60-second waitlist demo shows guest entry, the host queue and the table-ready update in sequence. SMS requires a configured channel and a reachable destination; check the recorded delivery result before relying on it during service.
How to run the guest and host flow
- Publish one entry point. Open the exact location link or QR code on a guest’s phone while signed out. Check that it leads to the right restaurant and that the join screen explains what contact details are used for.
- Manage one live queue. Ask a host to find the test party, verify its size and status, and make a change. Use a single source of truth if you also keep a paper fallback.
- Send a table-ready update. Notify an approved test contact. Check the recorded delivery status and the guest’s next action, then rehearse a phone or in-person fallback for a failed delivery.
For the actual wording, use the restaurant SMS message templates as a starting point and adapt them to your service policy. For a comparison with physical devices, see digital waitlists versus restaurant pagers.
What happens when a guest needs to answer?
Inbound SMS replies do not appear in the StoveOps host queue today. Give guests a separate staffed route for changing party size, requesting more time or cancelling. The host can then update the party in the live queue.
Keep operational waitlist messages separate from marketing campaigns. Tell guests why you collect their number, follow the consent and opt-out requirements in your market, and check which channels your restaurant can actually send to. The SMS consent guide explains the questions to review for US and Canadian service; it is not a substitute for your own legal review.
Plans and message limits
| Plan | Stores | Included SMS or WhatsApp messages each month | Reservations |
|---|---|---|---|
| Basic | 1 | 500 | No |
| Professional | Up to 3 | 2,000 | No |
| Business | Up to 10 | 5,000 | Yes |
Email messaging is unlimited on these plans. Professional and Business allow unused included messages to roll over for up to three months; Basic has no rollover. SMS and WhatsApp overage and destination availability matter when you estimate cost. Count the messages your real service would send, then check current pricing and billing terms before subscribing. Guest entries themselves do not have a monthly quota.
If your main requirement is diner discovery through a reservation marketplace, an owned waitlist solves a different problem. The OpenTable comparison explains that distinction. If you need a wider vendor shortlist, use the restaurant waitlist apps guide.
Try it with one representative service
Start with the waitlist demo, then use the seven-day trial to test your own location and staff workflow. A card is required at checkout, and billing begins after the trial under the terms shown there. Run an approved test join and notification first; during service, record the party status and any delivery failures so your team knows when to use its fallback.