Tuesday at 6:30 PM is the hardest seat to fill in American casual dining. The Birthday Club automation solves that problem by turning every diner’s birthday into a 14-day-ahead, party-of-four-minimum, slow-night booking trigger. Free dessert is the hook. A guaranteed $80-$140 cover is the outcome.
What it ships with
- GHL workflows:
Birthday – T-14 Day Send,Birthday – T-3 Day Reminder,Birthday – Redemption Tracking,Birthday – Expiry Sweep - Birthday capture form (web, host stand tablet, POS signature screen)
- Pre-written SMS templates: invitation, reminder, redemption confirmation, expiry nudge
- Custom fields:
birthday_month_day,birthday_offer_sent_at,birthday_offer_redeemed,birthday_party_size - Slow-night logic: offer skews Tuesday/Wednesday/Thursday redemption by default
- Party-size minimum: 4 guests (operator-tunable down to 2 or up to 6)
The flow (step-by-step)
1. Birthday captured
At booking, at the POS signature screen, or via a “join the birthday club” web form, the diner’s birthday_month_day is stored as MMDD (no year, no PII bloat).
2. T-14 send
14 days before the birthday, an SMS fires: “Happy almost-birthday, [first_name] — your free dessert is on us. Book a table of 4+ between [date range] and we’ll bring the cake. Reply BOOK to grab a time.”
3. Slow-night steering
The offered date range deliberately excludes Friday and Saturday prime time. Tuesday-Thursday dinner and Sunday brunch are the default redemption windows because that is where the empty seats live.
4. T-3 reminder
If birthday_offer_redeemed is still false 3 days before the birthday, a softer reminder fires: “Three days left to claim your birthday dessert — reply BOOK or call us.”
5. Redemption at the table
The server fires the comp dessert from the POS. The closing-check webhook flips birthday_offer_redeemed to true and triggers a thank-you SMS within an hour of the check closing.
6. Expiry sweep
7 days after the birthday, unredeemed offers expire automatically. No stale comps floating in the system. The contact stays in the loyalty pipeline normally.
What you can expect
Operators typically see a 22-35% redemption rate on birthday SMS — strong for any restaurant offer. Because the minimum party size is 4, a single redemption brings 3 paying guests at the going-rate check average. Slow-night fill rate (Tuesday through Thursday dinner) climbs measurably inside the first full birthday cycle. Cake-with-a-candle photos get posted to Instagram by the guests themselves — free FOH-generated social content.
Setup & customization
Pre-built: every workflow, every SMS, the slow-night calendar logic, and the redemption tracking.
What you tweak in 10 minutes: the dessert offer copy (some operators use a free app instead), the party-size minimum, the redemption date range (default is birthday-week Tuesday through following Sunday), and the reminder cadence.
Compliance notes
Birthday SMS runs on a 10DLC-registered campaign. Diners opt in explicitly when joining the club — the web form and POS signature screen both capture timestamped consent. STOP removes the contact from the birthday workflow and every other marketing sequence. Storing only month and day (not full birthdate) keeps PII surface area minimal. No COPPA exposure because the snapshot does not collect data on anyone under 18 by design — the birthday form is gated by an age-check checkbox.
Turn empty Tuesdays into booked tables of four. Get the Restaurant Snapshot for $997 full or $997 lite, with a 30-day money-back guarantee. Buy now or book a walkthrough to see a birthday SMS land on your own phone.