The standard restaurant birthday email arrives on the morning of the birthday and contains a free dessert. It is competing with several other birthday emails that landed the same morning, offering roughly the same dessert, at a point where the guest has already decided where they are going.
Occasion outreach is one of the few things in restaurant marketing where timing does more work than copy. Three to four weeks out, you are the restaurant that remembered. On the day, you are the eleventh dessert.
What follows is when to send, what to say, and where the dates come from — which is usually the part that stops people.
Why the day-of message cannot work
A birthday dinner or an anniversary is booked one to four weeks ahead. By the morning itself the decision is not merely made, it is confirmed, in a calendar, and somebody has arranged a babysitter.
So the day-of email arrives after the only decision it could have influenced. It converts occasionally, because somebody always has a second celebration, but it is fishing behind the boat.
It also has a subtler problem: it is the message every other restaurant sends, which means the guest reads it as a category rather than as a note from you. The thing that makes occasion outreach work — the sense that a person remembered — is exactly what the day-of blast destroys.
Where the dates come from
Nobody has an anniversary field filled in across their whole book, and no software will conjure one. The dates come from four places, worth going after in this order.
- Your booking notes. The words "anniversary," "birthday," and "celebrating" typed by whoever took the reservation. Search an export for them — this is the largest single source of occasion data in most restaurants and almost nobody mines it.
- The pattern. A guest who has booked the same week three years running has an occasion whether or not anyone wrote it down. You do not know which one, and you do not need to.
- What guests tell hosts. Currently walks out of the building at the end of the shift unless somebody writes it into the guest record within the hour.
- Asking. One question on a confirmation or a follow-up. Low yield, completely honest, and the only route that gives you an actual date rather than an inference.
The timing ladder
Three moments matter, and the last one is not a message at all.
T minus 3 to 4 weeks Ask. One short note, no offer. "Do you want me to hold something?" T minus 1 week Only if they booked. Confirm the detail — table, timing, and whether the occasion should be mentioned out loud at all. On the night Do the thing in the room. This is not a message. It is a table, a card, the somm already knowing. T plus 1 week Nothing. Resist this.
The anniversary ask
The register is a question rather than an offer. You are asking to be part of something instead of bidding for it, and the difference is audible.
Where the date came from a person, say so. It is the most persuasive sentence available to you and it costs nothing.
Subject: The 14th Hi James, You mentioned to Priya last time that October is your anniversary. She wrote it down, which is the entire reason you are getting this. If you are marking it here, tell me a night in the next week or so and I will hold the corner table before it goes. If you are going somewhere else this year, that is completely fine and I will stop emailing you about October. — Elena, Ember & Vine
The birthday ask, when you know less
Birthdays are more often self-reported and more often for a group, which changes the useful question. You are asking about the party rather than about the person.
Do not guess the size. A message that assumes a table for two when they wanted a table for fourteen has lost the booking more decisively than saying nothing.
Subject: November birthday — worth holding a table? Hi Priya, We have you down for a birthday in November. I have no idea whether that means two of you or fourteen, so I am asking rather than guessing. If it is a big one, give me a number and a night and I will see what we can hold. If it is two of you and you would rather nobody said a word about it, that is also a plan and I will note it down. — Marco
What actually happens in the room
Everything above is logistics. The part guests describe to other people happens on the night, and almost none of it needs a budget.
A card on the table in somebody's handwriting. The GM using the name without looking at a screen. The somm knowing what it is before anyone says. A dessert with nothing written on it in chocolate.
And the negative version, which matters just as much: ask in the confirmation whether they want it mentioned. Some people are marking an anniversary quietly, or marking one they would rather not have announced across a dining room, and a singing waiter is the worst thing that could happen to their evening.
When not to send
Occasion data goes stale in a way other guest data does not. A birthday does not change; a marriage might. A guest who booked an anniversary three years running and has vanished since may be celebrating it elsewhere, or may not be celebrating it at all.
Two rules cover most of it. Do not send occasion outreach to a guest who has lapsed entirely — send the win-back first and let them tell you they are still around. And stop after one unanswered year, quietly, without a final "we miss you" message.
Finding the occasions buried in your own booking notes, and knowing which of those guests are still active, is the sort of assembly work software should be doing for you. Deciding what to say three weeks out is not, and never will be.