Set up automated messages for your restaurant
Flows are an automated series of messages that you set up in Klaviyo. Unlike campaigns which you manually send or schedule, flows will send messages to recipients as soon as they complete an action that triggers the flow to send, say placing an order or setting up a reservation.
Most restaurants start with a welcome flow that automatically sends new guests an email welcoming them to your business. The trigger for this flow is when someone joins your email list. Once a guest subscribes, they will automatically enter your flow and receive your first preset message, getting them excited to place their next order.
Once you create your flow in Klaviyo, you can sit back and let your flow drive orders for you, creating a good experience for both you and your guests.
For more detailed information about flows, head to our course: Getting started with flows.
Out-of-the-box restaurant flow templates
Once you integrate your POS with Klaviyo, you’ll find the following flow templates available for you to get started quickly. In the table below, learn a bit more about each of these flow templates. Once you’re done, update messaging and tweak the structure to your specific use case, and set them live!
To find all of these flow templates in your account, head to Flows > Create flow, and you’ll land right in the flow template library.
Flow description | Trigger details | Why it matters | |
|---|---|---|---|
Welcome series | A series of messages that introduces new subscribers to your restaurant, menu, and ways to order or visit. | Someone joins your marketing list, such as through a website sign-up form or an in-person QR code. Messaging can differ for new and returning guests. | Builds the relationship from the first interaction and encourages a first order, reservation, or return visit. |
Guest winback | A series that reconnects with guests who have not ordered or visited recently. | Starts from a tracked order, completed reservation, or supported loyalty check-in, then waits a defined period. Filters check that the guest has not returned before sending. | Gives past guests a relevant reason to return, such as a favorite dish, a menu update, or a timely offer. |
Guest thank-you | A follow-up message that thanks guests after an order or dining visit. | A guest places an order, completes a reservation, or records a supported loyalty check-in, depending on the integration. | Shows appreciation, strengthens guest relationships, and can tailor the message for first-time guests versus regulars. |
Reservation cancellation | A follow-up message for guests whose dining reservation was canceled. | A reservation cancellation is recorded by a supported reservation integration. | Keeps guests informed and, in a separate marketing follow-up where appropriate, can make it easy to book another date. |
Abandoned order reminder | A reminder for guests who add items to an online order or begin checkout but do not finish. | A tracked Added to Cart or Started Checkout event occurs, followed by a delay and filters that exclude guests who have since placed an order. | Helps recover high-intent orders by giving guests a clear path back to complete their purchase. |
Browse abandonment | A follow-up for guests who view a menu item online but do not move forward with an order. | An identified visitor generates a supported Viewed Product event. Filters exclude guests who have since added items to their cart, started checkout, or ordered. | Brings an item back to mind and makes it easy to return to the menu while interest is still fresh. |
Reservation Reminder Series | Timely reminders that help guests prepare for an upcoming dining reservation. | Uses the reservation date and time from a supported reservation object to schedule messages before the visit. Exclude canceled reservations. | Keeps the reservation top of mind and provides useful details, such as the location, arrival instructions, and how to change the booking. |
Reward Confirmation | A message that confirms a newly earned loyalty reward and explains how to use it. | An Earned Reward event is received from a supported loyalty integration, such as Thanx or Punchh. | Makes loyalty benefits clear and gives guests a reason to return and redeem their reward. |
Power additional flows using objects and other triggers
Once your core flows are in place, use guest, order, reservation, and loyalty data to create more relevant reasons to return. Explore the tabs below for ways to celebrate guests, encourage a second visit, and introduce something new.
Not every flow below requires objects. Reward-expiration reminders use a Reward object, while the other examples can use a profile date or tracked events. Check the data requirement in each tab, use only data available through your connected integrations, and confirm that guests have the appropriate marketing consent for each channel.
Reward expiring soon
Requires a Reward object with an expiration date. For the date-based flow described here, your loyalty integration must sync a supported Reward object to the guest’s profile. An Earned Reward event alone does not provide the object-date trigger used to schedule this reminder.
An earned reward is a reason to return, but guests may need a reminder to use it. A reward-expiration flow highlights an available benefit before it expires and makes the next step clear.
- Build a date-triggered flow using the expiration date on the Reward object, such as three days before the reward expires. For Thanx, this may be CampaignRedeemableTo or ExpiringAt; for Punchh, use ExpiringAt. Confirm the field populated by your integration before configuring the trigger.
- Personalize the message with the reward name, expiration date, and redemption instructions. Include the value or eligible location when available.
- Check that the reward is still available and unredeemed before each reminder. Stop reminders if it has been redeemed or is no longer valid.
- Link to the relevant reward, ordering, or location page so guests can act easily.
For example, BeanTown Coffee could remind a guest that their complimentary pastry reward expires Friday, with a link to view the reward and find a participating café.
Birthday
Objects are not required for this version. You need a birthday saved as a date property on the guest’s profile to power an annual date-triggered flow. If you also want to display or track an individual loyalty reward, that additional content may use a Reward object.
A birthday flow helps your restaurant celebrate guests with a personal touch. Whether you offer a treat or simply send a warm greeting, it gives guests a reason to include your business in their celebration.
- Use a birthday date saved on the guest’s profile to schedule an annual message. Invite guests to share their birthday if you don’t already have it.
- Choose timing that fits the experience. Send a dining invitation ahead of the birthday so guests can plan, or a greeting on the day itself.
- If you include a reward, explain what’s included, how to redeem it, and when it expires. Only promise benefits your restaurant can fulfill and track.
- Include a clear next step, such as reserving a table, viewing the menu, or accessing an available birthday reward.
For example, a restaurant could invite a guest to book a birthday dinner a week before their birthday, highlighting celebration options at their preferred location.
First visit to repeat visit
Objects are not required for this version. Use a supported order or completed-reservation event, along with activity-history filters, to identify first-time guests and check whether they return. You do not need an Order or Reservation object just to start this event-based flow.
The first experience starts the relationship. A follow-up flow can help turn that initial order or visit into a habit by giving guests a thoughtful reason to come back.
- Start from a guest’s first tracked order or completed reservation, using the event supported by your integration.
- Thank them, then wait a period that fits your restaurant’s typical visit frequency before sending a return invitation.
- Introduce a popular menu item, another ordering option, or a loyalty program they may not know about. Use a modest second-visit offer only if it fits your strategy.
- Before sending the return invitation, check whether they have already ordered or visited again. Coordinate with your guest thank-you flow to avoid repeating the same message.
For example, BeanTown Coffee could follow a guest’s first tracked purchase with a short introduction to its cafés, then invite them back a week later to discover a new drink.
Menu and order-based cross-sell
Objects are not required if the triggering order event includes the item or category data you need. Use that event data to choose the recommendation. If those details are available only through an Order object in your setup, you will need that object data for the object-based version instead.
Past orders can help you recommend something relevant for a future visit. Use a cross-sell flow to introduce a complementary dish, drink, or menu category rather than sending every guest the same suggestion.
- Start from a tracked order and use available item or category data to identify a relevant pairing.
- Recommend something that complements the order, such as a pastry for a coffee buyer or a side for someone who regularly orders a main dish.
- Send the recommendation when it could inspire a future order. Avoid suggesting that a guest can change an order that has already been placed.
- Check menu availability and location relevance. Where the data supports it, exclude guests who have already purchased the suggested item, and avoid inferring dietary needs or allergies from order history alone.
For example, BeanTown Coffee could recommend a lemon loaf slice to guests who have ordered a latte but have not yet tried its baked goods, with a link to explore the pairing for their next visit.
Enhance your flows with more tools
Explore the dropdowns below to learn about features available to help you quickly and easily design more effective flows.
Audit your flows using Composer
Composer can review your flow structure, trigger logic, and performance to help you identify issues and prioritize improvements. Ask Composer to audit all of your flows or focus on one specific flow, such as your pre-arrival, welcome, or winback flow.
Start with a broad prompt, such as “Audit my hotel flows,” then ask follow-up questions about the most important finding. Composer is advisory, so review its recommendations and apply the changes yourself in Klaviyo. Re-run the audit after making updates if you want to confirm that your changes addressed the issue.
Flow library & templates
The Klaviyo Flow library is a comprehensive database of flow templates designed to help you accomplish specific goals. Browse the library for inspiration on new flows to create, and find templates to get started quickly and easily.
To access the Flow library:
- Log into your Klaviyo account.
- Click Flows on the left-hand navigation menu.
- Select Create flow to land in the Flow library.
You can use the search field to find specific templates, or filter by integration type and message channel. You can also browse flows by goal, including encouraging repeat orders, building customer loyalty, and more.
Use Flows AI to design flows in seconds
Have an idea for a new automation, but not sure how to build it yourself? Use Flows AI to generate what you’re looking for in seconds, and then you can make any necessary tweaks after.
To access this AI feature:
- Log into your Klaviyo account.
- Click Flows on the left-hand navigation menu.
- Select Create flow.
- Click Build your own.
- In the side panel that appears, name your flow.
- Select Create with AI. Describe your automation details in the field labeled Describe the flow.
- Click Generate draft, and watch the flow populate before your eyes.
Want to make a few tweaks, Just click Edit in builder to make your changes.
Use conditional splits to send messages via the guest's preferred channel
Adding conditional splits to your flows allows you to create branches of personalized messages.
Conditional splits are criteria you can set which determine the next message someone in the flow receives. An example conditional split might be: has placed an order in the last 30 days. You can then create a message version for those who have placed an order in the last 30 days and for those who haven’t.
Your guests will then move down the path of messages that specifically applies to them; in this example, whether or not they’ve placed an order in the last 30 days.
Consider adding conditional splits to your flows for message type (e.g., email versus text), so you can send your guests messages via their preferred channels.
Let’s say you’ve set up a birthday flow that provides guests with 20% off if they place an online order today. You’d like to send this message via text for all profiles who have subscribed to receive text messages, to get this message in front of them quickly. However, you still want your email-only subscribers to receive the birthday discount as well.
In that case, insert a conditional split after your flow trigger, with the condition:
- If someone can or cannot receive marketing > can receive > text message marketing.
Any guest who joins the birthday flow and has subscribed to text marketing will be sent down the YES path of the flow, while guests who join the flow and are only subscribed to email marketing will be sent down the NO path.
Drag an SMS message under the YES path and an email message under the NO path, and customize your birthday messages from here.
Review flows analytics
Flows analytics make it easier to see how guests move through each flow. Review how many guests enter the flow, how many reach each step, where people stop engaging, and which messages drive bookings, revenue, or survey responses. Reviewing your data frequently enables you to spot obstacles quickly, make swift improvements.
To review your overall flow performance:
- Go to Flows in the left-hand navigation, then select the Analytics tab.
- Choose a timeframe, such as the last 7, 30, or 90 days, the last 12 months, or a custom range.
- Use Flow view to compare individual flows, or Channel view to compare performance across email, SMS, and other channels.
- Review key metrics such as revenue, conversions, conversion rate, deliveries, and unique recipients. For hotel flows, choose a conversion metric that aligns with your goal, such as a booking, revenue event, or survey response.
To review a specific flow’s performance:
- Select a flow to explore the messages within it.
- In the visual flow builder, click Show Analytics to display performance metrics directly on each sending action and compare messages or split paths.
- You can also select an individual message and click View all Analytics to review engagement over time, deliverability, recipient activity, link activity, and skipped reasons. The recipient activity view can help you understand who received, opened, clicked, converted, or was skipped from a message.
Use these insights to improve your flow over time. You might adjust the timing of a pre-arrival message, test a clearer call to action, remove an underperforming step, or refine a conditional split based on guest behavior. If you need to share results or analyze them outside Klaviyo, export the flow analytics as a CSV.