A generic assistant
Knows the name and the industryAsk a question and this side answers with nothing but the business name.
The phone rings during service, and the answer to "do you have anything at 8pm?" decides where a table of six eats. What happens after they leave decides whether they come back, and almost nobody has a system for that half.
Phone · WhatsApp · Instagram · Reservations · Private dining · Post-visit feedback
Not one dramatic failure — a few at each step, in the specific places this kind of business loses them.
Seven to nine on a Friday is when bookings are made and when nobody can answer. A table of six that cannot get through books somewhere else, permanently.
One unavailable slot is treated as a closed door. Nobody offers 7:30 or 8:45, the bar for the wait, or another evening — so a willing guest simply leaves.
Whether a group books often turns on one vegetarian, one allergy or one child. A vague answer sends a party of eight elsewhere.
An anniversary booked with no note is a missed chance to be the restaurant that remembered — and occasions are what create regulars.
A guest who had a poor experience says nothing on the way out. The first the manager hears of it is a review, when it is far too late to fix.
The single largest missed opportunity in hospitality. They enjoyed it, they meant to come back, and nothing ever reminded them.
A search, a social post, a recommendation, or walking past.
Answered during service, when the phone would otherwise ring out — including at 11pm for tomorrow.
Vegetarian options, allergies, price per head, parking, whether children are welcome, how private the private room really is.
If 8pm is gone, the nearest slots, the bar for the wait, or another evening — never just "we're full".
Date, covers, occasion and dietary needs captured together. Groups and private dining go to the events team, never confirmed in chat.
A reminder the day before, and the floor already knows it is an anniversary and that one guest cannot have nuts.
A short message afterwards inviting honest feedback — the same invitation to every guest, regardless of how the evening went.
Anything that went wrong reaches a manager the same day while it can still be put right. Guests who enjoyed it hear from you again at a moment that makes sense.
This is what the system has to know to be useful here — and, just as importantly, what it must refuse to do.
Saffron & Salt is an illustrative restaurants & hospitality business. Ask it anything — the same model answers twice, once knowing only the name, once given the business. The second answer is the one your customers would get.
Ask a question and this side answers with nothing but the business name.
…and this side answers with everything in the panel on the left.
Both answers come from the same model, in real time. The tags under the second answer are the system events that would follow in a live deployment — this page cannot write to a CRM or a calendar.
These are the sentences that stall a sale in this business. A system that has never been told how you answer them will answer them badly.
Calls, WhatsApp and Instagram handled when the floor cannot pick up.
The table of six books with you instead of the restaurant that answered.
Nearest available times, the bar for the wait, or another evening offered automatically.
A willing guest has somewhere to go other than a competitor.
Dietary detail, price per head, children, parking — specifically, not vaguely.
One vegetarian or one allergy stops being the reason a group books elsewhere.
Anniversary, birthday, dietary needs and seating preference recorded at the point of booking.
The floor can be the restaurant that remembered, which is what creates regulars.
A post-visit message inviting honest feedback, sent identically to every guest.
A manager can put something right while the guest still cares about the outcome.
Guests who enjoyed it hear from you again at a moment that makes sense to them.
The largest missed opportunity in hospitality stops being missed.
The numbers that tell you whether it is working in this business. No figures are shown until they come from your own systems.
Enquiries that got no response at all — the leak most businesses cannot see.
Measured from Inbound conversations with no outbound reply within the agreed window.
How long a person waits for their first real answer.
Measured from Timestamp of inbound message to timestamp of first reply.
Enquiries arriving outside working hours, and how many were answered.
Measured from Conversation timestamps against your published opening hours.
Enquiries that became a booked appointment, viewing, table or call.
Measured from Confirmed calendar bookings ÷ qualified conversations.
Customers who responded after their visit, and how many raised something worth fixing.
Measured from Responses to post-service messages.
Customers who came back, and how long they took.
Measured from Repeat bookings matched to an existing CRM contact.
Lapsed customers who returned after re-engagement.
Measured from Contacts inactive beyond your threshold who then booked again.
What counts as a win here: A confirmed reservation with the occasion and dietary needs attached — and a guest who comes back.
Limits are part of the build, agreed before anything goes live. In this industry they are these.
Working in a different industry? The approach is the same — we map how your business wins customers before recommending anything.
A free 30-minute look at how your business attracts, captures, converts, serves and retains customers. No obligation, and the recommendation is not always automation.