Skip to content
For restaurants and coffee shops

Requests arrive during service. Nobody is free during service.

Bookings, catering enquiries and “are you open on the 14th” land on Instagram and WhatsApp while the room is full. They get read at midnight, when the guest has already eaten somewhere else.

Book a call
See it runBooking request on Instagram
Instagram DM
Trigger
Covers read
GPT-4o
Times offered
Your book
Table confirmed
20:30
Reminder scheduled
Day before

Read, offered and confirmed in 4.8 seconds, without leaving the floor.

The Sunday inbox

The requests worth the most arrive at the worst possible moment. A DM about a table for eight, a WhatsApp about the private room, a form submission about catering. Each is worth more than a walk-in and each waits until the shift ends. Meanwhile the phone rings through service and nobody can pick it up.

Four things we automate for restaurants

Each one is a workflow you own, running in your own accounts, monitored and documented.

Table requests, answered while you are on the floorA request from WhatsApp, Instagram or the site gets a reply offering times you actually have free. The guest picks one, it lands in your book, and the confirmation goes out without anyone stopping what they are doing.
Large tables and private hire, qualified before you replyCovers, date, occasion, whether they want the set menu. The enquiry arrives with the basics already settled, so the one message you write is the one that closes it.
A menu your staff change, not your web developerDishes, prices, allergens, opening hours and the gallery, edited by whoever knows them. No ticket, no wait, no invoice for changing a price.
Reminders and the no-show problemA confirmation, a reminder the day before, and a one-tap cancel. A table that cancels at 16:00 can be resold. A table that never turns up cannot.
What ships
  • WhatsApp and Instagram feeding one intake, not three inboxes
  • Time offers read from your real availability, never invented
  • A CMS your staff run: dishes, prices, allergens, hours, gallery
  • Confirmation, reminder and one-tap cancel with opt-out handling
  • A runbook: what breaks, how to recover, what it costs to run

Questions restaurants ask

Does this replace TheFork or my booking system?
No, it feeds it. The assistant answers the enquiry and books into whatever you already use. If you have no system we can set that side up too, but the accounts stay yours either way.
What if someone asks something odd?
It answers from the responses you approve, not from a model improvising. Anything else becomes a handoff to a person, visibly, so the guest knows they are talking to you.
Can it take bookings when we are fully booked?
It offers only what your book actually has free. When there is nothing it says so, and offers the next available times or a waiting list, which is the version most owners want.
Who edits the menu after launch?
You do. That is the point of the CMS. Prices, dishes, allergens and hours are yours to change, without a ticket and without an invoice.
How long before it is running?
Five to eight working days from discovery to a signed spec. Then a fixed scope, a fixed price and a fixed date before anyone builds anything.

Tell us the process you hate most.

Thirty minutes, no deck. We walk one process end to end and tell you whether automating it pays for itself.

Book a callNo newsletter. No sequence.