HannaAI

Write to forty people, not four thousand.

Hanna's marketing starts from a gap in next week's diary and works backwards to the handful of guests who actually fit it — using what they ordered, when they come and what they're worth. From your address, in your voice, and never a discount on a night that would have filled itself.

Records built from real visits Sent from your own domain Replies book straight into the diary

One note · six steps

The gap finds me, not the other way round.

Marketing starts with a night that needs filling. Everything else follows from that.

Next week · forecast against capacity

Tue32 free
Wed23 free
Thu11 free
Frifull
Satfull

Tuesday is the night worth filling. Friday and Saturday are already full, so anything sent to those guests would cost you money and gain you nothing — which is why Hanna won't.

Replaces: a calendar of campaigns nobody asked for

The audience picks itself.

Not everyone on the list. The people whose own habits say they might come on a Tuesday.

43Regulars who come midweek — three or more visits, most on a Tue or Wed
118Lapsed 60–90 days — used to come, haven't lately, no complaint on file
206Weekend-only guests — excluded, they don't come midweek
77No marketing consent — excluded, permanently
Written to from a list of 444161
Excluded because the night is full for them206
Excluded on consent77

Replaces: emailing the whole list and hoping

The reason to come isn't a lower price.

Hanna proposes something worth turning up for, drawn from what these guests already order.

A gluten-free tasting on Tuesday 18% of parties now carry a gluten flagProposed
Junmai flight alongside 44% of these guests take sakeProposed
Counter seats held back until 48 hours out two-tops fill lateProposed
20% off TuesdayNot proposed

A discount moves the same guests to a cheaper night. A reason brings different guests at full price. Hanna will send a discount if you write one — it just won't be the thing it suggests.

Replaces: discounting a night that would have filled

And it sounds like you, because it knows them.

Written against the actual record, from your own address, and yours to edit before it goes.

From: [email protected] · to 161 guests · drafted Sunday 09:12

Good morning — it was a pleasure having you in on Friday.

We've a gluten-free tasting on Tuesday evening, with a Junmai flight alongside it. Given how you were looked after last week I thought you'd want first refusal. Reply here and I'll hold you a table.

Warmly,
The team

Sent from your domain, your reply-to[email protected]
Approved by you before sendingAlways
Unsubscribe honoured immediately, permanentlyEvery send

Replaces: a template that sounds like a chain

A reply is a booking, not an email to answer.

The guest replies in their own words and Hanna takes it from there — same diary, same rules.

Replies received14
Booked without you touching it availability checked, allergy carried across11
Passed to you questions Hanna wouldn't answer alone3
Covers added to Tuesday26

Nothing was re-keyed. The 26 covers are in the same diary as every other booking, with the same allergy flags, and they'll appear in Tuesday's briefing like anybody else.

Replaces: asking people to "call us to book"

And I know what it earned. Honestly.

What followed, counted properly — and the one thing nobody can honestly tell you.

26Covers booked from the note
£1,134Revenue, at full price
£43.62Average spend, in line
Tuesday, before forecast52 covers
Tuesday, actual78 covers
Cost of sending£0.00

What Hanna won't claim: that those 26 covers wouldn't have come anyway. There is no control group in a forty-cover restaurant, so any return-on-investment figure would be invented. You get a count of what followed, not a number designed to flatter the tool.

Replaces: never knowing whether it worked

The guardrail

It will never suggest a discount.

Not as a stylistic preference — as a rule in the system. Hanna knows which nights are forecast to fill, and a discount offered to guests who were coming anyway is a straight transfer out of your margin into theirs.

What most restaurant marketing does

Sends the same offer to the whole list because the list is all there is. A proportion of the people who redeem it were already booked, or would have booked. The night looks busy, the covers look up, and the margin quietly falls — and because nobody measures the counterfactual, it gets repeated next month.

What Hanna does instead

Excludes the guests whose night is already full, writes only to the ones whose own history says they might come on the night that isn't, and proposes a reason rather than a reduction — an event, a dish, a table held back. If you decide to discount, it will send it. It simply won't be the recommendation.

The same rule runs everywhere else in the platform. Business Insight won't recommend a discount either, and neither will the weekly findings. A system that can see your margin should not be in the business of proposing you give it away.

The record

Nobody typed any of this in.

A guest record in Hanna is a by-product of running the restaurant, not an administrative task competing with it. Which is the only reason it's accurate — data entry that depends on a busy floor remembering to do it never survives a Saturday.

From the booking

Who they are, how often, how far ahead they book, what they told you about allergies and access.

From service

What they ordered, what they drank, what they avoided, which table, how long they stayed.

From the bill

What they spent, how it split, what they're worth across every visit rather than this one.

From the pattern

Which night they come, whether they've stopped coming, and roughly when they're due back.

The Osborne party

First visit March 2024 · 4 visits · midweek · books 3–4 days ahead · £612 lifetime

CoeliacStep-freeOmakase ×3JunmaiAnniversary · MayConsent · Mar 2024

That record is why a note can mention the gluten-free tasting rather than "our latest offer", and why it lands as a message from a restaurant that remembers you rather than a mailshot from a database.

Consent and data

Your list, and nobody else's business.

The guests are yours. That is not a slogan — it is an architectural fact, and it is worth being specific about because the alternative is what most of this industry does.

Consent, captured properly

Marketing consent is asked for explicitly at booking, stored against the guest with a date, and kept separate from the transactional messages a booking requires.

Unsubscribe means unsubscribe

Immediate, permanent, across every send. A guest who opts out still receives their confirmation and reminder, because those belong to the booking rather than to marketing.

Separated at the database

Every venue's guest records are isolated at the data layer, not merely filtered in application code. One venue cannot see another's guests, and neither can we casually.

Never sold, never shared

We have no advertising business and run no marketplace, so there is no commercial reason for your guest list to go anywhere — and no quiet incentive to change that later.

Exportable, always

The whole record, in a standard format, whenever you ask. Including on the day you tell us you're leaving.

Sent from your domain

Guests see your address and reply to you. Hanna is the machinery behind the note, not the name on it.

In service

Writing to real guests, from three London venues.

Each name here will take your call.

Hotori Yakitori & Edomae sushi · London EC4ALive since 2024
Charcoal Champ Chinese barbecue · London N1Live since 2026
Brass Bar Cocktail bar · LondonLive since 2026

Before you ask

The questions operators actually ask.

Why won't it recommend a discount?

Because a discount on a night that would have filled anyway is a straight transfer out of your margin, and most restaurant discounting is exactly that. Hanna knows which nights are forecast full, so it will not suggest an offer on those, and on a quiet night it will suggest a reason to come rather than a reduction in price — an event, a new dish, a table held back. If you want to run a discount you can, and it will send it. It just will not be the thing it proposes.

Where does the guest data come from?

From bookings and service. Somebody books a table, tells Hanna about an allergy, eats, and pays — and all of that writes to their record automatically. Nobody types a guest into a CRM. That is why the record is accurate: it is a by-product of running the restaurant rather than an administrative task competing with it.

Do you sell or share my guest list?

No. Your guest data is yours, held separately from every other venue at the database layer, never sold, and never used to market another restaurant to your guests. You can export the whole record at any time, including on the day you decide to leave. We are not a marketplace and we have no advertising business, so there is nothing to be tempted by.

How do you handle consent and unsubscribes?

Marketing consent is captured explicitly at booking and stored against the guest with a date, separately from the transactional messages a booking requires. Unsubscribes take effect immediately and permanently across every send. A guest who opts out still gets their confirmation and reminder, because those are part of the booking rather than marketing.

Can it tell me whether a campaign worked?

It can tell you how many people it wrote to, how many booked, how many covers arrived and what they spent. It cannot tell you whether those guests would have come anyway, because there is no control group in a forty-cover restaurant and any figure claiming otherwise is invented. What you get is an honest count of what followed, not a manufactured return-on-investment number.

Book a demo

See who you'd write to next week.

Tell us your quiet night and we'll show you how the audience is built — and which guests Hanna would leave alone.

Book a demo