← Back to Blog

Running a Restaurant Waitlist Without Pagers or a Clipboard

· 6 min read

Coaster pagers cost real money, walk out of the building in coat pockets, and stop working somewhere around the far end of the terrace. The clipboard they replaced was worse. Here is how a restaurant or cafe waitlist runs off the guest's own phone, and what actually changes at the host stand.

What pagers really cost you

The sticker price is the smallest part. A set of coasters and a charging base is a four-figure purchase, each replacement unit runs $50–$80, and a busy restaurant loses several a year to pockets and bins. Then there is the charging station nobody remembers to use, the units that hold four minutes of battery by year two, and the range that does not reach the pavement tables you actually want people waiting at.

The deeper cost is what pagers do to your host. Handing one out, retrieving it, wiping it, chasing the guest who wandered off with it — that is a person doing device admin during your busiest forty minutes.

How a phone-based waitlist works on the floor

A guest arrives, scans the code on the host stand, and enters the size of their party. They get a position in line and an estimated wait on their own screen. When you are ready, the host taps to call them, and their phone updates.

Three things change immediately:

  • Your doorway clears. Guests who can see they are number six with a 25-minute wait go and have a drink somewhere, or walk the block. They come back — and crucially, they come back rather than leaving for good, because they can see they are still in the line.
  • The host stops repeating themselves. The "how much longer?" question is answered on the guest's phone, continuously, without anyone being interrupted mid-seating.
  • Nothing needs charging. No base station, no lost units, no end-of-night hunt for coaster number nine.

The part that is harder than with pagers

Be straight about this: a pager buzzes in someone's hand. A phone in a pocket on silent does not. You will have guests who miss the call.

What makes it work anyway:

  • Tell them the rule when they join. "Keep an eye on your phone, we'll hold your table for five minutes." Said once at the start, this prevents nearly every dispute later.
  • Call slightly early. Ring the party when the table is being cleared, not when it is wiped and set. The buffer absorbs the guest who is two doors down.
  • Make "missed" recoverable, not fatal. A party that turns up three minutes late should go back near the front, not to the bottom. Any waitlist that cannot do this will cost you covers and goodwill.

Quoting the wait

Restaurant waits are harder to estimate than counter service because table turn time varies enormously with party size and time of night. Two practical rules:

  • Estimate by party size, not by headcount waiting. Four parties of two ahead of you is a different wait from two parties of eight, and a single average will be wrong for both.
  • Quote a range and lean high. A guest told 30–40 minutes who is seated at 28 is delighted. A guest told 20 who is seated at 35 is writing a review.

If you want to do this properly, measure your actual turn times by party size for a fortnight rather than guessing — the method is in how to estimate wait times accurately.

Walk-ins, bookings and the bar

Most restaurants should run the waitlist as its own line, separate from the reservation book. Mixing them produces an order nobody can explain to a guest standing in front of them. Keep the booking system for booked tables, keep the waitlist for walk-ins, and let the host decide which table goes to which.

If you have a bar, say so when the guest joins: a waiting party at your bar is revenue, and a waiting party on the pavement is not. A waitlist that shows a 25-minute estimate is, in effect, a drinks recommendation.

A first Friday night

  1. Run both systems for one service. Keep the pagers on the shelf for the guests who want one and for phone-flat emergencies.
  2. Put the code on the host stand at eye level, with one line: "Scan to join the waitlist."
  3. Give the host one script, and make them say it every time: party size, estimate, "watch your phone, we hold for five minutes".
  4. Review two numbers at close: how many parties walked away before joining, and how many missed their call. Those two tell you what to adjust next week.

The bottom line

Moving the waitlist to the guest's phone removes the hardware, clears your doorway and stops your host answering the same question all night. The one thing you give up is the buzz in the hand, and you get it back with a clear rule at sign-up, calling a touch early, and a missed party that can be recovered rather than sent to the back.

SnapQ puts a numbered ticket, a live position in line and an estimated wait on your customer's phone.

Start Your Free 14-Day Trial

14 days free. No credit card, no hardware.