Why a Seattle dining room is different
Most American waitlist software is designed against one federal statute and a general assumption that texting a customer who gave you their number is fine. Washington is where that assumption breaks, twice.
The first break is the text message itself. State law does not merely require disclosure or an opt-out — it prohibits a person conducting business in the state from initiating a commercial electronic text message to a Washington cellular number, and it declares a violation an unfair or deceptive act under the consumer protection act. Prior clear and affirmative consent is the exception that makes it lawful. That is a materially different posture from “collect the number and be careful”, and it means the consent record is the compliance artefact, not the message.
The second break is stranger and newer. Washington’s consumer health data law defines that category expansively and reaches ordinary businesses, not just clinics. Front-of-house teams collect health-adjacent information constantly — a nut allergy, a wheelchair-accessible table, a guest who cannot manage stairs — and type it into a queue entry without a second thought. In this state that note deserves to be treated as regulated data: collected because the guest offered it for this visit, used to seat them, and gone with the entry.
The third difference is labour. Seattle regulates scheduling in food service directly, which changes what “we will call someone in if it gets busy” costs.
What the law requires when you text a guest in Seattle
Consent first, message second. Because the state rule is a prohibition with a consent exception, the join screen is doing the legal work. Say plainly that you will text about this visit, capture the affirmative action, and keep the record. Do not import a list from another system and assume the consent travelled with it.
One purpose per permission. A table-ready alert and a promotional message are different things and need different permissions. Merging them is the single most common way a well-run restaurant ends up sending an unconsented commercial text.
Health-adjacent notes: short-lived and minimal. Ask for what you need to seat the party well and no more. Do not build a guest profile that accumulates dietary flags across visits unless the guest asked for that and you can explain it. If you do keep a guest record, the retention question is the first design decision, not the last — see restaurant waitlist with guest CRM for the version of that with a delete path built in.
Scheduling, if you are covered. Seattle’s secure scheduling rules apply to larger food service employers and require schedules in advance, a written good faith estimate of hours at hire and annually, and predictability pay when the schedule changes late. A queue tool that lets a manager see the next two hours accurately is, in that context, a scheduling instrument.
Service charges. State guidance requires telling customers how a service charge is split. In a walk-in room the practical place for that is next to the wait, because the two questions get asked together.
The Seattle dining calendar
- Late May to mid-September — cruise season and long evenings. Waterfront and downtown rooms take an early, compressed dinner from sailings and a second, later local turn. Two peaks, one host.
- October to April — the dark, wet stretch. Guests will not wait outdoors, and a room without an interior waiting area sees walkaways that have nothing to do with the food.
- Weeknight event nights near the stadiums. Kickoff and first pitch move the entire evening forward by ninety minutes, and any staffing rule keyed to the day of the week fails on those dates.
- Convention weeks. Party sizes rise, arrival times cluster, and the mix shifts to guests who will not return, which is exactly when quoting an honest wait matters most.
The POS and reservation stack you will meet in Seattle
Washington has no certified till requirement, and the checkout market here is as consolidated as anywhere in the United States. The interesting constraint is the tipping and service-charge structure, because the state’s high minimum wage has pushed many rooms toward service charges rather than tips, and that in turn creates the disclosure duty above.
For a waitlist, the practical implication is that the queue is a communication surface as much as a seating tool: it is where the guest learns what the wait is, what the service charge is, and how you will contact them. Anything that hides one of those to look tidier is storing up an argument at the table.
If you are comparing a purpose-built queue against a broader booking platform, the Waitwhile alternatives page covers where the two diverge; the product frame is in restaurant waitlist software.
How StoveOps fits a Seattle room
Guests join from their phone, consent is captured with the purpose stated, and the table-ready message goes out by SMS, WhatsApp or email on one tap. Notes on an entry are scoped to that visit rather than accumulating into a profile by default, and the guest data stays with the restaurant — not with a marketplace whose retention policy you did not write.
Because the whole list is visible to everyone on shift, the handoff when a host goes on break stops being a verbal ritual; the shift handoff checklist is the version of that we recommend printing.
Seattle operator checklist
- Treat consent as the artefact: capture it, store it, be able to show it.
- Never import a phone list from another tool and assume the consent came with it.
- Keep marketing permission in a separate opt-in from the queue.
- Ask for a dietary or access note only for this visit, and keep it brief.
- Delete visit notes with the entry unless the guest asked otherwise.
- Check whether the secure scheduling rules apply to your headcount.
- If they do, stop using early cuts as your load-balancing tool.
- Disclose how the service charge is split, where the guest sees the wait.
- Give the room an indoor place to wait between October and April.
- Build a separate quoting rule for stadium nights.