Restaurant marketing12 min read
Automated Guest Messages After a Visit: Birthdays, Win-back and Consent
Registration and service messages aren't marketing. Birthday greetings and come-back invitations are, and they need consent, an unsubscribe option and sensible limits.
A practical overview, not legal advice. Rules differ by country; check consent wording and procedures with an advisor.

After a visit, a guest can receive several kinds of message: a verification code when joining the loyalty programme, a booking confirmation, a welcome to the programme, a birthday greeting or an invitation to come back after a long absence. Each has a different purpose and different rules. When they get mixed up, consent becomes a problem and guests unsubscribe from everything at once. This overview is for owners and managers who want to automate communication after a visit. It separates registration and service messages from marketing, explains when you need consent, how to handle birthday greetings, win-back and sending limits, and describes what RestoCraft can do today. It isn't legal advice: rules differ by country, so check consent wording and procedures with a data protection advisor.
Five kinds of post-visit messages and how they differ
Before you set up any automation, sort your messages by purpose. The purpose decides whether you need consent, what the message may contain and how often it can go out.
Kinds of messages to guests after a visit
| Kind of message | Example | What it relies on | What to watch |
|---|---|---|---|
| Registration | A verification code when joining the loyalty programme | The guest asked for it | Don't add offers to it |
| Service | A booking confirmation, a welcome after completed registration | It responds to what the guest asked for | Once it contains a promotion or an invitation, it becomes marketing |
| Marketing | A coupon, a new menu, an event invitation | Consent, or an existing-customer exception where the law allows it | Recognisable as marketing, a named sender and an unsubscribe option in every message |
| Greetings | Birthdays, holidays, anniversaries | Safest to treat as marketing, because they promote the restaurant | The same rules as marketing |
| Win-back | An invitation to a guest who hasn't been back for a while | Marketing based on the guest's behaviour | Frequency, unsubscribing, a careful tone |
The line between a service message and a marketing message isn't always sharp. A purely service message sent to your own customer, containing only what they need, is generally not treated as marketing. But once you add a tip about the weekend menu to a booking confirmation, or a coupon for the next visit to a welcome e-mail, you push the message towards marketing. The practical rule: a service message contains only what the guest needs for what they asked for. Everything else belongs in messages the guest has consented to and can unsubscribe from.
Consent and marketing messages: what the rules say
In the EU, marketing by e-mail is governed by the ePrivacy Directive, which each member state implements in its own law. Its Article 13 allows e-mail for direct marketing only to people who have given prior consent. The exception is for existing customers: a business that obtained a customer's e-mail address in the context of a sale may use it to market its own similar products or services, provided the customer was clearly offered a free and easy way to object when the address was collected and in every later message. The directive also bans marketing e-mails that disguise or conceal the sender or have no valid address where recipients can ask for messages to stop, and it refers to the e-commerce rules on commercial communications. National rules add details and differ between countries; outside the EU, your local law applies.
The GDPR applies alongside. If processing relies on consent, you must be able to demonstrate that the guest gave it (Article 7, paragraph 1). A request for consent in a document that also covers other matters must be clearly distinguishable from them (paragraph 2), and withdrawing consent must be as easy as giving it (paragraph 3). A guest can object at any time to processing for direct marketing, and their data may then no longer be processed for that purpose (Article 21, paragraphs 2 and 3). Data must be limited to what is necessary for the purpose (Article 5, paragraph 1(c)).
A few practical consequences follow. Because you must be able to prove consent, confirm the address, for example with a confirmation link (double opt-in). Be careful about asking for consent by e-mail: such a request may itself count as a marketing message. And keep a list of contacts who have opted out or objected, and check every send against it.
For a restaurant this comes down to a simple principle: collect consent separately for each purpose, such as e-mail offers and birthday greetings. Collect it when the guest is actually dealing with you, at loyalty sign-up or when booking, and store when and how it was given. Whether the existing-customer exception covers a loyalty member who hasn't bought anything from you yet, and how your consent wording should read, is for an advisor in your country to assess. This article doesn't replace legal advice.
Birthdays: a greeting that is also marketing
A birthday message is pleasant for the guest and a natural reason for the restaurant to get in touch. From the rules' point of view, though, treat it as marketing: a greeting promotes the restaurant, and one with a gift or a dinner invitation promotes its services directly. So consent, clear identification as marketing and an unsubscribe option apply, as with any other offer.
A date of birth is personal data you need for this one purpose only. Ask for it only if you really send birthday messages, explain why, and consider whether the day and month without the year are enough. Giving a date of birth shouldn't be a condition of membership; a guest who doesn't give it simply won't get a birthday message.
Keep the content simple: a greeting, one gift and a clear validity period. A free dessert or a glass of something valid around the birthday is clearer than a percentage discount and gives the guest time to plan a celebration. Setting validity, minimum spend and usage limits is a topic for a separate article on restaurant coupons.
In RestoCraft, the birthday scenario („Narozeniny“ in the Czech admin) with an optional gift is in development. It runs only at pilot venues, sends e-mail only, and the loyalty programme issues the gift only after approval. Until then, a manager can issue a birthday coupon or privilege to a specific member manually in the Loyalty admin.
Win-back: inviting back a guest who hasn't visited for a while
A win-back message is for a guest who used to come and stopped. It isn't a mass discount but a personal reason to return. The key decision is after how long a silence to send it, and that depends on how often your guests usually come. A café whose regulars come several times a week notices someone drifting away sooner than a restaurant people visit for anniversary dinners.
A few principles that apply to win-back in any venue:
- contact only guests with marketing consent, and leave the others alone even if the message would suit them;
- one message, one offer, a clear end date;
- don't send the same guest a come-back invitation and a birthday greeting in the same week;
- after an unsubscribe, nothing goes out, not even a come-back invitation;
- measure the return (a booking or a visit), not e-mail opens.
A guest who stopped coming after a bad experience needs personal contact more than an automated offer; guest recovery, handling the problem before it ends in a public review, is a topic of its own. For the bigger picture of why caring for existing guests pays off, read our article on restaurant customer retention.
In RestoCraft, the scenario for a guest who hasn't visited for a while („Host dlouho nepřišel“) is in development. It works with an interval of 30, 60 or 90 days and an optional gift of points, a coupon, a benefit or a free item, which the loyalty programme issues only after approval. Like birthdays, it runs only in pilot and only by e-mail; it doesn't yet have a booking button directly in the e-mail. A come-back invitation after a cancelled booking or a no-show is also in development.
Sending limits and safeguards
Automation is safe only with safeguards that apply to all scenarios at once. Otherwise one guest gets a birthday greeting, a points reminder and a come-back invitation in one week, and unsubscribes from everything.
In RestoCraft, the guest return automation („Návrat hostů“) in pilot enforces four safeguards before every send. A message goes only to a guest with consent and a permitted e-mail contact. It isn't sent without a valid unsubscribe link, and unsubscribes and blocks are respected. Between 9 pm and 8 am local time, sending is postponed. And a guest receives at most one such message every 30 days. The restaurant sets the sender name and reply-to address in the communication centre („Centrum komunikace“).
Measure returns, not clicks. Today RestoCraft shows the status and delivery attempts of e-mails in the delivery history („Historie doručení“); it doesn't measure opens or clicks. Measuring returns after a message is in development and in pilot so far covers only invitations after a cancelled booking or a no-show.
What RestoCraft can do today and what is in development
In RestoCraft, communication after a visit is based on e-mail and on data from bookings, the QR menu, the loyalty programme and reviews. The status of the individual parts differs, so the overview separates what runs, what is in development and what isn't available yet.
Guest communication in RestoCraft by status
| Feature | Status | Note |
|---|---|---|
| Verification code when joining the loyalty programme | Running | E-mail immediately after the address is entered |
| Welcome e-mail after verified registration | Running | The welcome bonus is an optional programme setting |
| Booking confirmation by e-mail | Running | A service message for the booking |
| Communication centre | Running | Templates with variables, preview, test e-mail, sender and reply-to address |
| Delivery history | Running | Status and delivery attempts of e-mails |
| A case for the team after a low rating | Running | Guest Recovery in ReviewHub, if switched on |
| Manually issuing a coupon, points or a privilege | Running | In the Loyalty admin |
| Birthday, guest hasn't visited for a while, points expiring soon | In development | Pilot venues only, e-mail only, with approval |
| Review request by e-mail after a visit | In development | Pilot |
| Booking reminder | Not available | Not sent today |
| SMS and messages through the Wallet card | Not available | The Wallet card is only updated |
| Open and click tracking | Not available | Delivery is measured |
Guest Retention Automation is listed in RestoCraft's product registry as a module whose availability is still being verified, and it isn't offered on its own yet. Guest communication has a documented e-mail channel; neither SMS nor other providers have been verified. RestoCraft's restaurant marketing service is also still being verified, so the scope of cooperation is agreed with each restaurant individually.
Rollout step by step
Start automated communication with a list of what you already send, not with a tool. A sequence that works in venues of any size:
- List every message that goes out to guests, and its purpose.
- Separate registration and service messages from marketing, and remove offers from service messages.
- Prepare consent wording separately for each purpose and have an advisor check it.
- Decide where guests give consent, for example at loyalty sign-up or when booking, and where the consent record is stored.
- Set up unsubscribing, the list of contacts who have opted out, a frequency cap and quiet hours.
- Start with one scenario, such as birthdays, and add come-back invitations once the first runs smoothly.
- After the first month, review unsubscribes and complaints, not just the number of returns.
An automated message only works as an addition to what the guest experiences in the restaurant. Why guests come back even without discounts or advertising is the subject of our article on getting repeat customers for a restaurant.
Frequently asked questions
The confirmation itself is a service message: the guest asked for the booking and the confirmation belongs to it. Once you add an offer or an event invitation to it, treat it as marketing.
That is risky: an e-mail asking for marketing consent may itself count as marketing, so sending it to people without consent can break the rules. It is safer to collect consent where guests deal with the restaurant: at loyalty sign-up, when booking or at the table. Check with an advisor what options you have with existing customers.
Joining the programme and consenting to marketing are two different things. The GDPR requires a request for consent to be clearly distinguishable from other matters, and when assessing whether consent is freely given, account is taken of whether a service is made conditional on consent that isn't necessary for it. So set up registration so that a guest can join the programme without agreeing to receive offers.
The rules above don't set a number; guest expectations do. Start with a cap per guest that applies to all scenarios together, and adjust it based on unsubscribes and reactions. In pilot, RestoCraft sends at most one guest return message every 30 days.
Key takeaways
Registration and service messages aren't marketing; an offer turns them into marketing.
Birthday greetings and come-back invitations are marketing and need consent or another legal basis.
Collect consent separately for each purpose and store when and how it was given.
Every marketing message is recognisable as such and has a sender and an unsubscribe link.
Set the frequency cap and quiet hours for all scenarios together.
RestoCraft's automated scenarios are still in pilot and e-mail only.
Rules differ by country; check consent wording and procedures with an advisor.
Conclusion
Automated communication after a visit works when every message is classified by purpose: registration and service messages inform, while marketing messages, including greetings and come-back invitations, make offers and need consent, clear identification and an unsubscribe option. Start with a list of your messages, separate consent by purpose, set the safeguards for the whole venue and launch one scenario. Before going live, have a data protection advisor in your country check the consent wording and procedures; this overview describes practice, not a legal conclusion.

