Birthday Email for Restaurants

A restaurant birthday email has one job: fill a table this month that would have stayed empty. The trigger is the birthday date a guest hands over at the host stand, on a reservation form, or in your loyalty signup. You send once a year, and you send early. Ten to fourteen days before the date beats day-of every time, because a birthday dinner gets booked ahead. Send on the day and the guest has already made plans elsewhere.

The offer is a comped dessert, not a discount code. A slice of olive oil cake runs you four to eight dollars in food cost and pulls a whole table. Birthday parties average three to four guests and run a check roughly thirty percent higher than a normal two-top, between drinks, courses, and the second bottle. That trade, four dollars of cake for a party of four, is why restaurant birthday flows consistently post the highest open rate of any automated email in the channel, often in the thirty-five to fifty percent range.

The copy sounds like a person who works in the room. The eyebrow reads "From our kitchen." The headline names the date: "Your birthday's in 10 days. We saved you a table." The body comes from the chef, not the brand. Giulia, Chef and Owner, signs the note. No "exclusive offer," no "unlock your reward." A guest reads it and forwards it to the friend choosing the restaurant.

The call to action is "Reserve your table," and it points at your booking page, not a checkout. Wire it to Resy, OpenTable, or Tock, and prefill the party size if you can. The fine print carries the real terms: complimentary dessert with an entree, dine-in only, valid during the birthday month, one per guest, parties of six or more call the host stand. CAN-SPAM still applies, so the footer carries the street address and an unsubscribe link. Honest terms and a real address are what keep the offer from reading as bait.

Restaurant lists are messy. A guest who signed up at the host stand opens your email in Gmail on a Pixel, the owner checks it in Outlook on Windows, and the regular who actually comes in reads Apple Mail in dark mode on an iPhone. This template holds up in all three because it follows email rules, not web rules.

The layout is one 600px table centered inside a full-width background table, with nested tables carrying each section. Every style sits inline on its element, so no client can drop a stylesheet and collapse the design. The wordmark, headline, chef note, and fine print are live text, not images, which means they stay sharp when images are blocked and they resize on a phone. There is exactly one mobile media query, which is all most clients honor.

The button is bulletproof. MJML renders it as a styled link with fixed width and line height for Gmail and Apple Mail, and as VML roundrect markup for Outlook, which uses Word to draw HTML and ignores border-radius and padding on links. Without that VML fallback the button shows up in Outlook as a thin underscore with no background. The head carries the MSO conditional block, a 96 DPI fix, and color-scheme meta set to light and dark, so dark-mode clients get the hint and do not invert the cream ground into blue-gray. The hero carries real alt text, and the web font falls back to Helvetica and Arial where it does not load.

Open the MJML below, or copy the rendered HTML once you compile it. In Klaviyo, start a new email, choose to start from HTML, and paste the full markup. In Mailchimp, start a campaign, pick "Code your own" then "Paste in code," and paste it there. The table structure survives the import in both.

Now make it yours. Swap "COPPA ROSSA" for your restaurant name, drop the hero image URL for a photo of your own room or signature dish, and point the button at your reservation link. Then wire the merge tags. In Klaviyo the first-name tag reads {{ first_name|default:'friend' }} and the reservation link can sit in a profile property or a custom field. In Mailchimp the first-name tag reads *|FNAME|* and the birthday field is *|BIRTHDAY|*, which Mailchimp's built-in birthday automation uses to fire this campaign once a year.

Set the flow to send ten days before the birthday date, and add a second nudge three days before for anyone who did not click. A reminder lift of fifteen to twenty-five percent is normal. Last, test before you send. Run a proof through Gmail, Apple Mail, and the Outlook Windows desktop client, and open it once more in dark mode on a phone. If the cream background, the brick-red button, and the chef note all hold, ship it.