Theme
Palette
Saved to this browser. Applied before the page paints, so it never flashes.
Hospitality & digital · SK-REST
Configured for a service-time phone: reservations and event enquiries answered while the floor is full, no-shows reduced, guests brought back.
What is in the kit
Every SubaccountKit snapshot contains the same nine components and nothing else. What changes between kits is what they are configured to say and do — everything below is written for the Restaurant Sub-Account Kit, laid out in the order it runs.
Stage 01Lead capture and first contact
Answers between seven and nine on a Friday when the floor is full, checks availability, books the table, and routes private dining and event enquiries straight to a manager.
Answers menu, dietary, parking and availability questions on the website, Instagram and SMS at any hour, and takes the booking inside the conversation.
Menu, private dining and event pages written properly, booking on every one, and enquiry forms that capture covers, date and occasion.
Stage 02Ten days of multi-channel follow-up
Calls guests who did not arrive, follows up event enquiries that went quiet, and reaches guests who have not visited since a particular occasion.
Stage 03Booking and no-show prevention
Reservations confirmed instantly with the time and party size, reminded at 24 hours, 1 hour and 15 minutes, and a recovery call inside the hour on a no-show — a Saturday table cannot be resold.
Stage 04Reviews and social proof
The ask goes out after the meal, while the evening is still fresh. One satisfaction question decides whether the guest sees the review link or reaches a manager.
Keeps a high-volume venue from over-asking regulars: requests paced per guest, platform rotation and monthly reporting on covers against reviews.
Stage 05Lifetime client nurture
Guests who have not visited in six months get a message built on their last booking — the occasion, the party size, the date — rather than a general offer.
Occasion anniversaries, seasonal menu launches, event-season early booking prompts and a referral reward aimed at regulars who bring groups.
The same nine ship in every kit in the catalog. Delivered within 1–2 business days of purchase confirmation. 12 hours of dedicated installation support, to be used within 14 days of purchase.
The end-to-end run
From a stranger’s first ring to a client of several years. This is the flow the Restaurant Sub-Account Kit wires into a sub-account on day one — the nine components above are what you get, and this is how they run together.
A stranger makes contact
Multi-channel entry with intelligent routing
The call is answered on the first ring, at any hour, in a natural speaking voice.
The same assistant, on every inbox the business owns.
A submission is the start of a sequence, not an entry in a spreadsheet.
They are interested but not ready
A ten-day multi-touch sequence across three channels
Establish who this is and why they should keep reading.
Shorter, closer, easier to act on from a phone.
The touch almost every sequence is missing.
They have booked
Protecting the slot from the moment it is taken
Confirmation lands before they have closed the tab.
Three reminders, three different jobs.
The slot is missed, and the phone rings while the intent is still warm.
The visit is done
Turning finished work into public evidence
Two hours after the visit, one question decides where it goes.
Reviews are answered, which is half of what a profile is judged on.
The reviews go back onto the site rather than sitting on a platform.
They are a client
Keeping the relationship alive for years, not weeks
Low frequency, long horizon, never silent for a whole year.
Existing clients get answers without waiting for office hours.
Nobody is allowed to quietly disappear.
The two performance figures above — a 70% no-show recovery rate and 5–10 reviews a month — are the system's design targets, supplied by the product team. They are not measured results from named customers, and they are never published as review or rating markup.
The problem it is pointed at
The busiest booking hour is the busiest service hour, and every unanswered ring is a table that fills somewhere else.
The highest-value call a restaurant gets arrives during service and sits unheard until the next morning.
A missed eight o'clock table on a Saturday is revenue that expires, and the reminder was a single email.
Names and emails are collected at booking and used only for a monthly newsletter nobody reads.
Built for
Not built for
If you are in the second list, say so and we will tell you what would actually help — or that nothing we sell would.
A restaurant taking 300 covers a week, missing about 45 calls, with an average cover worth $48 and 20 no-show covers a week.
~13.5 hours a week in this illustrative scenario — roughly 58 hours a month. Your figures will differ; the arithmetic is shown so you can substitute them.
When it pays back
Recovering fourteen of the twenty weekly no-show covers at $48 is roughly $2,900 a month in this scenario, and one saved private dining booking usually exceeds that on its own.
Run your own numbers
These are not measured customer results and never will be presented as such. They are arithmetic. Change any field and the sentence below changes with it — including the sub-account multiplier, because most people reading this are rolling the Restaurant Sub-Account Kit out across more than one client.
Illustrative arithmetic only. It assumes every missed enquiry is answered and that your own close rate holds on recovered contacts — neither is guaranteed, and both depend on your offer and your team. No figure here is a measurement from a real customer, and none of it is published as review or rating markup.
Between seven and nine on a Friday every phone call is a booking and nobody can answer it. That is the entire problem this configuration solves: the receptionist takes the call, checks availability, books the table and escalates anything unusual to a manager.
An event enquiry is worth many times a two-cover booking, and it is the one most likely to be lost to voicemail during service. Those calls are qualified and routed to a manager immediately.
A no-show table at eight on a Saturday cannot be resold. The reminder ladder and the same-hour recovery call exist for that reason, and in a restaurant they justify the system on their own.
Most restaurants collect names and email addresses and then send everyone the same newsletter. Here the win-back is based on the last visit — what they booked, when, how many covers — which reads as recognition rather than as a mailing list.
Small groups running per-venue sub-accounts should look at bulk sub-account provisioning.
Delivery and support
Clear edges make a better engagement than a long list of exclusions. Here is where the included support ends and where a quote begins.
Included with every kit
Quoted separately, or run by a VA
All four are real services we offer — seeintegrations, APIs and custom software. They are scoped and quoted so you know the cost before anyone starts.
Reviews
These are sample entries. SubaccountKit is new, so rather than invent testimonials we are showing clearly-labelled placeholders while the deck waits for real customers. Nothing here is published as review or rating markup either — search engines see no ratings from this site until the words are real.
This is a preview card so the review deck can be styled and tested before real feedback exists. The kit went into a fresh sub-account, the load sheet listed every custom value in order, and the build was finished before lunch.
Placeholder copy standing in for a real review. The point being illustrated here is the follow-up ladder stopping the moment someone books, which is the thing most sequences get wrong.
A preview entry, not a customer quote. It exists so the deck renders with a realistic length of text and the shuffle animation can be judged honestly before launch.
Sample text. Deliberately four stars rather than five, so the star row is tested at more than one value and the layout is proven before real reviews arrive.
Another preview card. Real reviews will replace every entry in this file, and the same change that swaps them in also switches the review structured data on.
It takes the enquiry, checks availability and books, including the calls that arrive at seven on a Friday when nobody on the floor can reach a phone. Anything unusual is escalated to a manager.
They are the highest-value calls a restaurant receives and the most likely to be missed during service. They are qualified and routed to a manager immediately rather than sitting in voicemail until Monday.
That is what the reminder ladder and same-hour recovery are for. A no-show table on a Saturday is revenue that cannot be recovered afterwards, so the reminders matter more here than almost anywhere.
The seven stages from signed client to live account.
Conflict list first, sending held back, links re-pointed.
The per-client step no kit can do for you. Start it on day one.
The exit conditions are the test, not the first message.
Ready when you are
Delivered within 1–2 business days of purchase confirmation, with 12 hours of dedicated installation support to use within 14 days.
No call required to buy a kit · replies within one business day
Accessibility
Text size
Display
Turning animation off tears down the WebGL grid and the particle field — they stop running, they are not just hidden.