Module · Marketing

Restaurant Marketing Software

The guests worth reaching are the ones who already came, already liked it, and haven't been back since March. You already have their names. This is the part that does something with them.

Why it matters

Restaurant marketing usually means buying strangers. A boosted post, a discount to whoever walks past, a mailing list bought from somewhere. All of it competes for people who have never eaten your food and have no reason to believe it's good.

Meanwhile the person who came four times last spring and then stopped is sitting in your own order history, and nothing in a normal restaurant stack can find them — because finding them needs the orders, the guest records and the consent in one place.

Customers list showing each verified guest with lifetime spend, order count, loyalty progress and last visit
Guests verified at this venue — what they spent, how often, and how long ago. A guest whose card is full is flagged Reward ready.

Two campaigns, one set of rules

Everything below — consent, the frequency cap, the codes, what you can honestly claim afterwards — applies to both of the things this module actually sends. The campaigns themselves have a page each, because they are different jobs.

Birthday campaigns

Four messages over five weeks, with the ask for the party arriving a month out, while somebody is still deciding where to take eight people.

Birthday marketing →

Personal offers

Pick the guests who stopped coming, or the regulars worth thanking, and make them one offer with an end date. Four kinds, and the percentage is the weakest.

Win-back offers →

What stops you sending the wrong thing

Consent is per venue and opt-in, and it has two levels. A guest can agree to hear about events only, or events and offers. An offer will not go to somebody who only agreed to events — and consent given before offers existed counts as events-only until they're shown the wider wording and agree again. Those guests appear on the audience screen as a count, so you can see how many are reachable and how many aren't, without ever seeing a name you're not allowed to mail.

Two emails per guest per thirty days. Across the entire platform. Not per venue — a guest verified at six restaurants still receives at most two marketing emails in any rolling month from all of them combined. It's a rolling window, not a calendar month, and it counts every event invitation, every offer and every birthday touch together.

Your staff can't be marketed to. An employee who also eats at your venue is excluded from every audience, even when they'd otherwise match perfectly.

Discounts stop at 90%. A hundred percent off is not a marketing offer; it's a typo somebody is about to email to four hundred people.

Every email carries an unsubscribe link, and a guest can turn a venue off from their own account without contacting anybody.

Codes people can read out

Offers travel as a six-character code the guest shows and a waiter types in. The alphabet drops every pair that gets misheard across a room — no O and 0, no I, L and 1, no S and 5, no B and 8. Codes are unique inside your venue, valid between the dates you set, and can be redeemed exactly once even if two phones try at the same moment.

Nothing comes off a bill automatically. That's on purpose: a birthday cake arriving at a table isn't always an order line, and the person holding the code should be the person deciding.

What it can honestly tell you afterwards

Campaigns planned, emails sent, codes issued, codes redeemed, enquiries received, parties confirmed, covers, and revenue attributed — where attributed means real served orders from those parties and bills a code actually came off. No per-head estimates dressed up as measurement.

There is no tracking pixel in any of it. Nothing follows a guest around, and nothing counts an image loading as interest. The signals are that an invitation page was opened and that a code was redeemed — fewer numbers than a marketing suite reports, and every one of them is a person doing something.

Guest feedback report showing overall rating, scores by category, a weekly trend and a grid of which shifts go wrong
Ratings by category, week by week, and which shifts go wrong. The sample size is printed next to the score.

Common questions

Can I upload my mailing list?

No. There's no contact import, and you can't type in an arbitrary email address. The audience is drawn only from guests who created an account, were approved at your venue, and opted in. That's a real limit — it's also the reason the list is worth mailing.

Does it send SMS or WhatsApp?

No. Email only, delivered through Amazon SES.

Do birthday emails send themselves?

No. You open the upcoming-birthdays list, pick a person and plan their campaign. Once planned, the four messages go out on schedule on their own — but nothing creates a campaign without you.

What if a message misses its moment?

It's skipped, not sent late. A birthday greeting that arrives two days afterwards is worse than none, so anything more than 48 hours behind schedule is dropped and recorded as skipped.

Is there A/B testing?

No. One version, written by you.

Can I offer a discount for bringing friends?

You can make the offer, and the party-size condition is shown to the waiter when the code is redeemed. It isn't enforced by software — the system doesn't know how many people sat down, and pretending otherwise would just mean refusing valid codes.

What happens to guests at my other venues?

Consent is per venue, so agreeing at one doesn't opt them in anywhere else. The two-per-month cap, however, is shared across all of them.

See it in action

See the rules your campaigns would run under.

Book a demo