Skip to content
PROOF48
All answers
automation

How the automatic birthday message actually gets sent, and what triggers it

An automatic birthday message needs four things: a stored birth date, a daily check that compares it with today's date, permission to email the person, and a channel, usually email. PROOF48's plans list email auto-responders and a CRM but no birthday feature, so a sender would be a custom automation.

Founder, PROOF48Updated 2026-10-316 min read

01The trigger is a date column and a daily check

A birthday message is not triggered by anything the customer does. It is triggered by the calendar. The usual build is a small job that runs once a day at a fixed hour in the business's time zone. It reads the contact list, picks the people whose stored month and day match today, drops anyone who has opted out or already received this year's message, and hands the rest to the email sender. Then it writes a record of what it sent, so a re-run cannot send twice. Someone has to decide what happens to 29 February birthdays. This is how such a job is typically built, not a published PROOF48 build. A loyalty message works the same way, with a count, such as the fifth visit, in place of a date.

  • Data: a contact record with month and day of birth, plus an opt-in status
  • Trigger: a job that runs once a day, in the business's time zone
  • Safeguards: skip opt-outs, skip anyone already sent this year, log every send
  • Decide the 29 February rule once, in writing
  • Loyalty messages: the same job, with a visit count instead of a date

02Where the date comes from, and what the law asks about it

The date has to be collected somewhere, usually a booking form, a checkout or a sign-up. GDPR Article 5(1)(c) says personal data must be adequate, relevant and limited to what is necessary for the purpose. That is how we read it: a birthday greeting needs the day and month, not the year of birth. Where you ask for consent, Article 7 says you must be able to demonstrate it, the request must be clearly distinguishable from other matters, and withdrawing must be as easy as giving it. In practice, store when and where each person agreed and the exact wording they saw. This is a summary of the regulation's text, not legal advice.

  • Ask for day and month only: data minimisation, Article 5(1)(c)
  • Say on the form what the date is for
  • Keep proof of consent: when, where and which wording (Article 7(1))
  • Withdrawal as easy as consent: an unsubscribe link in every email (Article 7(3))

03Whether the email is allowed to go out

Article 13(1) of the ePrivacy Directive allows electronic mail for direct marketing only to people who gave prior consent. Article 13(2) makes one exception: email details obtained from customers in the context of a sale may be used to market your own similar products, if customers get a clear, free and easy way to object when the details are collected and in every message. On 13 November 2025 the EU Court of Justice ruled in Inteligo Media (C-654/23), a Romanian case. As the law firm Pearl Cohen summarises it, a newsletter with a commercial purpose counted as direct marketing even with editorial content, and a free account could count as a sale. GDPR Article 21 adds the right to object to direct marketing at any time, which ends it. We found no source that settles whether a plain greeting with no offer is marketing. If yours carries a discount code, treat it as marketing, and ask a lawyer.

  • Prior consent is the rule for marketing email (ePrivacy Directive, Article 13(1))
  • Exception: contacts from a sale, your own similar products, a free and easy opt-out at collection and in every message (Article 13(2))
  • Inteligo Media, C-654/23, 13 November 2025, a Romanian case, as summarised by Pearl Cohen
  • A plain greeting versus an offer: no source found; with a discount code, treat it as marketing
  • A working unsubscribe in every email, honoured at once (GDPR Article 21)

04The channel: email is what PROOF48 can deliver

The AUTOMATE plan lists AI DM and email auto-responders, booking automation with a CRM and two custom automations a month. It does not list birthday messages, scheduled campaigns, or SMS or WhatsApp to your customers, and AUTOMATE does not cover WhatsApp or phone. A birthday sender would therefore be a custom automation: the contact data in a CRM, the daily job, and email going out. Our automation page says a single flow takes one to two weeks from mapping to production and that standalone builds are scoped and priced on request. Your email tool may already send on a date field. Check that before buying a build.

  • Listed in AUTOMATE (2,997 EUR a month): AI DM and email auto-responders, booking automation with a CRM, two custom automations a month
  • Not listed: birthday messages, scheduled campaigns, SMS or WhatsApp to your customers
  • Automation page: a single flow takes one to two weeks from mapping to production
  • Standalone builds are scoped and priced on request

05Where PROOF48 is the wrong choice

AUTOMATE is 2,997 EUR a month, which is the wrong spend for a birthday email alone. If your email tool can already send on a date, use it. If your customers live on WhatsApp or SMS, AUTOMATE is the wrong plan, because neither is in it. A WhatsApp sender would be a custom build, priced on request, and SMS is not listed on any PROOF48 page. If you hold no record of who agreed to hear from you, fix that first: no automation repairs missing consent. If you have a few dozen customers, writing to them by hand probably costs less. And if you need it in 48 hours, note that the 48-hour offer is a website of up to about five pages, not an automation.

  • AUTOMATE, 2,997 EUR a month: too much for a birthday email alone
  • WhatsApp or SMS customers: not in AUTOMATE; WhatsApp would be a custom build
  • No record of consent: fix that before automating anything
  • A few dozen customers: by hand is probably cheaper
From a build we shipped

A triggered email that exists, and what it is not

Rotiseria Baba Novac's ordering system is the nearest working example of a triggered email. Its write-up lists an order confirmation email on every order, sent through Resend, plus pickup slots and order tracking. The trigger there is an event, a placed order; the data is the order; the channel is email. A birthday email differs on the trigger, which is the calendar, and on the law: an order confirmation concerns a purchase the customer just made, while a birthday email with an offer is marketing and falls under the consent rules above. We have not built a birthday sender and publish no results for one.

See the build: Rotiseria Baba Novac

Questions, answered

What do I need to send automatic birthday emails?

A stored day and month of birth, a record of who agreed to hear from you, a daily scheduled check, an email sender and a working unsubscribe link.

Do I need consent to send a birthday email?

For marketing email, ePrivacy Article 13(1) requires prior consent, with a narrow exception in Article 13(2) for your own similar products to customers whose details you got in a sale. We found no source on whether a plain greeting counts as marketing. Ask a lawyer.

Can PROOF48 send birthday messages by SMS or WhatsApp?

Not inside AUTOMATE or any other plan. A WhatsApp sender would be a custom build, priced on request. SMS is not listed on any PROOF48 page.

How long does a birthday automation take to build?

We publish no measured time. Our automation page says a single flow takes one to two weeks from mapping to production, as its own figure.

Where PROOF48 fits

An automatic birthday message is a stored date, a daily check, a record of consent and an email sender. The build is simple; the consent and unsubscribe rules are the part to get right. PROOF48's plans list email auto-responders and a CRM but no birthday feature, so it would be a custom automation, and AUTOMATE does not cover WhatsApp or SMS: a WhatsApp sender would be a custom build, priced on request, and SMS is not listed on any PROOF48 page.

· Founder, PROOF48

Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.

Related articles

ai

How to automate follow-up messages without sounding like a robot

A follow-up message avoids sounding robotic when it names something specific and true about that exact customer's action, a pickup time, an order number, a batch that just landed, rather than a generic "thanks for your order" that could apply to anyone. The trigger can be fully automated; the content still has to reference the real, specific event.

Read it
automation

Automating order confirmations: WhatsApp, email, or both?

An order confirmation should arrive the moment payment clears, with the pickup time or delivery window stated plainly, and it should arrive on the channel the customer actually checks. Email is reliable, easy to automate through a transactional service like Resend, and works well when the order includes a receipt or an invoice.

Read it
automation

What "two custom automations a month" actually means

Two custom automations a month, the line inside PROOF48's AUTOMATE plan, means two workflows built specifically around how a business already operates, not two generic templates picked from a menu: connecting a booking system to a spreadsheet nobody wants to update by hand, or routing a specific kind of lead differently than the rest. AUTOMATE costs 2,997 EUR a month and bundles that allowance alongside a website chatbot, DM and email auto-responders, booking automation and a CRM.

Read it
automation

Is it actually safe to connect your business data to an automation tool?

It is as safe as the access you grant. An automation tool holds keys to your other systems, so give each connection the narrowest permission it needs, keep keys out of code and chat, check that incoming webhooks are signed, and review connected apps.

Read it