Restaurant Waitlist and Host Stand Glossary
Reviewed for 2026, updated September 8, 2026.
Plain definitions of the terms hosts, managers, and waitlist software use, plus answers to the questions operators ask most about waits, paging, and seating.
- Abandonment rate
- The share of parties that join the waitlist and leave before being seated, whether they tell the host or simply disappear. Tracking it by hour and by quoted wait shows the point at which waits start costing you guests.
- Camper
- A party that stays at a table long after finishing their meal, stretching the turn and delaying everyone behind them on the list. Campers are one of the main reasons real turn times drift from the average the host is quoting.
- Check-in confirmation
- A text sent to the guest the moment they are added to the waitlist, confirming their spot and the quoted wait. It doubles as a test of the phone number, since a typo shows up immediately instead of at page time.
- Consent to text
- The guest's agreement to receive text messages from the restaurant. In the US, business texting is regulated, so waitlist tools typically collect consent at check-in and include a way to opt out, and operators should keep messages limited to what the guest signed up for.
- Cover
- One guest served during a meal period. Restaurants count covers rather than tables when planning kitchen staffing and comparing nights, and a party of four seated at a single table is four covers.
- Deuce
- Industry shorthand for a two-top, a table that seats two guests. Deuces usually turn faster than larger tables, which is why quoting all party sizes from one average wait is a mistake.
- Double seating
- Seating two parties in the same server's section at nearly the same moment, so the server has to greet, take orders, and deliver drinks for both at once. Hosts avoid it by rotating sections, and it is a common cause of slow first-course times.
- Four-top
- A table that seats four guests, generally the most common table size in a US dining room. Two-tops and four-tops are often combined to build tables for larger parties.
- Grace period
- The window after a reservation time during which the table is still held for the booking. Once it passes, the table is released to the waitlist. Stating the grace period in the confirmation keeps the policy from feeling arbitrary.
- Hold window
- The number of minutes a table is kept for a party after they are paged. Common practice is a short window stated at check-in, with a reminder partway through, after which the table goes to the next party on the list.
- Host stand
- The station at the entrance where guests are greeted, added to the waitlist or matched to a reservation, and led to a table. It is also the control point for the pace of the whole dining room.
- Large party
- A party whose headcount reaches the threshold a restaurant sets for special handling, often somewhere around six to eight guests, above which a separate quote and different seating rules apply. Large parties usually need combined tables and a longer turn, which is why hosts treat them as their own queue rather than part of the general list.
- No-show
- A guest who does not arrive for a reservation or does not return when paged from the waitlist. Reminder messages, a clear hold window, and a fair rejoin policy reduce no-shows without penalizing guests who had a good reason.
- Pager buzzer
- A restaurant-owned handheld device given to a waiting guest that vibrates or lights up when the table is ready. Buzzers work only within range of the base station and carry no information beyond the alert itself.
- Party size
- The number of guests in a group waiting to be seated together. It determines which tables can take the party and therefore which queue the party is really in, since a two-top clearing does nothing for a party of six.
- Pre-bussing
- Clearing finished plates and glassware from a table during the meal rather than all at once at the end. It shortens the reset after guests leave and can take minutes off every turn across a busy night.
- Quote buffer
- Padding added to a calculated wait estimate before it is given to the guest, so the table is ready slightly before the promised time. A modest buffer makes the host look reliable; a huge one drives guests to the restaurant next door.
- Remote check-in
- Letting a guest join the waitlist from their phone before arriving, usually through a link or a text. It smooths the arrival rush but requires clear rules about when the party must be present to keep their place.
- Reservation
- A table promised to a guest for a specific time, made in advance. Reservations and walk-ins share the same tables, so the host balances the two with holds, grace periods, and a single view of expected seating times.
- Reset time
- The minutes between a party standing up and the table being cleared, wiped, and set for the next guests. Reset time is part of every turn, and it is one of the easiest pieces to shorten with bussing staff and a clear process.
- Rotation
- The order in which hosts assign new parties to server sections so that work is spread evenly. A good rotation avoids double seating and keeps any one server from being buried while another stands idle.
- Section
- A group of tables assigned to one server for a shift. Sections determine who greets a newly seated party and are the unit hosts think in when deciding where the next party should go.
- Table combination
- Two or more tables pushed together to seat a party larger than any single table holds. Combining tables takes them out of the general pool, which is why large parties should be quoted from the availability of the specific combination, not the room as a whole.
- Text paging
- Notifying a waiting guest by SMS that their table is ready, in place of calling a name or handing out a buzzer. Done well, it includes a check-in confirmation, a clear ready message with a hold window, and a way for the guest to reply.
- Throughput
- The number of parties or covers a dining room can serve in a given period. Throughput is set by table count, turn time, and how quickly cleared tables are refilled, and the host stand influences all three.
- Turn time
- The elapsed time from a party being seated to the table being ready for the next party, including the meal and the reset. Turn time varies by party size, daypart, and menu, and it is the single most important input to an accurate wait quote.
- Two-way texting
- A paging setup where the guest can reply to the restaurant's message and the host sees the reply at the stand. It lets guests say they are on their way, ask for a few more minutes, or drop off the list without calling.
- Waitlist
- The ordered list of parties waiting for a table, along with party size, contact details, arrival time, and quoted wait. On software, the list can be ordered by expected seating time rather than arrival order, which matters when party sizes differ.
- Walk-in
- A guest who arrives without a reservation and is either seated immediately or added to the waitlist. Walk-in-driven restaurants live and die by how well the host stand quotes and pages.
- Walkaway
- A party that leaves the waitlist without being seated, often without telling anyone. Walkaways are the most direct cost of poor quoting and poor communication, and they are invisible unless the waitlist records removals.
Questions people ask
How do restaurants estimate wait times?
The honest method uses a few numbers the host can see: how many parties ahead need the same table size, how many tables fit that size, how long those tables turn on a similar night, and how far along the current occupants are. From those, the host estimates when the next matching table clears and how many clearings this guest must wait through, then adds a small buffer. Guessing from the size of the crowd is what most stands do, and it is why quotes are so often wrong.
What is a reasonable wait time for a restaurant before guests start leaving?
It depends heavily on the restaurant, the night, and the alternatives nearby, so there is no universal number. Most operators find a threshold in their own data where walkaways climb sharply, and it is usually shorter for casual and family dining than for a destination restaurant. The practical answer is to track walkaways by quoted wait and let your own numbers set the ceiling.
Should a restaurant use pagers or text messages to notify waiting guests?
Text messaging suits most restaurants because guests keep their own phones, can leave the property, and can reply. Pagers still make sense where guests prefer not to share a number or where cell coverage in the waiting area is poor. Many restaurants run text as the default with a simple fallback for the small share of guests who decline.
How long should a restaurant hold a table after paging a guest?
Long enough to be fair, short enough that the next party is not left staring at an empty table. Many restaurants settle on a window in the range of five to ten minutes, state it at check-in, send a reminder partway through, and then release the table. Whatever the number, guests accept it when they were told in advance.
How do you handle a guest who is angry about the wait?
Acknowledge the wait honestly, update them with a real estimate rather than a reassuring guess, and offer something concrete: a spot at the bar, a look at where they are on the list, or a text when the table is close. Most frustration comes from feeling ignored or misled, not from the wait itself, so attention and honesty solve more than apologies do.
What is the difference between a waitlist and a reservation system?
A waitlist manages guests who are already at or near the restaurant and waiting for the next available table. A reservation system manages tables promised in advance for a specific time. Many tools do both, but the core problems differ: the waitlist is about quoting and paging in real time, while reservations are about holds, grace periods, and no-shows.
How do you seat large parties without stalling the rest of the waitlist?
Treat them as a separate queue. Identify the specific table combinations that can hold the party, estimate when the next one frees up, and quote from that rather than from the general list. Ask the party to be complete before seating, since a half-arrived group ties up combined tables while producing nothing, and communicate the longer wait honestly up front.
What data should a restaurant track from its waitlist?
At minimum, the time each party joined, the wait they were quoted, when they were paged, when they were seated, and when they were removed if they left. Add party size and the table they took, and you can calculate real turn times by size and daypart, quote accuracy, and walkaway rate by wait length. Those numbers drive better quotes and better staffing.
Do restaurants need permission to text guests?
Yes. Business texting in the US is regulated, and guests should agree to receive messages when they give their number, with a clear way to opt out. Waitlist tools generally handle this at check-in. The safe practice is to send only messages the guest expects, such as the confirmation, the page, and wait updates, and nothing promotional unless they separately agreed to it.
How can a host stand reduce no-shows on the waitlist?
Confirm the number with a text at check-in so the page actually arrives, give an honest quote so guests do not wander too far, send a check-in message partway through long waits, state the hold window up front, and remind guests as the hold runs down. A fair rejoin policy for guests who miss the table keeps the occasional miss from turning into a lost customer.
How do you balance walk-ins against reservations on a busy night?
Give reservations priority within a stated grace period, then release the table to the list. Hold back a share of tables for walk-ins on nights when you know they come, and keep both streams visible in one ordered view so the host can see expected seating times side by side. Consistency matters more than the specific rule, because guests can tell when the policy is being improvised.
What makes a good host stand greeting?
Fast acknowledgment, a name and party size captured in seconds, an honest quote with a range if the night is unpredictable, and a clear description of what happens next: we will text you, we will hold the table for this long, feel free to step outside. A short script that every host uses the same way beats a warm but rambling one that leaves the next guest waiting.
Is waitlist software worth it for a small restaurant?
If waits are short and the room is small enough for the host to see every guest, a clipboard is fine. It becomes worth it when the line regularly stretches past the lobby, when guests are walking, or when the host is spending more time managing the list than greeting people. The record it leaves behind is often the most valuable part, since it lets a small team quote and staff from real numbers.