8 Guest Journeys That Bring Restaurant Guests Back
A guest’s relationship with a restaurant doesn’t end when they leave the table. The weeks between visits, a birthday, a cancelled reservation, or an event booking all create opportunities to bring them back. Guest journeys help restaurant groups act on those moments automatically, sending the right message at the right time to encourage another visit.
What are guest journeys, and why run them in Loyalist?
A guest journey is an automated series of messages triggered by guest behavior or profile, such as a first visit, 60 days without a visit, or a birthday. Journeys help restaurant groups stay in touch with guests at the right moments without relying on staff to send each message manually.
Loyalist supports guest journeys through:
- Automated email and SMS: Build multi-step journeys that send messages based on guest activity.
- Conditional branches: Change the next message based on who the guest is and what they’ve done, including their spend tier, visit history, tags, or a random A/B split.
- Manager approval: Review and approve a journey before it goes live.
- One guest profile across locations: Run journeys using a shared guest record, so someone who visits three restaurants in the group isn’t treated as three separate guests.
- Reservation and POS data: Trigger messages based on actual visits and purchasing behavior across connected systems.
- Booking and revenue attribution: See how many bookings and how much revenue each journey generates.
As of November 2026, Loyalist journeys had driven $14.4 million in attributed revenue since March 2026, across more than 1,000 active journeys at 138 groups.
The eight journeys below are practical starting points, with different options depending on a group’s marketing goals and operating needs.
1. Welcome series: a thank-you that sets up the second visit
The welcome series is a short run of messages that fires when a guest dines for the first time. We suggest a thank-you email the day after, then a nudge toward a return visit about two to three weeks later. Keep the thank-you short and personal to the venue they visited. Name the room or the chef, and skip the discount.
Do it because a first visit is the only moment a stranger becomes a regular, and most guests hear nothing after the check closes. Guests who don’t have a reason to return after their first visit may choose another restaurant instead. The second message can invite guests back to experience another part of the menu or try out a dish they missed.
The gap is large. A June 2026 Bloom Intelligence analysis of nearly a million first-time guests found that about 85% had exactly one recorded visit, and only about 1 in 7 came back even once. In Loyalist platform data, post-visit thank-you journeys earned $8 million in attributed revenue since March 2026.
2. Lapsed regular win-back: catch regulars before they are gone for good
A win-back journey identifies regulars who haven’t visited in a while and gives them a reason to return. Start by defining what counts as a regular for each concept, then set an inactivity threshold that reflects how often those guests typically dine. For example, a neighborhood bistro might consider someone a regular after six visits in a year, while a tasting-menu restaurant might use two.
Once a regular goes beyond their expected visit interval, trigger a personal follow-up. Write the message in the GM’s voice and mention a dish the guest usually orders when that information is available.
Do it because regulars rarely say goodbye. They just stop booking, and at a group with several concepts nobody on the floor notices when a weekly regular at one room goes quiet.
A DataDelivers analysis of more than 50 million guests found that only 1 in 5 customers return within one year. The same Bloom Intelligence analysis found that only about 1 in 32 first-time guests became a frequent regular, so each regular you lose is hard to replace. Loyalist’s lapsed regular journey brings back 15% of guests on average and up to 30% for the best journeys.
3. Birthday: invite guests early enough to book the celebration
A birthday journey works best as an invitation sent about a week before the date, so the guest has time to plan and book. A note on the day itself usually arrives after the dinner plans are made. Resy keeps a birthday field on the guest profile, and the Resy integration page lists it among the fields that sync into a guest record, so the data often already exists.
Do it because a birthday is one of the few nights when guests choose a restaurant on purpose, and often for a group. If your invite does not reach them, the party books somewhere else.
4. Anniversary: the same invite, built on dates from reservations
An anniversary journey follows the birthday shape with a longer lead time. We suggest sending it one to two weeks ahead, because anniversary dinners are often planned further out. OpenTable passes anniversaries as dates, as the OpenTable integration page describes, so the trigger can run from data your reservation system already collects.
Do it because an anniversary is a dinner a couple plans on purpose, and the couple remembers who made it feel noticed. Write the invite warmly and mention a table or a dish that suits the night.
Anniversary emails are the stronger of the two occasion sends. In the same Bloom Intelligence benchmark, anniversary emails had a 20.9% open rate, brought a return visit 1.34% of the time and earned $181 per 1,000 emails. One-time blast emails brought a return visit 0.27% of the time and earned $80 per 1,000, so an anniversary email returned guests about five times as often.
5. Event follow-up: keep past hosts coming back for the next event
An event follow-up journey turns one private event into the next booking. It fires after the event closes and keeps the host in touch until planning starts again. Loyalist connects to Tripleseat and sends past hosts event photos at 2 weeks, a check-in on lost events at 6 months and a rebook reminder at 9 months. How can a restaurant group get more private event bookings? covers the wider events playbook.
Do it because a host who loved the event may still not rebook on their own. Planners move on, and the next holiday party goes to whoever reached out first.
Demand for private dining keeps rising. OpenTable reports that private dining inquiries on its platform more than doubled last year, and that private dining is often booked weeks ahead around busy seasons. In Loyalist platform data from one multi-location group, about 3,000 guests had dined in parties of 8 or more, and about 2,800 of them had never hosted a private event. That is a very large pool of likely hosts.
6. Post-visit feedback request: one form for every guest
The feedback request belongs inside the post-visit thank-you, and every guest gets the same ask. A short form lets guests rate the night. Unhappy guests reach a manager fast, so the problem gets fixed before it turns into a public review. Guests are also invited to share their experience on Google. Google’s guidance on getting reviews prohibits incentives for posting reviews, and suggests asking unhappy reviewers to contact you by phone or email to resolve things privately.
Do it because you hear about a bad night from the guest or from a public review, and a form means you hear first. Leave Yelp out of the ask. The Yelp Content Guidelines say businesses should never ask guests to write reviews. Send the same form to every guest, whatever the rating.
The payoff shows at group scale. When Boka Restaurant Group, with 23 locations, centralized its replies to guest feedback, response times fell and response rates rose. The OpenTable customer story describes how responding to negative feedback helped Boka offset the impact of bad experiences on guest retention. Loyalist brings more than 3 million reviews into one platform, giving restaurant groups a larger pool of guest feedback to monitor, identify recurring problems, and act on across locations (as of November 2026).
7. Cancellation save: offer another date while the plan is fresh
A cancellation save fires when a reservation status changes to cancelled. We suggest sending it within a day, with an easy way to pick another date. Keep the offer soft. One line that says you hope to see them soon, plus a booking link, does the job. At a group, the journey can also point guests to a sister restaurant when the original room is full on their new date, which keeps the cover inside the group.
Do it because a guest who cancels over timing may still want the dinner, and without a follow-up the cover simply disappears from the book. A short note keeps your room at the top of their list when they replan.
Cancellations arrive late, which makes a same-day reply matter. In the Resos No-Show Index, built from 3,768,761 reservations at 2,417 restaurants between August 2025 and July 2026, 317,541 of 566,049 cancellations, or 56%, came within 24 hours of the booking or after it had started. There is little time to refill a table that late, so a quick offer of another date is often the only chance to keep the guest.
8. Notify List nudge: turn repeated waitlist joins into a booking
A Notify List nudge reaches guests who keep joining the Notify List and never get a table. The trigger is repeated joins with no booking. We suggest sending the nudge within a day of the latest join. Offer a quieter night, an earlier seating or a seat at the bar. At a group, a table at a sister restaurant can work too. Keep the tone grateful, so the message feels like the host stand noticed.
Do it because these guests have already told you they want to come in. Each time they miss out, the chance grows that they give up. For a hard-to-book room, they are the easiest bookings you will ever win.
What should you look for in a guest journey platform?
A guest journey platform should do more than automate messages. It should protect guest preferences, prevent duplicate outreach, and give restaurant teams control over what gets sent. Before setting up a journey, make sure your platform supports four things:
- Separate email and SMS consent: Track permission for each channel independently and automatically stop texts when a guest replies STOP.
- Duplicate prevention: Recognize when a guest has already received an automation so they don’t receive the same message twice.
- Manager approval: Let managers review journeys before they go live, especially when each concept has its own brand voice.
- One guest profile across locations: Recognize the same guest across every venue, so visits at multiple restaurants don’t create fragmented records or duplicate messages.
Loyalist brings these capabilities together in one guest CRM. Every journey runs from a shared guest profile, while managers retain control over the messages each venue sends. Does your restaurant need a CRM? explains how a centralized guest record supports restaurant groups.
Guest journey FAQ
What guest data do you need to run automated journeys?
It depends on the journey. Welcome and win-back campaigns need visit history, birthday invitations need birth dates, and event follow-ups need private dining history. Connecting reservation, POS, and event systems helps make those journeys possible. Check our integrations page to see which platforms Loyalist connects with.
Do guest journeys need consent for email and SMS?
Track consent separately for email and SMS, since a guest may agree to one and not the other. The FTC CAN-SPAM compliance guide explains that commercial emails must include a valid postal address and a clear way to opt out. Honor opt-outs promptly and honor STOP replies on texts.
How do you know if a guest journey is working?
Count the bookings and spend that come from guests who received it. Compare that to a similar group of guests who did not, over a set window such as 30 days. Opens and clicks show interest, and booked covers show revenue. Cut journeys that bring in no bookings after a fair test. You can do this on Loyalist.
Sources
- OpenTable, How private dining can work for any restaurant, checked October 19, 2026
- Google Business Profile Help, Tips to get more reviews, checked October 8, 2026
- Yelp Content Guidelines, checked October 8, 2026
- OpenTable, Boka Restaurant Group customer story, checked October 19, 2026
- FTC, CAN-SPAM Act: A Compliance Guide for Business, checked November 16, 2026
- Vendor pages, checked November 16, 2026: Loyalist, Resy integration, Loyalist, OpenTable integration, Loyalist, Introducing Journeys
- Bloom Intelligence, 8 in 10 First-Time Restaurant Guests Never Come Back, June 5, 2026
- DataDelivers via RestaurantNews, Study Finds Only 1 in 5 Guests Return Within 12 Months, March 21, 2023
- Bloom Intelligence, Restaurant Email Marketing Benchmarks 2026, September 11, 2026
- Paytronix, Birthday program generates a sparkling 47% response rate, checked November 16, 2026
- Resos, No-Show Index, covering August 2025 to July 2026, checked November 16, 2026
- Loyalist platform data (journey revenue by trigger, win-back return rate, party-size example, review count), as of November 2026
If your hospitality group is looking to supercharge your data, we’d love to chat.