A guest books a table on Tuesday and hears nothing until Friday. Another cancels, and the relationship ends right there. A no-show vanishes without a nudge. A visitor fills out a form on your website and the submission sits quietly in a database. A regular orders the brisket for the fifth time and nobody notices the pattern. Another regular slowly stops coming in, and the only way anyone notices is an export and a spreadsheet.
Every one of those is a guest signal. And in most restaurant marketing stacks, every one of them dies unanswered. Not because the team doesn’t care, but because the platform never gave them a trigger, a view, or a button in the right place.
The Bloom Summer Release is about coverage. Four new capabilities that expand when Bloom can act (five reservation lifecycle moments instead of one), where it can act (any form widget on your website), how precisely it can act (workflows triggered by real guest behavior, down to the specific menu item), and how fast a human can act (four one-click actions on every row of the guest list). By the end of this post you’ll know exactly which signals stop slipping through, and how to turn each one into a campaign today.
The Summer Release adds reservation triggers for all five reservation actions, behavior-based workflow triggers with n’th-occurrence thresholds, a redesigned Guest Profiles page built for one-click action, and Widget Campaigns that respond to website form submissions the moment they happen. All live now, for every Bloom user.
Why This Release Matters
The Spring Release was about intelligence: more data flowing into the unified CDP, more automated analysis coming back out. The Summer Release is about coverage: making sure every signal that intelligence produces has a response path.
Think about the signals your restaurant generates in a single day. Reservations get created, changed, cancelled, completed, and missed. Website visitors submit contact forms, feedback forms, and signup widgets. Guests log into WiFi, order online, order in-store, and reveal their favorites one menu item at a time. And inside your database, guest profiles quietly cross thresholds, a lapsed regular here, a rising spender there.
Before today, Bloom could act on some of those signals. After today, it can act on nearly all of them.
One reservation trigger. Signals slipping through.
- Campaigns fire only on completed reservations
- Cancellations and no-shows go unanswered
- Workflows can’t see orders, visits, or menu choices
- Widget submissions sit in the database
- Acting on one guest means exports and list-building
- The guest list is a report, not a tool
Five reservation moments. Real behavior. One-click action.
- Created, modified, cancelled, completed, and missed all trigger campaigns
- Win-back and recovery journeys fire automatically
- Workflows trigger on behavior, down to the menu item, with n’th-time thresholds
- Any widget submission sends an email or SMS instantly
- Email, enroll, view, or inactivate right from the guest row
- The guest list becomes a launchpad
That’s sixteen net-new activations across the four flywheels: Discovery, Marketing, Sentiment, and Operations. Let’s walk through each capability.
Reservation Triggers by Action: The Whole Lifecycle Becomes a Campaign
Every reservation tells a story. Now every chapter can trigger a campaign.
Until now, reservation-based marketing in Bloom fired on one event: a completed reservation. Useful, but it ignored the four other moments where a guest is telling you something. The Summer Release changes that. You can now trigger an automated email or SMS campaign on any of the five reservation actions, and it works across every reservation source Bloom ingests.
Each action type gets its own campaign. Create one for cancellations, another for no-shows, another for the moment a booking is created. The setup takes minutes, and the coverage is permanent.
The two most valuable plays are the two that were impossible before. A missed reservation is a guest who wanted to come and didn’t show, the warmest recovery audience you will ever have. A cancellation is a guest whose plans changed, not whose loyalty did. Both now get a response within minutes instead of never.
How it activates the four flywheels
-
DiscoveryRecovered cancellations and rescued no-shows become completed visits, and completed visits become the reviews and repeat behavior that bring the next guest through the door.
-
MarketingFive lifecycle moments become five precision triggers: confirmation on creation, clarity on modification, win-back on cancellation, gratitude on completion, recovery on a miss.
-
SentimentCompletion triggers let you ask for feedback at the moment of peak signal, right after the visit, while the experience is still fresh.
-
OperationsCancellation and missed-reservation patterns surface by day, daypart, and location. Demand intelligence that used to hide inside the reservation system.
What reservation actions can trigger a marketing campaign in Bloom Intelligence?
Bloom Intelligence can trigger an automated email or SMS campaign on any of five reservation actions: when a reservation is created, modified, cancelled, completed, or missed. Each action type is configured as its own campaign, and the triggers work across all reservation sources connected to the Bloom platform. Before the Summer Release, campaigns could only fire on completed reservations.
The New Guest Profiles Page: From Report to Launchpad
The distance between seeing a guest and acting on that guest is now one click.
The Guest Profiles page has been redesigned around the questions operators actually ask. Who is this guest. How often do they visit. What have they spent with us. When did we last see them. Every row now shows name and email, number of visits, Total Spend, and date of last visit at a glance, no clicking into a profile to find out whether a guest matters.
The four action buttons are the point. Email this one guest. Enroll them in a workflow. Open their detailed profile. Or inactivate the profile and keep your database clean. No exporting, no list-building, no losing your place.
The workflow is almost embarrassingly simple: sort by last visit, scan Total Spend, and act. The guest who spent $965 with you and hasn’t been in for six weeks is no longer hiding on row 400 of an export. They are one click away from a win-back workflow.
How it activates the four flywheels
-
DiscoveryEvery recovered regular is a future reviewer and referrer. The guests most worth recovering are now the easiest ones to find.
-
MarketingThe list view becomes a launchpad. One click sends an email to a single guest. One click enrolls them in an automated journey.
-
SentimentThe detailed profile view puts a guest’s feedback next to their visits and Total Spend, so every response and outreach is written with full context.
-
OperationsSorting by last visit turns the guest list into a churn radar. Inactivation keeps reporting honest and the database clean.
What does the new Bloom Guest Profiles page show?
The redesigned Bloom Intelligence Guest Profiles page shows each guest’s name and email, number of visits, Total Spend, and date of last visit in a single row. Each row also includes four one-click action buttons that let a user email the guest, enroll them in a marketing workflow, view their detailed profile, or inactivate the profile. The list can be sorted by last visit to surface lapsed guests quickly.
Your lapsed regulars are already in there. Come find them.
A 15-minute walkthrough of the new Guest Profiles page against your own guest database. Sort by last visit, scan Total Spend, and watch how fast “we should reach out to them” becomes “we just did.”
Widget Campaigns: Your Website Just Became a Campaign Trigger
Every form on your website can now answer back, instantly, automatically, every time.
Every form widget on your website, contact forms, feedback forms, signup widgets, all of them, can now fire a campaign the moment a guest hits submit. The new Widget Campaign trigger sends an email or SMS automatically on submission. Pick the widget, pick the message, and the response is instant, whether the guest submits at 2 PM or 2 AM.
Each Widget Campaign points at one widget, which means each form on your site gets its own perfectly matched response. The feedback form gets a thank-you and a next step. The contact form gets an immediate acknowledgment. The signup widget gets a welcome that starts the relationship on the right foot.
The three firing modes are where the configurability earns its keep. Every-submission mode is for confirmations that should never be skipped. First-submission mode is for welcome-style messages a guest should only ever see once. And new-guests-only mode turns any widget into a database growth engine, firing exclusively for people Bloom has never seen before.
How it activates the four flywheels
-
DiscoveryEvery website visitor who raises a hand gets an instant response. First impressions stop depending on whether someone checked the inbox.
-
MarketingSubmission-triggered email and SMS with per-widget precision. The message always matches the form the guest just filled out.
-
SentimentFeedback widget submissions land on the guest profile and receive an immediate acknowledgment, which is itself a sentiment play.
-
OperationsNew-guests-only mode grows the database cleanly. No duplicate noise, no re-welcoming your regulars.
What are Widget Campaigns in Bloom Intelligence?
Widget Campaigns are a new Bloom Intelligence campaign trigger that automatically sends an email or SMS when a guest submits a form widget on the restaurant’s website. Each campaign is tied to one specific widget and can be configured to fire on every submission, only on a guest’s first submission, or only for new guests who are not yet in the database.
New Workflow Triggers: Automation That Watches Guest Behavior
Your workflows can now watch what guests actually do, and fire on the exact behavior that matters.
Bloom workflows could already run multi-step email and SMS journeys. The Summer Release gives them a new set of eyes. Workflows can now trigger directly from guest behavior: a WiFi login, an online order, an in-store order, or a reservation. And for the first time, they can trigger on what a guest actually orders, a specific menu item or any item from a selected group.
Every behavioral trigger also accepts a threshold. Fire on the first occurrence, the third, the tenth, any n’th time the behavior happens. That one setting turns a simple trigger into a loyalty engine: a guest’s fifth online order can automatically earn a thank-you perk, and their tenth WiFi login can unlock VIP recognition, without anyone watching a report.
The menu-item trigger deserves special attention. Ordering behavior is preference data, and preference data is the raw material of personalization. The guest who orders the smoked brisket three times is telling you exactly what belongs in the subject line of their next email. Now a workflow can hear it and act on it automatically.
How it activates the four flywheels
-
DiscoveryGuests recognized on their n’th visit or order become the regulars whose reviews and word of mouth bring in the next table.
-
MarketingMenu-item and behavior triggers mean every automated journey starts from something the guest actually did, not a guess about what they might like.
-
SentimentRecognizing a guest’s fifth order or tenth visit at the moment it happens is a loyalty gesture guests feel, and mention in reviews.
-
OperationsThreshold triggers automate the recognition work managers used to do from memory, consistently, across every location.
What can trigger an automated workflow in Bloom Intelligence?
Bloom Intelligence workflows can now trigger on guest behavior, including a WiFi login, an online order, an in-store order, a reservation, or ordering a specific menu item or any item from a selected group. Each behavioral trigger also supports an occurrence threshold, so a workflow can fire on the first, third, or any n’th time the behavior happens.
The Coverage Effect: One Guest, One Summer, Zero Blind Spots
Each capability stands on its own. Together they close the loop around a single guest in a way no amount of manual effort could. Here is one guest, one summer, every feature firing, zero exports.
The coverage effect in motion. No signal left behind.
-
Tuesday, 6:40 PM: a guest books a table for Friday.
The reservation-created campaign fires within minutes: a warm confirmation and a menu preview. The visit starts before the guest walks in.
Reservation Triggers · Created -
Thursday: plans change and the guest cancels.
The cancellation campaign fires with an easy rebook link and a small incentive. The guest rebooks for the following week instead of drifting to a competitor.
Reservation Triggers · Cancelled -
The next Friday: the reservation completes.
The completion campaign says thank you and asks how it went, at the moment of peak signal, while the meal is still fresh in memory.
Reservation Triggers · Completed -
That weekend: the guest submits the feedback widget on your website.
A Widget Campaign in first-submission mode responds instantly, and the submission lands on the guest’s profile in the CDP.
Widget Campaigns -
Over the next month: the guest places their fourth online order.
A behavior workflow with a threshold of four fires automatically and recognizes the milestone with a small perk. The guest never filled out a loyalty card.
Workflow Triggers · Threshold -
Six weeks later: the visits quietly taper off.
A manager opens Guest Profiles and sorts by last visit. There is the guest, near the top, with a Total Spend figure that says this one matters.
Guest Profiles -
One click: Enroll in Workflow.
The win-back journey runs automatically. The guest returns, and every touch along the way is already on their profile. No export ever happened.
Guest Profiles · Workflows
Now multiply that by every guest, every reservation, every order, and every form submission across every location. That is what coverage means.
The activation matrix: every feature, every flywheel
| Feature | Discovery | Marketing | Sentiment | Operations |
|---|---|---|---|---|
| Reservation Triggers | Recovered bookings become completed visits, reviews, and repeat behavior. | Five lifecycle moments become five precision campaign triggers. | Completion triggers time the feedback ask at peak signal. | Cancellation and no-show patterns surface by day and location. |
| Guest Profiles | Recovered regulars become repeat reviewers and referrers. | One-click email or workflow enrollment turns list views into campaigns. | Feedback sits next to visits and Total Spend for full-context outreach. | Sort by last visit for churn radar. Inactivate to keep data clean. |
| Widget Campaigns | Every raised hand on your website gets an instant first impression. | Instant email or SMS on submission, matched per widget. | Feedback submissions flow to the profile and get acknowledged immediately. | New-guests-only mode grows the database without duplicate noise. |
| Workflow Triggers | Milestone recognition builds the regulars who review and refer. | Journeys launch from real behavior: menu items, orders, visits, reservations. | Automatic recognition at the n’th visit or order is loyalty guests can feel. | Thresholds automate VIP recognition consistently across every location. |
Five takeaways worth pinning
- Every reservation action is now a campaign trigger: created, modified, cancelled, completed, and missed.
- Workflows now trigger on real guest behavior: WiFi logins, online and in-store orders, reservations, and even specific menu items, with n’th-occurrence thresholds.
- Every website form widget is now a campaign trigger, with three firing modes to match the job.
- Acting on a single guest takes one click from the guest list, not an export and a list build.
- All of it is live today for every Bloom user. Nothing to install, nothing to request.
What This Release Means for Your Team
The Summer Release lands differently depending on the seat you sit in. Here’s what changes this week.
Fewer guest signals die unanswered.
Every reservation event, every order, every website form, every drifting regular now has an automated or one-click response path. Coverage compounds without adding headcount.
Triggers that start from real behavior.
Build a campaign per reservation action. Point a campaign at any widget. Launch workflows from WiFi logins, orders, reservations, and menu items, with thresholds. The response starts the second the signal happens.
The guest list finally works like a tool.
Sort by last visit, see Total Spend, act in one click. Milestone recognition runs automatically, and cancellation and no-show patterns stop hiding inside the reservation system.
How to Turn It On
Everything in the Summer Release is live now for every Bloom user. Nothing to install, no plan upgrade, no waitlist.
Reservation triggers: create a new campaign and choose the reservation action that should fire it. One campaign per action type, so build all five and cover the entire lifecycle.
Workflow triggers: open a workflow and choose a behavior trigger: WiFi login, online order, in-store order, reservation, or a menu item or group of menu items. Then set the occurrence threshold and let it run.
Widget Campaigns: create a campaign with the widget submission trigger, pick the widget, and choose the firing mode: every submission, first submission only, or new guests only.
Guest Profiles: already live. Open the page, sort by last visit, and see who’s been waiting for you to notice.
One next step: a fifteen-minute walkthrough against your own data, so you can watch the coverage close in real time.
Every unanswered signal is a guest deciding you didn’t notice.
The Summer Release makes sure Bloom notices for you: every reservation action, every order milestone, every widget submission, every drifting regular. A 15-minute walkthrough shows what full coverage looks like on your own guest data.