What should a restaurant tell guests about consent before texting them from the waitlist?

A table-ready page and a marketing blast are two different asks

When a guest gives a host their cell number, they are agreeing to a single, obvious thing: you will tell them when their table is ready. That is a transactional message. The guest asked for it, they are standing in front of you, and they expect exactly one text in the next thirty minutes or so. Nobody in that moment is agreeing to a Tuesday brunch promo, a birthday club, or a newsletter about the new patio. Related: How do you text guests the moment their table is ready reliably?

The mistake we see most often is treating the waitlist as a free list-building machine. Someone exports six months of numbers into an email and SMS tool, sends one campaign, and the restaurant gets complaints, opt-outs, and occasionally a much more serious problem. Business texting rules in the United States are stricter than most host stands assume and they do change, so treat this article as operational guidance and run your actual promotional program past your own counsel. The safe operating rule is simple: consent for a table page is not consent for anything else. Related: How do you manage a restaurant waitlist during a packed weekend rush?

Keep reading: How do you text guests the moment their table is ready reliably?, How do you quote accurate wait times so guests are not frustrated?, How do you manage a restaurant waitlist during a packed weekend rush?. See how TablePingr helps you guest table-ready sms paging for restaurants.

The one sentence a host should say out loud at the stand

Consent works best when it is spoken, not buried on a laminated card. Give hosts a short line they can say in one breath: "What is the best cell number? We will text you once when your table is ready, and that is the only message you will get." That sentence does three jobs at once. It states the purpose, it states the frequency, and it states the limit, so the guest knows what they are agreeing to before they say the digits out loud.

Back it up in the first message itself. The initial text should name the restaurant, say why it arrived, and include a way to stop. Something like "This is the host stand at Rosewood. We will text this number when your table is ready. Reply STOP to opt out." If a guest would rather not give a number at all, that has to be a real option, not a fight. Take a name, tell them where to stand or sit, and page them by voice. A guest who says no should walk away feeling like they picked the normal choice. Related: How do you quote accurate wait times so guests are not frustrated?

Store the minimum, purge it early, and lock down who can see it

A waitlist needs surprisingly little data: first name, party size, a cell number, and timestamps. It does not need an address, an email, a birthday, or a note about what the guest was wearing. Every extra field is something you now have to protect and eventually explain. Set a retention window that matches how you actually use the data. Most restaurants can purge guest numbers within a short window after service, keeping only the anonymous timing data (party size, quoted wait, actual wait, turn time) that is genuinely useful for planning next month.

Then decide who can see live numbers and write it down. Personal phones should not be the paging device, screenshots of the list should not exist, and a guest number should never be used for a personal message from a staff member. This is not a hypothetical problem in hospitality, and it is the fastest way to turn a normal Friday into a genuine incident. Give managers accounts, give hosts accounts, remove accounts the day someone leaves, and make the rule part of host training rather than something people learn after it goes wrong. Related: Why should a restaurant ditch physical pager buzzers for guest text paging?

Opt-outs, complaints, and the guest who says never text me again

Opt-out handling has to be instant and automatic. If a guest replies STOP, the system should stop, no manager approval and no delay. There is one operational catch worth planning for: a guest who opts out while still on the list can no longer be paged, so the host needs to see that state on the waitlist itself and switch that party to a voice page. A silent opt-out that nobody notices looks exactly like a no-show, and you end up holding a table for someone standing twenty feet away.

When a complaint does arrive, answer it fast and plainly. Confirm the number is removed, say what the number was used for, and do not argue about whether the guest technically agreed. Delete first, explain second. It also helps to run a quiet audit once a quarter: pull a sample of numbers still in the system, check that anything past your retention window is gone, and confirm nobody exported the waitlist into a mailing tool. Ten minutes of checking beats a very bad week later.