What to Include in a Restaurant Booking Confirmation
The confirmation is the one message every guest opens. Here is what belongs in it, what quietly prevents problems on the night, and what you should keep out of it.
A booking confirmation is the highest-open-rate message your restaurant will ever send. The guest has just made a decision, they are waiting for proof it worked, and they will open it within seconds. Many of them will open it again in the car park on the night. Nothing else you send comes close.
Most confirmations waste it. They say "thanks for your booking", repeat the date, and stop. Everything the guest actually needs an hour before service — the address, a number they can tap, whether you hold the table, how to cancel without phoning — is missing, so it arrives as a phone call to your host stand instead.
The non-negotiables
These belong at the top, above anything else, in a block the guest can read in one glance on a phone screen.
- Your venue name. Obvious until the guest has three confirmations in their inbox from a weekend away and is scrolling to find yours.
- The date with the day of the week written out. "Saturday 14 March" is checkable at a glance. "14/03" is not, and a surprising share of wrong-date arrivals start with a guest who read the number and assumed the day.
- The time and the party size. Together, on one line, in the same sentence.
- A booking reference. Short enough to read aloud over a noisy phone line. It saves your host spelling out surnames and it gives the guest something to quote.
- The full postal address. Written out, not only linked. A guest with poor signal outside can still read text, and they can paste it into whatever map application they actually use.
- A tappable phone number. The single highest-value element in the whole message. Running late, lost, party shrunk by one — all of it resolves in ten seconds if the number is one tap away.
Read it on a phone before you approve it
Send the confirmation to yourself and open it on the oldest phone in the building, in daylight, one-handed. If you have to pinch to read the time or scroll to find the address, it is not finished.
The details that prevent problems
This is the section most restaurants skip, and it is the one that removes work from your floor team. Each line below exists because something goes wrong when it is missing.
- Arrival window and table-hold policy. Say plainly how long you hold the table — fifteen minutes is a common rule of thumb — and that a call will usually keep it longer. Guests who know the rule ring you. Guests who do not simply arrive late and argue.
- Last seating or table duration, if you run one. If a 7pm table is needed back at 9pm, that has to be in the confirmation and not delivered by a server at 8:45.
- Cancellation policy and the deadline. A specific time, not a vague request. "Please cancel by 3pm on the day" is actionable.
- Deposit or card-hold terms, if any. How much, when it is taken, what triggers a charge, and how it is applied to the bill. This is the one place a dispute is genuinely expensive, so write it in short sentences.
- Parking and access notes. Where to park, whether the entrance is the obvious door, step-free access, and which floor you are on if you are not at street level.
- Dress code — only if you actually enforce it. If you have never turned anyone away, leave it out. A dress code you do not enforce only makes guests anxious and makes your team look inconsistent when they wave someone through.
The one-tap actions
Three buttons do more for your covers than any wording change.
- Cancel. Counter-intuitive to put in a confirmation, and the most valuable thing in it. A guest whose plans changed will either cancel in one tap or say nothing at all — those are the two realistic outcomes, and one of them gives you the table back.
- Modify. Party-size changes are the most common amendment by a wide margin. Letting the guest drop from six to four without phoning you saves a call and keeps your covers accurate.
- Add to calendar. The cheapest no-show prevention available. A booking in a calendar with an alert competes with the other things in that calendar; a booking in an inbox does not.
These are also the actions that stop your inbox becoming a reservation queue again, which is the failure mode described in How to Stop Managing Restaurant Reservations Through Email.
What to leave out
The confirmation gets opened because it contains something the guest needs. Every element that is there for you rather than for them costs you a little of that attention.
- Marketing offers. A voucher for a future visit, before the current visit has happened, reads as a shop rather than a receipt.
- A newsletter signup as the primary call to action. If you want one, put it in a small line at the very bottom, below the booking details and below the cancel link.
- A wall of text. Terms, allergen policy, the story of the building — link to them if you must, do not paste them in.
- An image-only email. Designs built as one large graphic break when images are blocked, break in dark mode, and cannot be read by a screen reader. The critical details must exist as real text.
- Anything that pushes the cancel link below three screens of scrolling. If cancelling is hard, guests do not cancel, they simply do not turn up.
Subject lines
The subject line has one job: make the message findable three days later in a full inbox. Put the venue, the day and the time in the first forty characters, because that is roughly what a phone shows in a list view.
- Good: "The Harbour Rooms — Sat 14 Mar, 7:30pm, 4 guests"
- Weak: "Your reservation is confirmed"
- Bad: "Thanks for booking with us" — no detail at all, so the guest has to open it to learn anything and cannot find it later
Keep the same structure for the reminder so both messages sort together when the guest searches your venue name.
SMS versus email
Email is where the full confirmation lives. SMS is where the reminder lands. Send both when you have both, and let each do the thing it is good at rather than duplicating one inside the other.
A text message gives you roughly 160 characters before it splits, and guests read it on a lock screen. That constraint forces a useful discipline: venue, day, time, party size, and one link. Nothing else fits, and nothing else is needed, because the link opens the full booking with the address, the phone number and the cancel action already on it.
Do not put the whole policy in a text
A three-part SMS containing your cancellation terms costs you three times the send and gets read as spam. Put one short line and a link. The terms live at the other end of the link where they can be read properly.
The reminder is a separate message
Do not try to make the confirmation do reminder duty. Send it separately, and time it so the guest can still act on it.
- For a booking made more than a week ahead, one reminder the day before, late morning or early afternoon.
- For a booking made the same day, no reminder at all — you will only annoy someone who is already on their way.
- For large parties, set menus and anything with a deposit, a reminder two to three days out so changes still leave you time to resell the table.
- Always include the cancel link. A reminder without one is a message that says "we are expecting you" and gives the guest no way to say otherwise.
Wording matters more here than in the confirmation. How Independent Restaurants Can Reduce Missed Bookings goes through how to phrase a reminder so cancelling feels easy rather than shameful.
Getting the small details right
Three formatting decisions cause almost all of the confusion in confirmation messages, and all three are worth ten minutes of your time once.
- Time zone. Times should always be the local time at your venue, and should say so if you take bookings from abroad. A guest booking from another country on a phone set to their home clock will otherwise read your 8pm as theirs.
- Clock format. Pick 24-hour or 12-hour and use it everywhere — the confirmation, the reminder, the website and the door sign. Mixed formats are how a 7pm booking becomes a 19:00 argument.
- Unambiguous dates. Never numeric-only. "Saturday 14 March 2026" cannot be misread by an American, a European or anyone half-reading on a train. "03/14" and "14/03" both can.
An example worth copying
Here is a complete confirmation as a list of lines. It fits on one phone screen with the cancel link visible, and there is nothing in it that is not doing work.
- Subject: The Harbour Rooms — Sat 14 Mar, 7:30pm, 4 guests
- Your table is booked.
- Saturday 14 March 2026, 7:30pm, 4 guests
- Reference: HR-4821
- The Harbour Rooms, 12 Quay Street, Bristol BS1 4AB
- Call us: 0117 496 0000
- We hold your table for 15 minutes. Running late is fine — give us a ring and we will keep it.
- Plans changed? Cancel by 3pm on the day, free of charge: [Cancel booking]
- Need a different time or party size: [Change booking]
- [Add to calendar]
- Parking: the Quay Street car park is two minutes away and free after 6pm. Step-free entrance on the left of the main door.
- Anything we should know — allergies, a birthday, a pushchair? Reply to this email or ring us.
Set it up once
This is configuration, not copywriting you repeat. In Seatingly the confirmation and reminder templates live with your widget settings, so the arrival window, cancellation deadline and access notes are written once and appear on every booking. See Customize booking widget for where those fields sit.
Review the wording twice a year, and every time your opening hours, parking situation or cancellation policy changes. A confirmation that tells guests about a car park that closed last spring is worse than one that says nothing.
