The library ·Room & Screen · Edition 15
Restaurant GHL Snapshot Edition
Covers, not leads. A no-show on Friday is the whole margin.
A restaurant does not count leads. It counts covers, and a table of four that does not arrive at eight on a Friday is the evening's margin gone. This edition is written for the phone, the book and the waitlist.
The phone rings hardest at seven on a Friday, which is the one hour nobody in the building can answer it.
The case
What is going wrong now
Four things, specific to a restaurant. If none of them is true of your week, this edition is not worth $935 to you and we would rather you knew that here than after paying.
01
The phone during service
Between seven and nine the host stand has a queue and the pass is calling for a runner, and the phone rings through all of it. Every ring that goes unanswered is a party of four booking somewhere else on the same street.
02
Friday's empty four-top
A table that does not arrive at eight cannot be sold again at half past. The food was prepped, the section was staffed and the covers do not come back later in the week.
03
Large parties, no deposit
A booking for fourteen is agreed by text on a Wednesday with no card taken and no menu settled. On the night nine people arrive, the kitchen has prepped for fourteen, and nobody wants to have that conversation at the door.
04
The morning-after ask
The guest leaves happy, the review request goes out at ten the next morning, and by then the meal is competing with the school run. The ones who still write are usually the ones who had something to complain about.
The change
What is different by the second month
- The Answering Desk
Answered mid-service
The seven o'clock call is picked up on the first ring while the host is seating a table, and the date, the party size and the name are taken without anyone leaving the floor. A caller asking about twelve people on a Saturday goes to the private hire enquiry instead of being squeezed onto the book.
- The Diary Guard
Fewer gaps at eight
Every booking is confirmed when it is made and reminded on the afternoon of service, with a one-tap way to release the table when plans have changed. Seventy per cent recovery of no-show covers into a refilled table is the target the sequence is built to.
- The Standing Page
A card before the date
Large-party and private-hire enquiries land on their own form, which asks the date, the head count, the occasion and dietary requirements, and holds nothing until a card has been taken. The kitchen then prepares for a number somebody has actually committed to.
- The Ask
Asked at the table
The review request reaches the guest as the bill is settled, while the dessert plates are still down and they can name the dish and the server. Waiting until the next morning turns a specific evening into a general impression.
The specimen sheet · Restaurant
The nine, cut for a restaurant
The same nine components every edition carries, written for what actually happens in a restaurant. Cover the title and you should still know whose page this is.
The Answering Desk
AI receptionist, on the phone around the clock
The phone rings at ten past seven on a Friday, when the host stand has a queue and the pass is calling. The desk answers on the first ring, takes the date, the party size, the name and the number, offers only what the book actually has free, and moves a party of twelve to the private hire enquiry rather than writing it onto the ordinary book. It also handles the questions that eat a host's evening: the parking, the corkage, whether the kitchen can manage a nut-free table on a Saturday.
- Answers at seven on a Friday
- Offers only what the book has free
- Moves large parties to private hire
The Message Desk
AI chat across the site, text, email and social
The message that arrives on Instagram at half past eleven asks whether Saturday has anything at eight for six and whether the tasting menu can go vegetarian. The desk answers from the actual menu and the actual book, holds the table while it does, and asks about allergies before confirming rather than discovering them at the pass. Site chat, Google messages and social all land in one thread, so the same guest is not answered three times by three different people.
- Answers from the menu, never guesses
- Asks about allergies before confirming
- One thread across site and social
The Standing Page
the website, written and built to be found
The pages are built for a guest deciding at half past five where to eat at eight, so the menu, the hours and the booking button come before the story of the chef. The menu is real text on the page rather than a PDF, which means the dish somebody is searching for within a mile of you can actually be found. Private hire has a page of its own with room capacity, minimum spend and deposit terms in plain sight, because an organiser who cannot find those moves on to the next dining room.
- Menu as readable text, not a PDF
- Booking button above the chef's story
- Hire capacity and terms shown plainly
The Diary Guard
confirmations, reminders and no-show recovery
A booking is confirmed the moment it is taken and reminded on the afternoon of service, with a one-tap release for a guest whose plans have changed, because a table given back at four can still be sold at eight. Large parties run to a different rhythm: a deposit when the date is held, a menu confirmation a few days out, and a final head count the day before so the kitchen orders to a real number. When a table does not arrive, the waitlist is offered it within minutes, with seventy per cent recovery of those covers as the target.
- One-tap release on the afternoon
- Head count confirmed the day before
- Waitlist offered the table within minutes
The Callback Round
AI outbound calling on misses and cold leads
Calls that ring out during service do not sit in a voicemail box until Monday. They are returned the same evening once the first sitting has settled, and the round also works the Saturday waitlist when a cancellation opens a table, calling in the order people joined rather than emailing everyone at once. Private hire enquiries that went quiet after the quote are called before the date they asked about, not after it has passed.
- Returns missed calls the same evening
- Calls the waitlist in joining order
- Chases hire enquiries before their date
The Ask
the review request, fired at the right moment
The ask fires at the end of the meal, while the guest is waiting on the card machine and can still name what they ate and who looked after them. That timing is the whole difference in a restaurant: at the table you get the lamb and the server by name, and by ten the next morning you get the word nice. It is sent only to bookings that were actually seated, so nobody who failed to turn up is asked how their evening was.
- Fires as the bill is settled
- Guests can still name the dish
- Never sent to a no-show
The Review Press
the ongoing review engine and its cadence
A regular can be asked more than once, but not on every visit, so a guest who has already written is held back for several months however often they come in. Anything under four stars reaches the manager's phone before it reaches the internet, because a cold main is fixable this week with a table and a conversation and a public reply cannot fix anything. What comes back is set on the menu page and the private hire page, with five to ten reviews a month as the target the cadence is built around.
- Holds regulars back for months
- Cold-main complaints reach the manager first
- Set on menu and hire pages
The Cold File
database reactivation of dormant contacts
Every restaurant has guests who came in three times one autumn and have not booked since, and almost none of them stopped for a reason worth remembering. The file goes back to them only when there is something to say: a new menu on, the anniversary of the room they hired last year, a quiet January midweek that needs filling. It names what they ate or what they booked last time, which is the only version of this message a guest believes.
- Reopens when the menu changes
- Names what they booked last time
- Fills quiet midweek sittings first
Standing Type
lifetime nurture, seasons, referrals
A restaurant's year is a fixed calendar of dates that everybody leaves too late to book: birthdays, anniversaries, Mother's Day, the office Christmas party organised in November that should have been sold in September. The standing type works those dates ahead of the rush and keeps the birthday on the guest record, so the note goes out a fortnight before rather than on the day the book is already full. Regulars hear about a new menu before it is announced, which is the closest thing a dining room has to a loyalty scheme.
- Birthday note sent a fortnight ahead
- Christmas parties sold from September
- Regulars hear about menus first
The run · Restaurant
The run, in a restaurant
Five formes, from the first enquiry to the guest you still have in three years.
A forme is the page of type locked up and put on the press. Five of them make an edition: setting, proofing, imposition, impression, and the type left standing for next time.
Setting
lead capture and first contact
A booking enquiry arrives in exactly the hour when every person in the building is already on the floor.
1.1The call
The seven o'clock ring is answered on the first ring, and the date, party size, name and number are taken without a host leaving the stand. A caller asking about twelve people on a Saturday is moved to the private hire enquiry rather than written onto the ordinary book.
1.2The message
A question on Instagram at half past eleven about a vegetarian tasting menu is answered from the actual menu, and the table is held while the conversation happens. Allergies are asked about before the booking is confirmed rather than discovered at the pass on the night.
1.3The form
Ordinary bookings and private hire use different forms, because one needs a time and a number while the other needs a head count, an occasion, dietary requirements and a card. The hire form shows the minimum spend and the deposit terms before it asks anybody to fill anything in.
Proofing
the ten-day nurture
A large-party enquiry that does not close on the first exchange deserves ten days of proper follow-up, because it is worth a whole section of the room.
2.1Days one to three, by email
The first days send the private hire menus, the room photographs and the deposit terms in one place, so the organiser can forward the lot to whoever is paying. Nothing in them asks for a decision yet, because an office party is decided by a group rather than a person.
2.2Days four to seven, by text
From day four a short text asks the single question that unsticks it: the head count, or which of the two dates they are holding. Text suits an organiser arranging this between meetings who is never going to open an attachment on a phone.
2.3Days eight to ten, by voice
By day eight the call goes out before their date rather than after it, and offers to hold the room for a few days against a deposit. If the party has gone elsewhere that is recorded, and they go into the run for next year's Christmas season.
Imposition
booking and no-show prevention
A confirmed table is not a kept table, and on a Friday sitting the gap between the two is the evening's margin.
3.1The confirmation
Confirmation goes out the moment the booking is taken, carrying the time, the party size and how long the table is held for. A large party's confirmation carries the deposit receipt and the date the final head count is due.
3.2The reminders
The reminder lands on the afternoon of service with a one-tap release, because a guest who gives the table back at four is doing you a favour and should find it easy to do. Large parties get a menu confirmation a few days out and a head-count check the day before, so the kitchen orders to a real number.
3.3The recovery call
When a table does not arrive, the waitlist is called within minutes rather than at the end of service, while the kitchen can still cook it. Seventy per cent of those covers recovered into a refilled table is the target the sequence aims at.
Impression
reviews and social proof
The review a restaurant actually wants is written at the table, not in the car park the following morning.
4.1The ask
The ask fires as the bill is settled, while the guest can still name the dish and the person who served it. It goes only to bookings that were seated, so nobody who failed to turn up is asked how their evening went.
4.2The reply
Anything under four stars reaches the manager's phone before it reaches the internet, because a cold main is fixable this week with a table and an apology. A public reply cannot fix a bad Friday, and a manager with a phone number sometimes can.
4.3The display
What comes back is set on the menu page and the private hire page, where a guest choosing between two dining rooms at half past five is already looking. A review that names a dish sells that dish more reliably than a photograph of it.
Standing Type
retention and reactivation
A restaurant's year is a calendar of fixed dates that everybody books far too late.
5.1The season
Christmas parties are sold from September, Valentine's from the middle of January, and Mother's Day before the florists start advertising. Quiet January and February midweek sittings are worked separately, because a midweek table needs a reason rather than a reminder.
5.2The support line
Between visits the same line handles what used to interrupt service: the allergy question, whether the room is free on a Thursday, what time the kitchen stops. A regular asking about the new menu reaches a person rather than a form.
5.3The revisit
Guests who came in regularly one season and then stopped are revisited when the menu changes or the anniversary of their hire comes round. The note names what they booked or what they ate, which is what makes it read like a restaurant and not a mailing list.
The delivery list · Restaurant
What actually lands in the account
Thirteen things arrive with every edition. Below each one is the problem it is there to solve for a restaurant, what changes when it runs, and how it pays for itself. No quantities are quoted, because a counted promise is a promise, and we would rather make the ones we can keep.
- 01
1 AI Receptionist
- The problem
- The phone rings hardest between seven and nine, which is the hour every person in the building is on the floor and the host stand already has a queue.
- What changes
- Booking calls are answered on the first ring right through service, taking the date, the party size and the name, and routing anything over ten to private hire.
- How it pays back
- If six calls a week ring out and one of them was a table of four, the phone alone puts a table a month back onto the book.
- 02
1 AI Chatbot
- The problem
- Half the enquiries now arrive on Instagram and Google after eleven at night, asking about the tasting menu, allergies and whether Saturday has anything left at eight.
- What changes
- They are answered from the actual menu and the actual book, allergies are asked about before confirmation, and every channel arrives in one thread.
- How it pays back
- A midnight message that becomes a Saturday booking costs nothing to answer and would otherwise have been read at ten the next morning.
- 03
Pipelines
- The problem
- Ordinary bookings, waitlist guests and private hire enquiries sit in one undifferentiated list, so a party of thirty is handled like a table for two.
- What changes
- Private hire runs enquiry to quote to deposit to menu confirmation to final head count, while the waitlist and the ordinary book run on tracks of their own.
- How it pays back
- On a Monday the manager can see which hire enquiries have not paid a deposit and which still owe a head count for a date this month.
- 04
Workflows
- The problem
- Confirmations, deposit chasing and head-count reminders get done by whoever has a spare moment, and in a busy week nobody has one.
- What changes
- Each runs on its own trigger, so the deposit request goes out when the date is held and the head-count check goes out the day before, whatever kind of week it has been.
- How it pays back
- The busiest week is the week these used to be forgotten, and it is also the week a missing head count costs the kitchen the most.
- 05
Appointment reminders, confirmations and no-show recovery
- The problem
- A table booked on Tuesday for Friday at eight has been forgotten by Thursday, and the guest never cancels because cancelling feels awkward.
- What changes
- The reminder lands on the afternoon of service with a one-tap release, and any table that goes unclaimed is offered straight to the waitlist.
- How it pays back
- Seventy per cent recovery of no-show covers is the target, and on a Friday sitting that is the difference between a full room and a section standing empty.
- 06
Funnels
- The problem
- The private hire enquiry usually comes through the same contact form as everything else, so nobody learns the head count, the occasion or the budget until the third email.
- What changes
- Private hire, large parties and the waitlist each have a page of their own, with room capacity, minimum spend and deposit terms stated before anyone fills anything in.
- How it pays back
- An organiser who can see the terms up front either books or moves on, and both outcomes save the manager a week of email in September.
- 07
AI Studio website
- The problem
- Most restaurant sites bury the menu in a PDF and open with the chef's story, while the guest deciding at half past five only wants the hours and a table at eight.
- What changes
- The menu is real text on the page, the booking button sits above the story, and the private hire room has its own page with capacity and deposit terms.
- How it pays back
- A menu a search engine can read brings in the guest hunting for one particular dish within a mile of the door, on the night they are hunting for it.
- 08
Nurture campaign
- The problem
- A guest who came in three times one autumn and then stopped is not annoyed with anyone; they simply forgot, and nothing ever brought them back.
- What changes
- Birthdays, anniversaries and the date they last booked sit on the guest record, and the note goes out ahead of the rush rather than on the day the book is full.
- How it pays back
- Filling a quiet Wednesday with regulars reminded a fortnight earlier costs a message, whereas an empty Wednesday still costs the full rota.
- 09
Review automation
- The problem
- The ask goes out the next morning if it goes out at all, and by then a specific evening has flattened into a vague good impression.
- What changes
- The request fires as the bill is settled, only to tables that were actually seated, and anything under four stars reaches the manager before it reaches the public.
- How it pays back
- Five to ten reviews a month is the target, and a recent set of them is what decides a guest choosing between two dining rooms at half past five.
- 10
Seasonal automation
- The problem
- Christmas parties are organised in November by people who should have booked in September, and Valentine's fills in the final ten days or does not fill at all.
- What changes
- The seasonal run sells the fixed dates ahead of the rush and works quiet January and February midweek sittings with a reason rather than a reminder.
- How it pays back
- A Christmas book half sold before December begins is a kitchen that can order properly and a rota somebody can actually write.
- 11
Custom values
- The problem
- Opening hours, the corkage charge, the private hire minimum spend and the deposit terms are typed into messages all over the account, and they change with the season.
- What changes
- They are held once as custom values and pulled into every confirmation, reminder and reply, so a change of winter hours is one edit.
- How it pays back
- When the kitchen closes half an hour earlier from November, nothing goes out quoting the old time and seating a guest into a closed pass.
- 12
Custom fields
- The problem
- A contact record holding a name and a number has nowhere for an allergy, a preferred table, the occasion, or the fact that this guest brings eight people every December.
- What changes
- Those sit on the guest record, so a returning guest's confirmation already knows about the nut allergy and the anniversary they always book.
- How it pays back
- A guest greeted with the thing they mentioned last time is the cheapest loyalty a dining room can buy, and it costs one field on a record.
- 13
Forms and surveys
- The problem
- Waitlist names go on a pad at the host stand, dietary requirements arrive by text to somebody's personal phone, and neither survives the end of the shift.
- What changes
- The waitlist, the large-party enquiry and the dietary form all write straight to the guest record with the date and the party size attached.
- How it pays back
- When a Friday table drops out, the waitlist is a list somebody can call rather than a page of handwriting nobody can read.
The hours
Eight to twelve hours a week
Assume the restaurant takes seventy booking calls in a week, that two thirds of them arrive between six and nine when the floor is at its fullest, and that a host loses three minutes to each one including the walk back to the stand. That is most of four hours of service time spent on the phone rather than in front of guests, before counting the calls that simply ring out. The desk takes those calls and the confirmations while the floor keeps working. Put your own call volume and your own service hours through the same arithmetic.
When it pays back
Suppose an average cover is fifty-five dollars and a month of Friday sittings loses two tables of four to no-shows. That is eight covers of food and wine that were prepped and staffed for and never sold. If the afternoon reminder and the waitlist offer recover even half of those tables across a quarter, the edition has paid for itself on no-shows before anything else in it has been counted. Use your own average spend per head and your own no-show count; the sum is a method, not a forecast.
The scenario assumed
- Assumed: an average spend of fifty-five dollars a cover.
- Assumed: two tables of four lost to no-shows in a month.
- Assumed: half of those tables refilled from the waitlist.
An illustration with its assumptions printed beside it, not a measured result. Change any assumption and the answer changes.
The arithmetic desk
Do the sum with your own numbers
Nothing below is a result anybody has measured. It is your four numbers multiplied together, printed with the assumptions showing, so you can see what the answer depends on and change any of it. If the sum does not work at your numbers, it does not work.
The only performance figures we quote anywhere are the system’s targets: a seventy per cent no-show recovery and five to ten reviews a month. Neither is used in this sum.
Installation
Free. 11 hours, inside 9 days.
Installation is free: eleven hours of dedicated installation time, to be booked and used within nine days of purchase.
That is eleven hours of work, not nine days of standing by. When the hours are used or the nine days are up, further work is quoted.
Delivery
Your edition is set and sent inside one working day — twenty-four business hours, counted 9am to 5pm Central, Monday to Friday. Nothing goes out at the weekend.
9am–5pm Central · 10am–6pm Eastern · 3pm–11pm UK
Refunds
All sales are final. Once the order is created and the snapshot link has been sent, the edition is non-refundable — the link is the goods, and it cannot be returned once it has been handed over.
Questions before you buy, or want a look at an edition first?Book a call and someone will walk you through the account rather than send you a brochure.
The hours cover
- Loading the edition into your GoHighLevel account
- Rebranding the website — your name, your colours, your copy corrections
- A2P / 10DLC registration and setup
- Email service setup, including your own domain email inside GoHighLevel
- A few extra automations where your process needs them
Never included, on any package
- Third-party integrations
- Third-party software
- Custom software development
Those three are quoted separately, or run by a GoHighLevel VA on a retainer. They are not withheld — they are simply a different job with a different price, and pretending otherwise is how installation windows overrun.
Queries · Restaurant
What a restaurant asks before buying
01Does this replace OpenTable or my table-management system?
No. It sits in front of the book rather than in place of it: enquiries, confirmations, reminders, deposits, the waitlist and reviews all run here, while your existing system keeps the floor plan and the covers. Where your system offers a booking link, the desk hands the guest straight to it and records the outcome on the guest record so the follow-up still runs.
02How does it handle walk-ins and the Saturday waitlist?
The waitlist is a form at the host stand and a link the desk can send, so a guest told forty minutes gets a text when the table is ready instead of standing in the doorway. When a booked table does not arrive, the waitlist is called within minutes and in the order people joined it, not at the end of service. Walk-ins who leave a number stay on the record and are worked for the following weekend.
03Can it take a deposit for a large party or a private hire?
Yes, and the private hire flow is built around that being the whole point. The enquiry form asks the date, the head count, the occasion and dietary requirements, the terms and minimum spend are shown before anyone fills it in, and the date is held once a card has been taken. The menu confirmation and the final head count then run to their own dates so the kitchen orders to a number somebody has committed to.
04When exactly does the review request go out?
As the bill is settled, while the guest is still at the table and can name what they ate. It is sent only to bookings that were seated, so a no-show is never asked how their evening was, and a guest who has already written is held back for several months however often they eat with you. Anything under four stars reaches the manager's phone before it reaches the internet.
05How quickly does it arrive, and who sets it up?
The snapshot link is sent inside one working day, counted as twenty-four business hours between nine and five Central, Monday to Friday, with no weekend deliveries. Installation is free: eleven hours of installation time, to be used within nine days of purchase, which covers your number, your service hours, your menus and your private hire terms. All sales are final once the snapshot link has been sent, so ask everything you need to ask beforehand.
Letters
Sample setting
The review wall, in proof
These are sample entries, written by us to show how this section reads. They are not customers, not testimonials and not results. Real reviews replace them the moment we have them, and the structured data stays switched off until they do.
The part I did not expect was the recovery call. Somebody booked a Saturday slot, did not answer the door, and the account had already called them and rebooked for Monday before I had finished the job I was on. That would have been a lost morning before.
Sample entry — a plumbing companyOwner, three vans
What sold it was that the reminders say nothing clinical. I have seen systems text a patient the name of their treatment. This one sends the time, the chair and a way to move it, which is all it should ever have said.
Sample entry — a dental practicePractice manager
Loading it was the easy half. Getting the registration through and the domain email actually delivering was the half I always underestimate, and that was the part they did without me chasing it.
Sample entry — an agency principalRuns eleven sub-accounts
The writing is the difference. It knows the difference between a storm call and a maintenance call, and it asks the questions in the order I would ask them. I have bought snapshots that clearly did not know what a supplement was.
Sample entry — a roofing contractorOwner
The shelf
Other editions on the shelf
Same system, different trade, different writing.
The last word
Take the Restaurant edition
$935, once. Your edition is set and sent inside one working day — twenty-four business hours, counted 9am to 5pm Central, Monday to Friday. Nothing goes out at the weekend. Installation is free and included: 11 hours to be used inside 9 days. All sales are final. Non-refundable once the snapshot link is sent, which is why the whole specimen is published above.
- Delivery
- Your edition is set and sent inside one working day — twenty-four business hours, counted 9am to 5pm Central, Monday to Friday. Nothing goes out at the weekend.
- Installation
- Installation is free: eleven hours of dedicated installation time, to be booked and used within nine days of purchase. That is eleven hours of work, not nine days of standing by. When the hours are used or the nine days are up, further work is quoted.
- Refunds
- All sales are final. Once the order is created and the snapshot link has been sent, the edition is non-refundable — the link is the goods, and it cannot be returned once it has been handed over.
- Rates
- 17 editions, $885 to $2,485. No edition is ever discounted below $850.