Four concrete elements that make the message to the waitlist guest clear
A practical overview of the four elements a message to waitlist guests should contain - time, number of seats, a deadline tied to action, and a response method the guest can use with one word or one click - with concrete examples of wording that works and wording that creates unnecessary uncertainty.
What the message actually needs to answer
A message to a waitlist guest should answer four questions without the guest having to read between the lines: When is the table available? How many seats does it cover? How long does the guest have to respond? And how do they respond? If one of these points is missing, a follow-up message often becomes necessary that could have been avoided.
Many messages are written as news that something has become available, not as a request requiring action. This means the guest reads the message and feels pleased, but doesn't necessarily understand that they must reply within a specific time to secure the table. The structure should always prompt a response, not merely inform.
Time and number of seats without room for interpretation
Write the time as a concrete combination of date, time of day and duration where relevant, for example 'tonight at 7:30 PM' or 'Saturday, June 14th at 8:00 PM'. Avoid phrasing such as 'a table has become available' without stating when - the guest cannot judge whether the time works until this has been clearly specified.
The number of seats should be stated as a figure, not as a description of the table. 'We have a table for 4' is clearer than 'a nice table by the window'. If the guest originally wanted seating for six but the available table seats four, this should be stated explicitly, so the guest can decide for themselves whether it works.
A deadline tied to an action, not just a time of day
A deadline without consequence feels optional. 'Reply by 6:00 PM' doesn't say what happens afterwards. It works better to state the consequence, for example 'Reply by 6:00 PM tonight, otherwise the table goes to the next guest on the list' - if that is indeed how the restaurant handles unanswered responses. Then the guest knows exactly what's at stake.
How long a reasonable deadline should be depends on how soon the table actually becomes available - should the deadline be shorter when the table frees up within minutes, and longer when it concerns the same evening or another day? Regardless, the deadline should be phrased as a specific time, not as 'as soon as possible', so the guest doesn't have to guess what that means.
Make the response easy to give
The guest should be able to respond with one word, such as 'yes' or 'no', or with a simple click. Lengthy explanations of how to confirm create friction precisely when time is short. Some restaurants send a link the guest can use without creating an account, so confirmation happens directly without the guest having to formulate a reply in their own words.
In TableBooking, the restaurant can create a booking link that the guest uses to confirm or decline the offer, without creating an account. The response appears in the dashboard together with other bookings, tables and guests, so staff find the overview in one place. This removes the need for the guest to formulate a written reply themselves.
Want to see how it works in practice?
Start with a free restaurant account and build your tables, opening hours and booking link at your own pace.
Start free