Maya
5 of her last 6 orders included a flat white.
“Maya, your usual flat white is on us when you next drop in.”
Marketing campaigns let your team build an audience from guest order history, such as regulars who have not visited for 30 days, inspect exactly who matches and how fresh the data is, save the rules and export a fixed customer list. AI can then choose one approved benefit per guest and write their message for your team to preview. Audience building and exports are available today; campaign sending and incremental-revenue measurement are not yet available.
The guest’s home screen brings the inbox, rewards and ordering together.
The guest inbox keeps order updates where the guest can find them again. The demo shows seeded order-delivered messages; offers arrive here once delivery is enabled.
Native iOS app · Spike’s Diner demo
Five actual back-office screens from Spike’s Diner: the audience builder with its exact count, the matching guests, saved definitions and exports, then the journey setup and the per-guest personalisation controls. The large benchmark audience shown in the exports screen is synthetic.
Combine purchase, visit, channel and loyalty rules. This captured example matches 249 of 402 demo guests with at least 3 orders and no order for at least 14 days. Counts are exact for the data at the displayed refresh time.
Inspect the matching guests, their tier, orders, spend, last visit and favourite category. The preview has its own freshness timestamp; a frozen export keeps a campaign list consistent as new orders arrive.
Reopen a saved definition for a fresh audience. Activate it to freeze the customer IDs, then export the list. The 83,334-member audience shown here is from the synthetic benchmark; activation sends no messages.
Describe the occasion to get a suggested journey template, then choose the audience and approved benefits. This screen sets up the campaign; individual decisions happen in the customer preview.
Enable AI benefit selection and personal messages. The customer preview uses one guest’s orders, favourites, loyalty and offer eligibility. These are the configuration controls; no generated result is shown here.
Actual Back office screens · Restaurant demo data; large benchmark audiences are synthetic · Journey previews are simulations, with no messages sent
Select a stage to watch its steps. Pause to inspect a screen.
Both guests qualify. Their own history shapes what comes next.
5 of her last 6 orders included a flat white.
“Maya, your usual flat white is on us when you next drop in.”
4 of his last 5 orders included a margherita.
“Leo, fancy your favourite margherita again? Enjoy 15% off on your next visit.”
Your approved offers. A separate decision for each guest.
A relevant offer, with boundaries you set.
Audience analytics runs independently of checkout and wallet operations. Your team can explore guest behaviour while those services handle the visit.
The commercial payoff still needs to be demonstrated. This is the first useful test.
Proposed test, not a completed campaign. The large benchmark dataset was synthetic; it is not evidence of customer demand or revenue lift.
Your website, customer app, waiter app and kiosk integration come together as standard. Retter builds and runs them under your brand, connected through the same menus, orders and guest records.
Guest segmentation means grouping guests by what they actually did, such as regulars who have not visited for 30 days, so an offer reaches only the people it suits. In the back office Retter provides, a marketing team builds an audience from order history, sees exactly who matches and who may be contacted on which channel, saves the rule and exports the list. Sending campaigns from the back office is not yet available.
Not yet. Today, in the back office Retter provides, the team can build an audience from guest order history, such as regulars who have not visited for 30 days, inspect exactly who matches and how fresh the data is, save the rules and export a fixed customer list. It can also preview personal offers for individual guests using sample data. Sending email, SMS and push campaigns from the back office and incremental-revenue measurement are not yet available.
A restaurant CRM is one record per guest that holds their orders, visits, rewards and marketing permissions across every site and channel. Retter builds it as the guest account behind a group's website, app, table ordering and loyalty programme, so the team sees one history per guest instead of separate lists in separate tools.
No. The AI agents Retter builds into the back office investigate the guest, order and site records and prepare a proposal, such as a campaign audience, a menu change or a follow-up. Changes require a named person’s approval, with the proposal and outcome visible to the team. Campaign sending is not yet available: approving an audience or offer preview does not send email, SMS or push messages.
The operator does. The group is the data controller and Retter processes guest data under a data-processing agreement. Every guest record keeps its marketing permission per channel, guests can unsubscribe from any message, and the operator can export its data at any time.
Tell us about your sites and the systems you use. We’ll show you the guest experience, the team’s workspace and what a first rollout would include.
The guest demo uses a fictional restaurant. Payments are simulated.
