Restaurant Birthday Marketing
A birthday is a booking waiting to be asked for. Four messages over five weeks, each one doing a different job — and none of them sent to somebody who did not agree to hear from you.
Why it matters
A birthday is the one occasion a year when somebody is actively looking for somewhere to take eight people, and they decide roughly a month before. Almost every restaurant that does anything about this sends a voucher on the day itself, which is several weeks after the decision was made and to a person who is already somewhere else.
The party is the prize, not the guest. One birthday dinner is a table of eight who did not otherwise have a reason to come, most of whom have never been. Treating it as a discount for one person misreads the whole occasion.
So it is planned like a booking rather than sent like a coupon: several touches, spread out, each one doing something different, with the ask arriving while the decision is still open.
Four messages, five weeks
Thirty days before — ask for the party
The only one of the four that is really a sales message, and it is the one almost nobody sends. It arrives while they are still deciding where to go, and it asks about a table rather than offering a free drink.
Three days before — a nudge
For the ones who meant to book and did not. Short, no new offer, just a reminder that the date is close and the room is not.
On the day — just happy birthday
No offer, no call to action, no link to a booking form. A message that wants something on somebody's birthday is a message they remember for the wrong reason.
A week after — the gift is still there
The one that recovers the people who spent their birthday elsewhere. The occasion is over, the offer is not, and there is no longer anything to compete with.
What the venue actually chooses
The offer, in your own words
Free text rather than a template, because a birthday message that reads like software is worse than none. What the guest reads is what you wrote.
A party package, when it fits
The thirty-day message can quote a set menu with a per-head price and a minimum party size, so somebody organising for eight gets a number rather than an invitation to enquire.
Which of the four to send
None of them is compulsory. A venue that only wants the thirty-day ask can run that alone.
A code they can read out
Every message that carries an offer carries a code, and the code is honoured by a person rather than applied by a till. Nothing here comes off a bill automatically.
The rules it obeys
Two, and both are enforced rather than advised. Consent comes first: this is unsolicited mail, and the only thing that makes it defensible is that the guest agreed to it, specifically, for this venue. A guest who consented to hear about events has not consented to birthday offers.
Then frequency. Birthdays draw from the same allowance as everything else — two contacts per guest per month across the whole system. A guest whose birthday falls in a month when you also ran an offer does not get four emails; the cap decides, not the campaign. Marketing covers how both work, and Personal Offers covers the campaigns that share the allowance.
Common questions
Where do the birthdays come from?
From guests who gave you one. There is no way to infer a birthday and no list to buy — which is also why the thirty-day ask matters, since a guest who tells you is a guest expecting something.
Do we have to send all four messages?
No. Each is optional. The thirty-day one is the one worth keeping if you only send one.
Why is there no offer in the message on the day?
Because a message that wants something on somebody's birthday reads as a transaction. The offer is in the other three.
Can we quote a set menu for the party?
Yes — the thirty-day message can carry a package with a per-head price and a minimum party size, so an organiser gets a real number.
What if a guest's birthday lands in a busy marketing month?
The frequency cap applies first. Two contacts per guest per month, across birthdays, offers and event invitations together.
Is the birthday discount applied automatically?
No. It arrives as a code and somebody honours it at the table.