Reservations and table management

Booking confirmation messages: what to include

What a restaurant booking confirmation should say: the details, the policy line, an allergen prompt and an easy way to amend, with email and text examples.

Ava research teamPublished 7 min read

On this page
  1. What a confirmation is for
  2. The essential fields, in reading order
  3. The allergen and dietary prompt
  4. An email template you can adapt
  5. The text message version
  6. Confirmations for bookings that need more
  7. Mistakes that cause calls and no-shows
  8. Phone bookings need a confirmation too
  9. Policies: say it once, plainly
  10. Keep marketing out of the confirmation
  11. Test your confirmation in five minutes
  12. Frequently asked questions
  13. References

Key takeaways

  • A confirmation has three jobs: prove the details, set expectations and make changing the booking easy.
  • Put the day, date, time, party size and name at the top, in that order. Everything else comes after.
  • Invite allergy details in writing as well as at the table: 86% of diners trust written allergen information, against 60% for verbal[1].
  • Keep promotions out of the confirmation. Marketing emails and texts need prior consent under PECR[2].

What a confirmation is for

Most guests read a confirmation once, quickly, on a phone. It has to prove the booking exists, show the details clearly enough that a mistake jumps out, and make changing plans easier than simply not turning up. Operators value this contact: in OpenTable’s research, 43% of restaurateurs named confirmation reminders as the most effective way to reduce no-shows[3]. Platform data is more cautious. The Resos No-Show Index found confirmation prompts on their own roughly neutral for no-shows, while a delivered SMS reminder was linked to a 16% lower recorded rate[4].

The practical reading: the confirmation sets the booking up correctly and opens a channel for changes, and the reminder nearer the date does more of the work on attendance. The guide to reminder texts and emails covers timing.

The essential fields, in reading order

What to include in a booking confirmation, from top to bottom
FieldWhy it mattersExample wording
Day and dateGuests mishear dates far more often than daysSaturday 14 November
TimePick one clock format and use it everywhere19.30 (7.30pm)
Party sizeCatches a four-or-six error before the nightTable for 4
Name on the bookingLets the host find it quicklyBooked under: Patel
Address and map linkSaves calls asking for directions12 Market Street, with a map link
Table time, if limitedAvoids a dispute at the end of the mealYour table is yours for 2 hours
Deposit or card detailsSays what was taken, why and when it is refundedDeposit refundable up to 48 hours before
How to amend or cancelTurns a would-be no-show into a cancellationUse the link, reply to this email or call us
Allergen and dietary promptGives the kitchen time to planTell us about any allergies before you arrive
Access and family needsGets the right table and a high chair readyNeed step-free access or a high chair? Let us know

If a field does not apply, leave it out rather than writing “N/A”. A shorter message with the right details is read more carefully than a long one.

The allergen and dietary prompt

Allergen law is mostly about what you tell guests about the food, but booking is the moment you can learn what guests need. The Food Standards Agency advises that written allergen information, supported by a conversation, works best for consumers[5]. Diners agree. In 2025, 86% were confident in allergen information provided in writing, against 60% for information given verbally by staff[1].

Diners’ confidence in allergen information, by how it is given (2025)Share very or fairly confident
Diners’ confidence in allergen information, by how it is given (2025)Comparison. Written information: 86%; Verbal information from staff: 60%.86%Written informationWritten information: 86%60%Verbal information from staffVerbal information from staff: 60%Diners’ confidence in allergen information, by how it is given (2025)Comparison. Written information: 86%; Verbal information from staff: 60%.86%Written informationWritten information: 86%60%Verbal information from staffVerbal information from staff: 60%

Source: Food Standards Agency, 2025[1]

Show the data
ItemValue
Written information86%
Verbal information from staff60%

Word the prompt so it invites detail without promising more than the kitchen can deliver: “Please tell us about any food allergies or intolerances in your party before your visit. We’ll go through them with you at the table too.” Then make sure the reply reaches the notes the kitchen reads on the night. The guide to booking notes the kitchen and floor actually use sets out a tagging scheme.

An email template you can adapt

Example. Subject line: “Your table at The Larder, Saturday 14 November, 19.30”. With the details in the subject, the guest can check the booking without opening the email. The body follows this order:

  • Opening line: “Thanks, Priya. Your table is booked.”
  • Details block: Saturday 14 November, 19.30, table for 4, booked under Patel.
  • Where to find us: address, map link, nearest station and a parking note.
  • Good to know: “We hold tables for 15 minutes. Running late? Call us on the number below.”
  • Your needs: the allergen prompt plus one line on step-free access, high chairs or a quieter table.
  • Changes: a single amend-or-cancel link, the phone number and the cut-off for changes.
  • Sign-off: the venue name and, if possible, a named person.

The text message version

Texts get read sooner than emails, so keep the SMS to essentials and link to the rest. Example: “The Larder: table for 4, Sat 14 Nov, 19.30, name Patel. Allergies or access needs? Reply or call us. To change or cancel: [short link].” Fit it in one message if you can, avoid abbreviations that read like spam, and send from a sender name guests will recognise.

If a guest booked by phone, the text matters even more. It is the first written record they have, and the first chance to spot that you heard the 15th when they said the 14th.

Confirmations for bookings that need more

A table for two on a Tuesday needs the basics. Some bookings need more, and the confirmation is the place to set them out so nothing is left to a phone call on the day.

  • Large groups: the final-numbers deadline, the pre-order link and deadline, whether a set menu applies and whether a service charge is added to the bill.
  • Private dining and exclusive hire: room name, access time, minimum numbers, what is included, the payment schedule and a named event contact.
  • Prepaid or tasting menus: the start time (and that late arrivals join the menu where it has reached), what the payment covers, and the dietary questionnaire with its deadline.
  • Outdoor tables: what happens if the weather turns, and whether you can guarantee an indoor table.
  • Children: whether high chairs are reserved, and whether there is space for a buggy at the table.

Write these as a short “Good to know” block under the main details rather than a wall of text. If the guest needs to do something by a date, put the date in bold-free plain words near the top: “Please send final numbers by Thursday 12 November.”

Mistakes that cause calls and no-shows

  • Sending from a no-reply address, so a guest who wants to cancel has nowhere to write.
  • Showing only the date in numbers (14/11), which some overseas visitors read the other way round.
  • Burying the amend link at the bottom under the marketing footer.
  • Different wording from different channels, so guests who booked by phone get less detail than those who booked online.
  • No confirmation at all for phone bookings, which leaves the guest relying on memory.
  • Policy text copied from another venue that does not match what your staff actually do.

Each of these generates a call during service, a dispute at the table or a guest who quietly stays at home. Fixing them takes an afternoon.

Phone bookings need a confirmation too

Bookings taken by phone are the ones most likely to go without written confirmation, and the ones most likely to contain a misheard detail. Close the gap with a routine: read the booking back, ask for a mobile number and an email address, and send the same confirmation the website would send before the next call comes in. If the guest has no mobile or email, note that on the booking so the host knows a reminder call may be needed.

Example. A fictional neighbourhood restaurant finds that most of its diary disputes involve phone bookings. It adds a two-line closing script to every call (“I’ll text you the details now. If anything looks wrong, just reply.”) and checks the next morning that every phone booking has a confirmation logged. Within a month, the arguments at the door about times and party sizes are rare enough that the manager stops counting them.

Policies: say it once, plainly

If you take a deposit, store card details or limit table times, the confirmation must say so in plain words, with a link to the full terms. Charges buried in small print are where disputes start. Keep the policy line short and specific: what is charged, when, and how the guest avoids it. See booking terms and conditions in plain English and wording your no-show policy for the detail.

Keep marketing out of the confirmation

A confirmation is a service message about a booking the guest made. Adding a newsletter offer or a promotion changes its character. Under PECR, marketing emails and texts to individuals need their prior consent[2]. The soft opt-in lets a business market its own similar products to people whose details it obtained during a sale or negotiation[2], provided they were given a simple way to opt out when their details were collected and in every message afterwards.

The safe pattern: the confirmation carries booking information only, and marketing consent is a separate, unticked choice at the point of booking. That keeps the confirmation deliverable to every guest, including the ones who said no to marketing.

Test your confirmation in five minutes

  1. Book a table yourself

    Use every channel you offer: website, phone and each platform. Check that every route sends the same confirmation.

  2. Read it on a phone

    If the day, date, time and party size are not visible without scrolling, move them up.

  3. Try to amend it

    Follow the change link. If it needs more than two taps or asks for a password, simplify it.

  4. Reply to it

    Check that replies reach an inbox someone watches, not a no-reply address.

  5. Check the allergy route

    Send a test allergy note and confirm it appears on the booking the kitchen sees.

Frequently asked questions

Should a restaurant send booking confirmations by email or text?

Both if you can. The email carries the full details and policy; the text carries the essentials and a link. Many guests act on the text first.

How soon after booking should the confirmation arrive?

Straight away. A delay makes guests wonder whether the booking went through, and some will book a second venue as a back-up.

Can I add a promotion to a booking confirmation?

Keep it out. Marketing emails and texts need prior consent under PECR unless the soft opt-in applies[2]. Ask for marketing consent as a separate choice.

If a guest told us about an allergy in advance, do we still ask at the table?

Yes. The FSA advises written information supported by a conversation[5]. The advance note lets the kitchen plan; the conversation confirms it.

References

  1. Food Standards Agency (2025). Food and You 2 Annual Report: Wave 11 (2025) (opens in a new tab) ↑

  2. legislation.gov.uk (The National Archives) (2003). The Privacy and Electronic Communications (EC Directive) Regulations 2003, regulation 22 (opens in a new tab) ↑

  3. Restaurant Online (2026). No-show rates fall year-on-year, report finds (OpenTable Restaurant Impact Report) (opens in a new tab) ↑

  4. Resos (2026). Restaurant no-show rate: the Resos No-Show Index (opens in a new tab) ↑

  5. Food Standards Agency (2026). Allergen guidance for food businesses (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo