How to Launch the Restaurant Snapshot in 24 Hours

You did not buy Restaurant Snapshot to spend three weeks reading docs. You bought it because Friday night is in five days and you need the no-show recovery flow firing before service. Most operators stall out at hour six because they hit a CSV column they cannot map, or they get stuck waiting on 10DLC approval, or the GM never gets shown the dashboard and quietly stops looking at it. This guide is the clock-by-clock plan we use to get a single-unit restaurant fully live in one calendar day, with every workflow tested against real reservations before dinner service the next night.

The 24 hours assumes you have an owner or operator who can give the project their attention in two long blocks. Multi-unit operators should plan on 24 hours of work spread across three calendar days — the install itself is the same, but staff training has to land at each location.

Why This Matters

Every hour Restaurant Snapshot is sitting idle in your GHL sub-account is an hour of no-shows you cannot reclaim, birthday revenue you are not capturing, and review velocity you are not building. A typical 80-seat full-service restaurant leaves about $4,200 a month on the table when these flows are off — most of it from no-shows that never get refilled and birthday guests who never get pinged. Twenty-four hours of focused setup is the cheapest week of revenue you will ever buy back.

The other reason to compress the install is staff buy-in. If the host stand sees the no-show reclaim work on the first Friday, they will trust the system. If they see it half-built for two weeks, you will be fighting them for a quarter to get them to actually use it.

Prerequisites — What You Need Before You Start

Do not start the clock until you have all of these on the desk. Hunting for a logo file at hour nine is how a 24-hour install becomes a 72-hour install.

• A GoHighLevel Pro plan with a sub-account already created for the restaurant
• POS export — last 12 months of guest data as CSV, with email, phone, last visit, and lifetime spend if available
• Stripe account connected to GHL, with the deposit product already created
• Brand assets — logo in PNG and SVG, primary and accent hex codes, the exact spelling of your restaurant name as it appears on the sign
• A local phone number you can either buy fresh in GHL or port in (porting takes 5-10 business days, so buy fresh if you are on the clock)
• Your EIN and a legal business address for 10DLC registration
• Reservation platform credentials (OpenTable, Resy, SevenRooms, or Tock) for the booking webhook
• A test phone — one you can text to during the no-show simulation that is not the owner’s primary line

The Step-by-Step Plan

Hour 1-2: Import contacts and tag by daypart

Open the GHL bulk import, map your CSV columns to first name, last name, email, phone, last visit, and lifetime spend. Before you hit import, add two custom fields: favored_daypart (brunch, lunch, dinner, late-night) and visit_frequency (one-time, occasional, regular, VIP). Run a quick SQL-style filter on your CSV beforehand so each guest gets bucketed. The system will work without these tags, but every downstream segment — weekly specials, birthday comps, win-back campaigns — gets sharper when the tags are clean from minute one.

Hour 2-4: Configure the reservation deposit

Open the deposit workflow inside Restaurant Snapshot and set your party-size threshold. The default we recommend is a $25-per-person hold on parties of six or more, Thursday through Saturday only. Connect it to your Stripe product, then rewrite the deposit-required SMS in your own voice — the default vendor copy is fine, but your guests will trust a message that sounds like the host stand they already know. Test the Stripe charge with a real card you can refund.

Hour 4-5: Provision the SMS sender and verify the number

Buy a local long code inside GHL — pick an area code that matches your restaurant’s, not a national 8XX. Kick off 10DLC brand registration immediately; campaign approval usually lands in 1-3 business days for restaurants, but submit at hour four so it is not blocking you at hour twenty. Run a live test send from the GHL conversations tab to a staff phone and confirm two-way reply lands back in the inbox.

Hour 5-8: Brand the workflows and templates

Restaurant Snapshot ships with four core flows: no-show recovery, birthday comp, review request, and weekly specials. Each one has 6-12 SMS templates. Walk through every template and rewrite anything that does not sound like your host would say it out loud. Add your signature signoff — ”— [Restaurant Name]” with the em dash matters more than people think because it signals a human, not a bot. Drop your logo and brand colors into the email templates while you are in there.

Hour 8-12: Test the no-show recovery flow end-to-end

This is the test that earns you the trust of your FOH. Book a reservation under the test phone for 7:30 PM tonight on your reservation platform. At 6:30 PM, the T-1 hour confirmation SMS should fire. At 7:42 PM (12 minutes late), the reclaim sequence should send. Walk through every branch: the guest replying “running late,” the guest going silent, the guest cancelling. Confirm the waitlist blast template loads with the right table size and time. Anything that misfires gets fixed before hour twelve.

Hour 12-16: Test the birthday and anniversary SMS

In your contact list, find two test guests and backdate their birthdays to today. Watch the birthday flow fire. Confirm the comp offer (we default to a free dessert, not a percent off — desserts drive a return visit, percents discount one you would have gotten anyway) and the redemption code attach correctly. If you run an anniversary flow for couples who have dined with you on past anniversaries, test that branch too.

Hour 16-20: Turn on review-request automation

Connect your Google Business Profile and Yelp inside GHL. Set the post-visit delay to 90 minutes — long enough that the guest has paid, tipped, and walked to the car, but short enough that the meal is still in their mouth. Write a two-line review ask that mentions the server by name using the [server_name] merge field. Restaurants that name the server in the review ask see roughly 2.4x the review conversion rate of generic asks.

Hour 20-22: Schedule the weekly specials broadcast

Load the next four Tuesdays of specials into the broadcast queue, scheduled for 10 AM each Tuesday. Pre-write fallback copy your sous chef can swap in if a special 86s before Wednesday. Tag the broadcast to fire only to guests with favored_daypart matching the special’s daypart — do not send a brunch special to a dinner-only regular.

Hour 22-24: Train FOH and BOH on the dashboards

There are three dashboards your staff will actually use. Walk the GM through the covers dashboard (booked, seated, no-show rate by daypart). Walk the host through the no-show recovery dashboard (who is late, what the flow has done, what action they need to take). Walk the chef through the review velocity dashboard so they can see what guests are saying about the food in near-real-time. Anything past these three is a distraction in week one.

Common Mistakes to Avoid

Skipping 10DLC registration until you need it. A2P 10DLC brand approval can stall an entire launch. Submit at hour four, not hour twenty. If you wait until you are ready to send, you will sit in a 1-3 day queue with everything else done and nothing to do.

Importing without de-duplication. Most POS exports have the same guest entered three or four times with phone-number variations (with and without the country code, with and without dashes). Run a phone-number normalization pass before import or your birthday flow will send the same guest three SMS on the same day.

Letting the GM watch the install but not touch it. If the operator does the entire setup and the GM only attends a 30-minute handoff, the system dies in week three. Give the GM two specific tasks during the install — usually the SMS rewrite and the dashboard tour — so they have hands on it before service.

Defaulting to vendor copy. Restaurant Snapshot ships with serviceable defaults, but the host of a fine-dining room and the manager of a fast-casual taqueria do not text guests the same way. Rewrite every template. The hour you spend doing this is the difference between a 14% reply rate and a 38% reply rate.

Testing on the owner’s phone only. The owner has been in the contact database for two years and has every tag possible. Test with a brand-new phone number you have never used so you can see what a real new guest sees.

Forgetting the BOH lives in the comp data. If the chef does not see what desserts are being comp’d for birthdays, you will run out of the dessert that fires in the comp flow. Loop the BOH in on hour twenty-three, not hour thirty.

What Success Looks Like

By the end of hour twenty-four, your restaurant is sending automated SMS to guests on five different triggers, with branded copy, with a working deposit hold on large parties, and with a staff that has watched a no-show reclaim work in front of them. By the end of week one, you should see your first reclaimed table during a live Friday service. By the end of week two, your Google review velocity is roughly 2-3x your baseline. By the end of month one, deposit-required large parties have cut your six-top no-show rate by something on the order of 60-70%, and birthday revenue has become a measurable, recurring line on your weekly report.

Operators who land the 24-hour install cleanly tend to recover the cost of Restaurant Snapshot inside the first two weekends of dinner service. Operators who let it drift into a three-week install usually never quite get there.