SMS Queue Management for Restaurants: Cutting Wait Times
The pager buzzer you hand out at the host stand was a clever solution in 2003. It still works. But it has a fixed range, the batteries die, guests can't wander to the bar two doors down, and every lost or stolen unit costs you $40 to replace. A text message does the same job with infinite range, no hardware, and a paper trail.
Full disclosure: I work for ReadySMS, so I have a horse in the SMS race. I'll still tell you where a plain pager system is fine and where a text-based waitlist actually earns its keep.
What an SMS queue actually does
The mechanics are boring, which is the point. A guest walks up, the host enters their name, party size, and mobile number. The system sends a confirmation text. When the table is close — usually two or three parties out — you send a "you're next" heads-up. When it's ready, you send "your table's ready, please see the host within 10 minutes."
That's it. Three messages, maybe four if someone replies asking how much longer.
The win isn't the texting. It's what the guest does between the first text and the last one. Instead of standing in your entryway watching a pager, they grab a drink at the bar, walk the block, or sit in their car with the AC on. Perceived wait time drops even when actual wait time doesn't move. A 35-minute wait that you spent shopping next door feels shorter than a 20-minute wait spent hovering by the door.
Where the real revenue shows up
Two places, and neither is obvious from the host stand.
Bar spend. If a guest can leave the entry and order a drink because they trust the text will find them, you sell more drinks. A single cocktail at $14 on a busy Friday, across even 30 waiting parties, is real money — and the margin on liquor is where restaurants actually make rent.
Table turns and no-walks. People who give up and leave a packed lobby ("walk-aways") are pure lost revenue. A text waitlist lets you quote an honest wait, let them roam, and pull them back precisely when the table flips. Fewer walk-aways, tighter turns.
There's a smaller third benefit: the data. Every text is timestamped, so you learn your actual wait times by daypart instead of guessing. That's useful when you're staffing.
The cost math, because it's tiny
This is the part that surprises people. SMS queue management costs almost nothing per guest.
A typical waitlist guest gets three to four messages. Let's say four, and assume each is a single 160-character GSM-7 segment (most are — "Hi Maria, your table for 4 is almost ready! ~10 min" is well under the limit; don't add emoji unless you want to halve your character budget to 70).
On ReadySMS Starter pricing, that's $0.0084 per segment plus the $0.0045 carrier pass-through = $0.0129 per message. Four messages per guest:
| Item | Math | Cost |
|---|---|---|
| Per message (Starter) | $0.0084 + $0.0045 | $0.0129 |
| Per guest (4 messages) | 4 × $0.0129 | $0.0516 |
| 60 waiting parties/night | 60 × $0.0516 | $3.10 |
| Full month (~26 service nights) | $3.10 × 26 | $80.50 |
About $80 a month to text every waitlisted party at a busy restaurant, all in. If you push higher volume — multiple locations, a heavy weekend operation — you'd slide into the Basic tier at $0.0074/segment and the per-message cost drops further. The SMS cost analysis for restaurants post walks through the tier math in more detail if you want to model your own numbers.
For comparison, lose one party of four who walked away because the lobby was packed, and you've burned more than that month's texting bill on a single Saturday.
Compliance: lighter than marketing, not zero
Here's where restaurants relax a little, and they should — but not all the way.
Waitlist texts are transactional, not promotional. The guest handed you their number specifically to be told their table is ready. That's clear, contextual consent for the thing you're texting them about. You are not, under that consent, allowed to text them next Tuesday's happy-hour promo. Different message, different consent.
What you still need to get right:
- 10DLC registration. Any business sending application-to-person SMS in the US needs a registered 10DLC brand and campaign, or carriers filter your traffic and your "table's ready" text quietly never arrives. ReadySMS handles brand + campaign registration in-app — roughly ~$10/mo per brand and ~$20/mo per campaign in carrier fees, usually approved in 1–3 days. If you've never set this up, the 10DLC registration cost breakdown explains exactly what you're paying for.
- Honor STOP automatically. If someone replies STOP, they're out — and that opt-out should stick across every campaign so no rogue promo blast hits them later. ReadySMS propagates opt-outs automatically; see handling SMS opt-outs.
- Don't repurpose the list. This is the one restaurants get wrong. A waitlist number is not a marketing list. If you want to text promos, capture separate marketing consent at the table or on the check.
You generally don't need expensive litigator scrubbing on a transactional waitlist the way a cold-marketing operation does — the guest is standing in front of you and just gave you the number. Quiet-hours enforcement also matters less when you only text during service. Keep it simple and the compliance load stays light.
A realistic before-and-after
I'll keep this honest — I'm describing the pattern operators report, not a controlled study.
A mid-size neighborhood spot doing 80–100 covers on a Friday with a 25-minute peak wait was bleeding maybe 8–12 walk-aways a night during the rush. They switched the pagers for SMS, kept the same host workflow, and added one line to the confirmation text: "Feel free to grab a drink at the bar — we'll text you when your table's ready."
The reported changes after a few weeks:
- Walk-aways dropped. People will wait longer when they're not chained to the lobby. Even cutting 4–5 walk-aways a night recovers a few hundred dollars in covers.
- Bar tickets opened earlier. Waiting guests started buying drinks instead of standing around. Pre-dinner bar revenue ticked up.
- The host stand got calmer. No one's asking "how much longer?" every four minutes because the "you're next" text already told them.
None of that is magic. It's the same dinner service with a less stressful waiting experience and a few recovered tables. The texting cost was a rounding error against the recovered covers.
When you don't need this
I said I'd be honest. A few cases where SMS queueing is overkill:
- You never have a wait. If your peak is four parties deep twice a year, buy a pager or just remember faces. Don't register a 10DLC campaign for that.
- Reservation-only fine dining. If everyone's booked and seated on a clock, your problem is reservations software, not a walk-in waitlist.
- Counter-service and fast casual. A buzzer or a number-on-a-receipt is plenty when the wait is six minutes for food, not 30 for a table.
SMS earns its place when you have genuine walk-in volume, real waits, and somewhere for guests to go while they wait — a bar, a patio, a shopping street.
The practical takeaway
A text-based waitlist is cheap (around $80/month even at busy volume), it cuts perceived wait time, it recovers walk-aways, and it nudges bar spend up — all by letting guests stop hovering in your entryway. The compliance lift is modest because waitlist texts are transactional, as long as you register your 10DLC, honor STOP, and don't quietly turn the waitlist into a marketing list.
If you want to model your own per-night cost, the cost calculator will run your volume against the tiers in a minute. And if you're starting from scratch, ReadySMS gives you 2,500 free credits with no card — enough to text a few hundred parties and see whether the lobby gets quieter before you spend a dollar.