Restaurant Sub-Account Kit

1. No. 01

   1 AI Receptionist

   Component 01 · AI Receptionist

   The problem

   Seven on a Friday is when every call is a booking and every pair of hands is carrying plates. Configuring a receptionist that can hold covers, sittings and a waitlist without double-seating the room is work an operator does again at every venue.

   Once it is loaded

   Covers, date and sitting are captured on the call, a full night offers alternatives and a waitlist place, dietary notes and a birthday are recorded, and a private dining or catering enquiry goes to a manager rather than into a two-cover booking slot.

   How it pays back

   If building service-hour call handling costs an operator seven hours per venue and a small group hands you five sites, that is thirty-five hours, and the restaurants stop losing the Friday calls, which is the only proof they will ask for.

2. No. 02

   1 AI Chatbot

   Component 03 · AI Chatbot

   The problem

   The message saying table for six at eight tonight arrives on Instagram, alongside corkage, allergen and parking questions, and none of it is answered until somebody opens the account tomorrow. Venue-specific intents are an evening of operator work each time.

   Once it is loaded

   One assistant answers opening times, allergen and menu questions, parking, group size limits and availability across the website, SMS, email, Facebook and Instagram, books what it can, and passes any event or large-party enquiry to a manager with details captured.

   How it pays back

   Assume a venue gets a hundred and twenty out-of-hours messages a month and a fifth become bookings averaging two covers at forty-five each; the account is visibly generating covers before the owner has finished reading the first invoice.

3. No. 03

   Pipelines

   Not one of the nine — what they run on

   The problem

   Table reservations are not opportunities, they are covers, and treating them as a sales pipeline clogs a board nobody then looks at. The genuine pipeline is private dining, catering and Christmas party enquiries, and operators tend to build the wrong one.

   Once it is loaded

   Reservations stay on the calendar where they belong, while the boards that exist run private events from enquiry through menu agreed to deposit paid, catering quotes, and corporate accounts, which is where the money the owner cannot currently see is sitting.

   How it pays back

   If an event board built correctly recovers three enquiries a quarter that would otherwise have died in voicemail, at two thousand a booking, that is twenty-four thousand a year the client traces to your account and not to the previous agency.

4. No. 04

   Workflows

   Not one of the nine — what they run on

   The problem

   A Tuesday with forty covers and a Saturday turning tables away need opposite automations, and a birthday captured in March has to fire the following March. That branching is fiddly, and every venue rollout rebuilds it from the same blank canvas.

   Once it is loaded

   Booking confirmation and reminder logic, waitlist release when a table cancels, a quiet-midweek offer that only fires when the book is light, a birthday sequence and event enquiry escalation to a manager are wired and running against the venue calendar.

   How it pays back

   If an operator spends nine hours a venue building this and you load six restaurants a year, that is over a working week; filling six extra midweek covers a night at forty-five apiece is the number the owner repeats to other owners.

5. No. 05

   Appointment reminders, confirmations and no-show recovery

   Component 05 · Smart Appointment System

   The problem

   A four-top that does not turn up at eight on a Saturday is revenue that cannot be recovered afterwards, and most venues confirm with nothing at all. Building the ladder plus same-hour recovery per site is repetitive, and it is also the component that pays first.

   Once it is loaded

   Reservations confirm on booking, remind at twenty-four hours, one hour and fifteen minutes with a one-tap cancel that releases the table to the waitlist, and a no-show is contacted inside the hour, against a seventy per cent recovery target.

   How it pays back

   If a restaurant loses fifteen covers a week to no-shows at an average spend of forty-five, that is roughly thirty-five thousand a year walking out, so the reminder ladder alone justifies the account before anything else in it is switched on.

6. No. 06

   Funnels

   Not one of the nine — what they run on

   The problem

   Private dining, Christmas packages, catering, gift vouchers and a set lunch are different sales with different qualifying questions, and most venue websites still route every one of them through the same contact form and the same auto-reply.

   Once it is loaded

   Conversion paths for private dining with party size and date, Christmas bookings with a deposit step, catering quotes, gift voucher purchase and a waitlist sign-up for a full night are built, each capturing what a manager needs before ringing back.

   How it pays back

   If a Christmas party page with a deposit step takes an operator four hours and several restaurant accounts want it live by October, the kit turns an autumn scramble into an afternoon of editing package prices per venue.

7. No. 07

   AI Studio website

   Component 04 · Professional Website

   The problem

   Menus change, hours change, and the chef sends the new one as a photograph of a printout. An operator rebuilding a venue site from a blank theme each time carries that chasing cost into every rollout and every seasonal menu change afterwards.

   Once it is loaded

   Menu pages structured for local search, a private dining and events page with its enquiry form, catering pages, opening hours and location data marked up properly, and a booking path wired to the calendar arrive written, needing photography rather than copy.

   How it pays back

   If a venue site is thirteen hours of build and menu chasing and you deliver five a year, sixty-five hours goes back, and the restaurant is live inside a week, which for a new opening is the difference between a full first month and an empty one.

8. No. 08

   Nurture campaign

   Component 02 · AI Outbound Caller + Component 08 · Database Reactivation

   The problem

   Most venues hold a mailing list of everyone who ever booked and send it all the same newsletter, so a regular who came fortnightly and stopped in March gets the identical email as a one-time tourist. A genuine lapse cadence per venue gets skipped every time.

   Once it is loaded

   Guests who have not returned within their own visiting pattern get a win-back referencing the last visit, stalled event enquiries get a follow-up sequence with an outbound call, and the dormant list is worked by what people actually booked rather than by broadcast.

   How it pays back

   If a venue has two thousand past guests and a considered win-back returns one in forty at a ninety pound table, that is four and a half thousand from a list the owner already had, which makes the retainer conversation a short one.

9. No. 09

   Review automation

   Component 06 · Review Harvesting + Component 07 · Review Automation

   The problem

   Review velocity decides which restaurant appears in the map pack, and the ask has to happen the evening of the visit rather than a week later. Wiring a completion trigger off a booking system per venue is exactly the integration work operators postpone.

   Once it is loaded

   The ask fires the evening of the visit off the reservation completing, passes a satisfaction gate so a bad table becomes a manager alert rather than a public review, runs a multi-touch cadence and rotates platforms, aiming at five to ten reviews a month.

   How it pays back

   If steady velocity of five to ten reviews a month moves a venue up the local map pack, and the map pack is where bookings come from, the owner attributes covers to your account monthly, which is why that account is still live in year two.

10. No. 10

    Seasonal automation

    Component 09 · Lifetime Nurture Campaigns

    The problem

    A restaurant year has fixed pressure points, the February and March flower-and-card weekends, Christmas party season, a dead January and a quiet Tuesday every week, and building that calendar per venue is an afternoon each that always lands too late to sell the date out.

    Once it is loaded

    Seasonal date campaigns, Christmas party booking opening in September, a January recovery offer, a midweek fill campaign, guest birthday and anniversary messages and a referral prompt are scheduled against the trading pattern the venue supplies.

    How it pays back

    If Christmas party enquiries opened in September rather than November fill eight extra parties at fifteen hundred, that is twelve thousand attributed to a campaign you loaded rather than built, and ten hours per venue you did not spend in October.

11. No. 11

    Custom values

    Not one of the nine — what they run on

    The problem

    A venue reprices its private dining minimum spend and suddenly every confirmation, reminder and enquiry reply is quoting last season. That happens because the number was typed into messages rather than held once at the top of the account.

    Once it is loaded

    Sitting times, cover limits, deposit rules, private dining minimum spend, corkage, cancellation window, the allergen contact and the booking link sit at account level, so a group opening a second site configures a screen rather than rebuilding messages.

    How it pays back

    If a small group opens two venues a year and each would otherwise take three hours of find-and-replace across confirmations and reminders, the kit removes that entirely, and no guest is quoted a minimum spend from last season for a Christmas party.

12. No. 12

    Custom fields

    Not one of the nine — what they run on

    The problem

    Most venues know a guest name and nothing else, because the booking platform keeps the reservation and throws away the pattern. Rebuilding a guest record shape from scratch per site is where operators quietly cut corners and the win-backs go generic.

    Once it is loaded

    The guest record holds last visit, visit frequency, typical covers, allergy and dietary notes, birthday and anniversary dates, seating preference and event history, which is what makes a win-back read as recognition rather than as a mailing list.

    How it pays back

    If designing and mapping that record takes two hours per venue and you carry ten restaurant accounts, that is two and a half working days; the greater value is that identical reporting works across a group, so one review call covers every site.

13. No. 13

    Forms and surveys

    Not one of the nine — what they run on

    The problem

    Event and catering enquiries arrive as a name and the words party of thirty, and a manager then burns two calls extracting date, budget, dietary needs and whether the room is wanted exclusively. That qualification belongs in a form nobody ever builds.

    Once it is loaded

    A private dining enquiry form capturing date, party size, budget band and dietary requirements, a catering brief, a post-visit guest survey feeding the satisfaction gate and a waitlist form arrive built and mapped onto the guest record.

    How it pays back

    If a manager loses two calls per event enquiry and a venue takes twelve a month, that is eight hours of management time returned monthly, and for you it is three hours of form building per account that you no longer repeat.

On purchase you receive two things: one snapshot link, and one PDF with full installation instructions. Installation is not in the kit price — load it yourself from the PDF, or add installation by us for $200 a sub-account. Every payback figure above is an illustrative scenario with its assumptions in the sentence, not a measured customer result.