Restaurant Owner Snapshot — GoHighLevel snapshot

1. CH-01

   1 AI Receptionist

   Capture

   SYSTEM COMPONENT 01AI Receptionist

   A restaurant phone rings hardest at seven on a Friday, which is exactly when nobody can pick it up. This answers, takes the covers, the date and the time, checks whether it is a special occasion, captures allergies and dietary requirements, and books into the real table plan. Large parties and private hire route to the manager instead of being booked blind.

   • Books into the real table plan, not a request list
   • Captures allergies and dietary requirements at booking
   • Asks about the occasion, which changes the table
   • Large parties and private hire go to the manager

   THE FAULT

   Half seven on a Friday: two servers down, the pass backed up, and the phone going for a table of eight next Saturday. Front of house lets it ring, because a guest standing at the desk beats a guest on the line, and those eight covers eat somewhere else.

   ONCE IT IS RUNNING

   Every call answered through service, taking covers, date, sitting, the occasion and any allergy note, writing it straight into the reservation calendar and reading it back. Anything above a set party size, or any private hire question, goes to the manager instead of being booked blind.

   THE RETURN

   At an $85 average cover, one table of six lost every Friday is roughly $2,000 a month walking out on a ring tone. Substitute your own cover value and your own worst hour and the figure moves, but the direction of it does not.

2. CH-02

   1 AI Chatbot

   Capture

   SYSTEM COMPONENT 03AI Chatbot

   People book restaurants on a phone in the evening and their questions are practical: is there parking, do you have a gluten-free menu, can you take a party of ten, is there a set menu at Christmas. This answers all of that from the site and the Meta inboxes, captures the party size and any dietary requirement, and books the table.

   • Answers parking, dietary and set-menu questions directly
   • Captures party size and dietary needs before booking
   • Runs on Instagram and Facebook, where restaurants get found
   • Books the table inside the conversation

   THE FAULT

   A guest deciding at nine on a Wednesday wants to know about parking, whether the tasting menu can be done gluten free, and whether you can seat twelve for a birthday. Those messages sit in the Instagram inbox until somebody opens it on Monday afternoon.

   ONCE IT IS RUNNING

   The same assistant works the site, the text line and both Meta inboxes, handling parking, allergens, corkage, set menus and dress, capturing party size and dietary notes, booking the table in the conversation, and passing anything about a serious allergy to a human rather than guessing at it.

   THE RETURN

   If forty of those messages a month wait until Monday and a quarter of them were a booking, that is ten tables gone. Ten tables of four at an $85 cover is over $3,000 a month in enquiries you were most likely already paying somebody to generate.

3. CH-03

   Pipelines

   Capture

   SUBSTRATE — NO COMPONENT OF ITS OWN

   Not one of the nine, and not decoration either. This is part of what the nine run on: get it wrong and every component above it misbehaves in a way that is very hard to debug six weeks later.

   THE FAULT

   A Tuesday table for two and a Christmas party for forty are worth wildly different money and get treated identically, so a private dining enquiry with a five-figure spend waits in the same inbox as a booking request and gets a reply on Thursday, by which point the venue is chosen.

   ONCE IT IS RUNNING

   Covers run on a reservation board where the stages are booked, confirmed, seated and no-show, while private hire and catering get their own board with deposit taken, menu agreed and final numbers, because a single entry on that board outweighs a whole night in the dining room.

   THE RETURN

   One private event of forty guests on a set menu at $60 a head is $2,400 before a drink is poured. If two of those enquiries a quarter currently go unchased because they are buried among table requests, separating the boards is not a marginal improvement.

4. CH-04

   Workflows

   Nurture

   SUBSTRATE — NO COMPONENT OF ITS OWN

   Not one of the nine, and not decoration either. This is part of what the nine run on: get it wrong and every component above it misbehaves in a way that is very hard to debug six weeks later.

   THE FAULT

   The waitlist only works when somebody remembers it exists. A four-top cancels at five, the manager is on the floor by half past, and that table goes out empty on the busiest service of the week while people are being turned away at the door.

   ONCE IT IS RUNNING

   Automations built to the clock of a service: a cancellation pushes the freed table straight to the matching waitlist entries, large parties get a final-numbers chase before the date, a birthday recorded at a booking fires eleven months later, and a thin midweek triggers a segmented fill.

   THE RETURN

   Two cancelled tables a week refilled from the waitlist rather than left dark, at four covers and $85 each, is close to $3,000 a month. The waitlist already exists; the only question is whether anyone is free to work it at half past five on a Saturday.

5. CH-05

   Appointment reminders, confirmations and no-show recovery

   Booking

   SYSTEM COMPONENT 05Smart Appointment System

   A no-show on a Saturday at eight is a table that could have been sold twice. The confirmation carries the time, the party size, the table-holding policy and the dietary note already recorded. Reminders at twenty-four hours and two hours, and a no-show releases the table to the waitlist immediately rather than at the end of service.

   • Confirmation restates the table-holding policy
   • Reminders at 24 hours and 2 hours, sized for a booking not a job
   • A no-show releases the table to the waitlist at once
   • One-tap cancellation, which is cheaper than an empty table

   THE FAULT

   A six-top books for Saturday at eight, forgets, and nobody rings. The table is held for twenty minutes, turned over late, and the walk-ins you turned away at half seven are eating down the road while your best section runs one table short.

   ONCE IT IS RUNNING

   Confirmation at the moment of booking restating the holding policy and the allergy note already recorded, reminders a day out and two hours out, one-tap cancellation, and a no-show contact inside the hour against a 70% recovery target, so the seat is resold rather than mourned.

   THE RETURN

   Assume a hundred and fifty covers booked a week and a five percent no-show rate. That is around thirty covers a month lost at $85 each. Recover most of them with a reminder landing two hours before the table and the arithmetic is not complicated.

6. CH-06

   Funnels

   Capture

   SUBSTRATE — NO COMPONENT OF ITS OWN

   Not one of the nine, and not decoration either. This is part of what the nine run on: get it wrong and every component above it misbehaves in a way that is very hard to debug six weeks later.

   THE FAULT

   The site has a reservation button and nothing at all for the money: no path that turns a Christmas party enquiry into a deposit, no set-menu route, and no way to sell a Tuesday to the people who already love the room and would come if asked.

   ONCE IT IS RUNNING

   Conversion paths for what a restaurant sells beyond a table: a private hire route capturing guest numbers, date and budget before contact details, a festive and set-menu path that takes a deposit rather than a promise, and a midweek offer page shown only to the segment that needs it.

   THE RETURN

   Take the festive window. If that enquiry path converts four extra party bookings at twenty-five guests and $55 a head, it has returned $5,500 in a single quarter from a page that sits there all year and costs nothing to run once built.

7. CH-07

   AI Studio website

   Capture

   SYSTEM COMPONENT 04Professional Website

   A restaurant site that answers the four things people actually check: the menu as text rather than a PDF, the opening hours, how to book, and where to park. Private hire and events on their own page because that is a different buyer with a bigger budget, and a booking form that takes covers and occasion before contact details.

   • Menus as readable text, not a PDF nobody can open
   • Opening hours and parking where people look for them
   • Private hire and events on their own page
   • Booking form takes covers and occasion first

   THE FAULT

   The menu is a PDF that will not open on a phone, the hours are wrong for bank holidays, and the private dining page does not exist. A guest checking whether you do a Sunday roast leaves the site without ever reaching the booking button.

   ONCE IT IS RUNNING

   Menus rendered as text a phone and a search engine can both read, hours and parking where people look for them, a private hire and catering page written for a buyer with a budget rather than a diner, review snippets on the page, and the booking calendar built in rather than linked out.

   THE RETURN

   If the site takes a thousand visits a month and a third bounce at a menu that will not open, that is over three hundred people who wanted to eat with you. Convert one in twenty into a table of two at $85 a cover and the site pays for itself every month.

8. CH-08

   Nurture campaign

   Nurture

   SYSTEM COMPONENT 02AI Outbound Caller

   The two calls a restaurant never makes are to the enquiry about a private event that was never followed up, and to the regular who has not been in for three months. This makes both. The event call happens at day two while the enquirer is still choosing a venue, which is the only window that exists.

   • Private event enquiries called at day two, inside the window
   • Regulars called when their visit gap doubles
   • Large-party bookings confirmed by voice before the date
   • Stops on a booking or an opt-out

   SYSTEM COMPONENT 08Database Reactivation

   A restaurant list is mostly people who came once for a birthday and never returned, and event enquirers who booked somewhere else. Six months of silence starts a sequence that leads with what has changed — a new menu, a new season — and a reason to come on a Tuesday, which is the night that actually needs filling.

   • Six months since the last cover starts the sequence
   • Leads with a menu or season change, not a discount
   • Aimed at midweek covers, which is where the gap is
   • Any reply puts them back on the booking list

   THE FAULT

   Half the database came in once for an anniversary two years ago and has heard nothing since, and the event enquirer who chose the hotel down the road is still sitting on the list with nothing scheduled against them at all.

   ONCE IT IS RUNNING

   A stalled-enquiry sequence on private hire that lands at day two while the venue is still being chosen, an outbound call on the parties worth a voice, and a dormant-guest programme whose reason for writing is a changed menu or a turned season, not money off.

   THE RETURN

   Assume eight hundred guests on the list who have not booked in a year. A reactivation message bringing back two percent fills sixteen tables. At four covers and an $85 average that is over $5,000 from a list you already own outright.

9. CH-09

   Review automation

   Proof

   SYSTEM COMPONENT 06Review Harvesting

   The ask goes out the morning after the meal, not two hours after it. Nobody writes a restaurant review in the car park, and asking during dessert puts a server in an awkward position. The next morning, while the meal is still the most recent thing they ate out, is the moment.

   • Fires the morning after, not during service
   • Never asked at the table by a server
   • One question decides whether a link is sent at all
   • A complaint reaches the manager before it reaches a listing

   SYSTEM COMPONENT 07Review Automation

   A regular eats with you fortnightly and must be asked once a year. The cadence caps them, spreads asks so a busy Saturday does not produce forty requests in one morning, and answers every review — because in hospitality an unanswered one-star is read as agreement, and the reply is read by more people than the review.

   • One ask a year per regular, whatever the visit count
   • Spreads a busy service across the following days
   • Every review answered, because the reply is read too
   • Target: 5–10 reviews a month for an active restaurant

   THE FAULT

   Restaurants are chosen on the most recent twenty reviews rather than the best ones, and a listing whose newest entry is four months old reads as a room that has slipped. Servers hate asking at the table, and they are right to hate it.

   ONCE IT IS RUNNING

   The request lands the morning after the table, never in the room and never from a server. A satisfaction question decides whether a public link appears at all, complaints reach the manager before a listing does, and asks are capped once a year per regular and spread so a full Saturday does not fire forty at once.

   THE RETURN

   Review velocity moves a restaurant in map results faster than almost anything else available in a week. A steady 5 to 10 a month is the target; if it puts you in the local pack and brings two extra tables a week at $85 a cover, the return is plain.

10. CH-10

    Seasonal automation

    Retention

    SYSTEM COMPONENT 09Lifetime Nurture Campaigns

    Restaurants have the best excuses to be in touch of any business: a new menu, a season, a birthday you recorded at a booking eleven months ago. Those go out on their own clocks, the anniversary of a first visit is used deliberately, and the referral prompt runs monthly because people ask each other where to eat constantly.

    • Menu and seasonal messages on their own clocks
    • Birthdays used from the booking record, a year later
    • Midweek offers timed to the quiet nights
    • Monthly referral prompt, because people ask where to eat

    THE FAULT

    Every restaurant owns a calendar that repeats and almost nobody works it. The festive party window that closes in October, Valentine bookings, the anniversary of a first visit, and the birthday written on a booking form eleven months ago and never looked at again.

    ONCE IT IS RUNNING

    Campaigns on their own clocks: festive enquiries opened early enough to matter, Valentine and Mothering Sunday waves, birthdays and first-visit anniversaries fired from the booking record, quiet midweek offers timed to the nights that genuinely need filling, and a monthly referral prompt.

    THE RETURN

    If the booking records hold six hundred birthdays and one in ten comes back for a table of four at $85 a cover, that is sixty tables and around $20,000 across a year, from dates you already collected at the point of booking and then never used.

11. CH-11

    Custom values

    Capture

    SUBSTRATE — NO COMPONENT OF ITS OWN

    Not one of the nine, and not decoration either. This is part of what the nine run on: get it wrong and every component above it misbehaves in a way that is very hard to debug six weeks later.

    THE FAULT

    The last sitting moves half an hour earlier in winter, the deposit for a large party changes, corkage goes up. Each figure is retyped wherever it appears, and confirmation messages keep quoting the summer sitting time to guests arriving in January.

    ONCE IT IS RUNNING

    Account-level values holding the reservation link, service and last-sitting times, the table-holding policy, the large-party deposit, the head chef name and the current set-menu price, so a seasonal change is one edit and every confirmation, reminder and reply says the same thing.

    THE RETURN

    A guest arriving at nine because a reminder quoted a last sitting you moved in November is a complaint, a comped course and quite possibly a review. Preventing one of those a month is worth considerably more than the minutes saved editing templates.

12. CH-12

    Custom fields

    Capture

    SUBSTRATE — NO COMPONENT OF ITS OWN

    Not one of the nine, and not decoration either. This is part of what the nine run on: get it wrong and every component above it misbehaves in a way that is very hard to debug six weeks later.

    THE FAULT

    Allergies, the regular who always wants table nine, the wheelchair access request and the fact that somebody came in for a birthday in March all live in free text, so the next booking arrives carrying none of it and the guest has to explain themselves again.

    ONCE IT IS RUNNING

    Structured fields for allergies and dietary requirements, preferred table and sitting, occasion type and its date, high chair and access needs, spend band, visit count and last visit, alongside the private hire fields for guest numbers, budget and event type.

    THE RETURN

    A guest greeted with the allergy already on the ticket and their usual table held is a guest who comes back. If that lifts a hundred regulars from six visits a year to seven, at four covers and $85, you are looking at over $30,000 across the year.

13. CH-13

    Forms and surveys

    Capture

    SUBSTRATE — NO COMPONENT OF ITS OWN

    Not one of the nine, and not decoration either. This is part of what the nine run on: get it wrong and every component above it misbehaves in a way that is very hard to debug six weeks later.

    THE FAULT

    The private hire enquiry form asks for a name and a message, so the manager rings back to establish the three things that decide whether the date is even possible: how many people, which date, and what they are willing to spend a head.

    ONCE IT IS RUNNING

    A booking form whose first fields are covers, date and sitting, with the allergy note captured before a name, a private hire enquiry taking guest numbers, event type, date flexibility and budget, and a short post-visit survey where a low score raises a manager task instead of a public link.

    THE RETURN

    If the manager spends fifteen minutes qualifying each of twelve event enquiries a month, a form that arrives complete gives three hours back and, more usefully, lets the impossible dates be declined in a sentence rather than a phone call nobody enjoyed.

Every figure in a return line above is an illustrative scenario with its assumptions in the sentence, so you can substitute your own. None of it is measured customer data. The only performance figures we publish as targets are the 70% no-show recovery on the recovery call and five to ten reviews a month.