Restaurant DM Automation in GoHighLevel: Full Walkthrough (No-Code)

The Instagram DM Problem Every Restaurant Owner Ignores

Someone opens Instagram on a Tuesday evening, sees your restaurant's reel, and types: "Do you have a table for 4 this Friday at 7pm?"

What happens next determines whether they sit in your dining room Friday or someone else's.

The average restaurant Instagram DM response time is 4 hours and 17 minutes. The average booking decision window — the time between sending the first inquiry and booking somewhere — is under 15 minutes.

That is not a staffing problem. That is not a training problem. That is a structural mismatch that costs you covers every single week.

Here is what the data looks like on the ground:

• 60% of restaurant Instagram DMs never receive a reply at all. The message sits in the "requests" folder, unseen, while the customer books at the place that replied in 3 minutes.
• When a restaurant does reply within 5 minutes, booking conversion is 3–4x higher than replies sent after an hour.
• The customer who books elsewhere rarely leaves a negative review. They simply never come back — and you never know why.

The table was never yours to lose. You just were not in the room when the decision was made.

This walkthrough fixes that. By the end, you will have a GoHighLevel automation that:

1. Responds to a booking-intent DM within seconds — at 2am if needed
2. Qualifies party size, date, and time through a natural conversation
3. Sends your direct booking link the moment the customer is ready
4. Fires a 24-hour pre-visit reminder so no-shows drop

No code. No developer. No monthly per-seat software cost beyond your existing GHL subscription.

What the Automation Does — The Full Flow

Before touching a single setting, understand the sequence you are building:

Customer DMs "table" or "reservation" or "book"
         ↓
Instant reply: "Hi! Thanks for reaching out to [Restaurant]. 
               We'd love to have you. Quick question — 
               how many guests will be joining you?"
         ↓
Customer replies: "4"
         ↓
"Perfect! What date are you looking at?"
         ↓
Customer replies: "Friday the 16th"
         ↓
"Great — and what time works best for your group?"
         ↓
Customer replies: "7pm"
         ↓
"We have availability. Here's your direct booking link: [link]
 Takes 60 seconds to confirm your table."
         ↓
Customer books → confirmation email fires
         ↓
24 hours before visit → reminder DM: "Looking forward to seeing 
you tomorrow at 7pm! Let us know if anything changes."

The entire qualification sequence runs inside Instagram DMs. The customer never leaves the app until they tap the booking link. That frictionless path is why conversion is high.

Prerequisites Before You Build

You need three things in place:

1. A GoHighLevel sub-account with a connected phone number and active subscription. If you are on the $97 Starter plan, you can run this — but the $297 Pro plan gives you unlimited contacts and more automation triggers. See this breakdown on which GHL plan is worth it in 2026 before upgrading.
2. A Facebook Business Suite account with your restaurant's Instagram page connected as an asset. The Instagram account must be a Professional account (not personal). If it is still a personal account, go to Instagram Settings → Account → Switch to Professional Account → Business.
3. An online booking page. This works with Resy, SevenRooms, OpenTable, a GHL calendar, or any page with a URL. If you do not have one, the simplest zero-cost option is a GHL calendar page set to "group appointment" — takes 10 minutes to configure.

Once those three are in place, the build takes 45–60 minutes the first time. Once you have done it once for a restaurant client, the template saves it to under 20 minutes per new account.

Step 1 — Connect Instagram to GoHighLevel

In your GHL sub-account:

1. Navigate to Settings → Integrations → Social Planner
2. Click Connect New Account → Facebook / Instagram
3. You will be redirected to Facebook's OAuth flow. Log in with the Facebook account that manages the restaurant's Business Suite.
4. When prompted to choose pages, select the Facebook Page that is linked to the restaurant's Instagram. GHL connects to Instagram through Facebook Pages — this is a Meta requirement, not a GHL limitation.
5. Grant all requested permissions. The critical ones are: Manage messages, Read user content, Manage Instagram messages.
6. Return to GHL. Under Settings → Integrations, you should now see the Instagram handle listed with a green "Connected" badge.

Common failure point: If the badge shows "Disconnected" after OAuth, it means the Instagram account is not formally linked to the Facebook Page in Business Suite. Fix this in Facebook Business Suite → Accounts → Instagram Accounts → Add → connect your handle. Then repeat the GHL OAuth.

Step 2 — Build the Conversation Trigger Workflow

Now you build the automation that fires when a DM arrives containing booking intent.

1. Go to Automation → Workflows → + Create Workflow → Start from Scratch
2. Name it: Restaurant IG DM Booking Flow
3. Click Add Trigger → search for Instagram DM → select it
4. Under trigger conditions, set:
   • Contains any of: table, reservation, book, available, friday, saturday, seat, tonight, tonight, dinner, lunch, tonight
   • Add your own local keywords — "iftaar", "dine", "walk in" — whatever your customers actually type
5. Check "Only trigger if no open conversation exists" — this prevents the automation from firing mid-conversation when the customer is already being qualified.
6. Click Save Trigger

Next, add the first action:

7. Click + Add Action → Send Instagram DM
8. In the message body, paste your instant reply. Keep it warm and direct:

   "Hi {{contact.first_name}}! Thanks for reaching out to [Restaurant Name]. We'd love to have you join us. Quick question — how many guests will be in your party?"

   GHL merges the first name automatically if Instagram provides it. If not, it sends without the name — no error.
9. Set a 1-second wait before this action fires. This prevents Meta's rate-limit from flagging it as a bot. A 1-second delay is imperceptible to the customer.

Step 3 — Build the Qualification Sequence

After the first reply, you need GHL to wait for the customer's answer and then ask the next question. This uses GHL's Wait for Response action.

1. After the first DM action, add: Wait → Wait for Instagram DM Reply
2. Set timeout to 2 hours. If no reply arrives in 2 hours, the workflow ends without sending further messages.
3. Add a Custom Field action: Store the customer's reply in a field called Party Size under the contact record. Use the merge tag: {{reply.message}}. This lets you reference it later in the confirmation message.
4. Add the second DM: "Perfect! What date are you thinking? (Day and date work great — e.g., 'Friday the 16th')"
5. Add another Wait for Reply (2-hour timeout)
6. Store reply in custom field: Booking Date
7. Add third DM: "And what time works best for your group?"
8. Add final Wait for Reply (2-hour timeout)
9. Store reply in custom field: Booking Time

Note on custom fields: In GHL, go to Settings → Custom Fields → + Add Field to create Party Size, Booking Date, and Booking Time before building this workflow. Name them clearly — you will reuse them in the confirmation message.

Step 4 — Send the Booking Link and Confirmation Message

After all three answers are collected, the workflow sends the booking link with a personalized summary.

1. Add action: Send Instagram DM
2. Message body:

   "Great news — we have availability! Here's your direct booking link to confirm your table for {{Party Size}} on {{Booking Date}} at {{Booking Time}}:
   
   [Your Booking URL]
   
   The whole process takes about 60 seconds. See you soon!"

3. Add action: Add Tag → tag the contact as DM Lead — Booking Sent. This lets you filter and report on DM-sourced bookings separately in your GHL dashboard.
4. Add action: Add to Pipeline → move the contact into a "Restaurant Leads" pipeline at stage "Booking Link Sent." Now you have a visual CRM view of every DM lead.

If you are using a GHL calendar as your booking page, you can go one step further: after the customer books, GHL fires a calendar-confirmation trigger automatically. Add a branch after the booking link step that listens for appointment creation and moves the contact to "Booked" stage automatically.

Step 5 — Build the 24-Hour Pre-Visit Reminder

No-shows are expensive. A single reminder DM cuts no-show rates by 20–40% in service businesses. Here's how to build it.

This is a separate workflow triggered by appointment confirmation, not by the DM flow.

1. Create a new workflow: Restaurant Pre-Visit Reminder
2. Trigger: Appointment Status Changed → Confirmed (fires when a GHL calendar appointment is confirmed)
3. Add action: Wait Until → set to 24 hours before appointment start time. GHL supports dynamic time conditions relative to appointment date — use the appointment date merge tag minus 24 hours.
4. Add action: Send Instagram DM:

   "Hi {{contact.first_name}}! Just a friendly reminder that your table for {{Party Size}} is confirmed for tomorrow at {{Booking Time}}. We're looking forward to having you! If anything changes, just reply here and we'll sort it out."

5. Add action: Send Email with the same reminder (belt-and-suspenders — customers who booked via email may prefer that channel).

If you are using Resy or SevenRooms rather than GHL calendar, the reminder workflow triggers differently: use a Tag Added trigger (when the "Booking Confirmed" tag is added to the contact via a Zapier/Pabbly webhook from your booking platform), then calculate the 24-hour window manually using a wait step.

What to Expect at 30 Days

These are realistic baselines for a restaurant running this automation with a modest Instagram following (5,000–20,000 followers) and 3–5 booking-intent DMs per week:

The time saving alone justifies the setup. The additional covers are the profit center.

At an average restaurant spend of $60–$90 per cover, recovering 8 covers a month is $480–$720 in revenue that was previously walking out the door — or rather, never walking in at all.

What to Charge for This as a Retainer Service

If you are building this for restaurant clients as an agency or freelancer, here is the pricing structure that holds in 2026:

Setup fee: $500–$800 (one-time)
Covers the GHL configuration, Instagram connection, workflow build, testing, and a 30-minute handover call. This is 4–5 hours of work the first time, under 2 hours once you have a template.

Monthly retainer: $400–$700
Covers GHL sub-account access (you white-label GHL at $297/month for the account, then resell at $400–700), monitoring, keyword updates as seasonal menus change, quarterly workflow audits, and a monthly report showing DM volume, conversion rate, and estimated revenue recovered.

Why restaurants pay this without hesitation: A restaurant owner who recovers 10 additional covers per month at $70 average spend is generating $700/month in recovered revenue. You are asking them to pay $400–700 to receive $700. The math is visible on a single slide.

The objection you will hear: "Can't I just hire someone to reply to DMs?" The answer is: a part-time social media manager costs $800–$1,200/month, is unavailable at 11pm on Saturdays when booking intent peaks, and cannot qualify and route 50 simultaneous DMs. This automation does all three at $0 marginal cost per additional DM.

For a deeper look at building a full AI automation retainer business that goes beyond single-workflow setups, see how to build an AI automation retainer business in 2026 without cold DMs.

The Playbook Behind the Playbook

This workflow is one component of a larger retainer offer. Restaurants that convert well on DM automation also benefit from:

• Google Business Profile review automation (request → respond → flag negative)
• Post-visit email sequences that drive repeat bookings (the easiest upsell once this workflow is live)
• Missed-call text-back for reservation phone inquiries
• Birthday and anniversary re-engagement campaigns using contact data collected through the DM flow

Each of those is a workflow addition, not a new system. One GHL account can run all of them for a single restaurant client.

If you want the complete system — the proposal template, retainer pricing calculator, workflow templates, and onboarding checklist for selling this to restaurants — the AI Retainer Playbook covers the full build:

Get the AI Retainer Playbook →

It is built for operators who want to go from "I built one workflow" to "I have five paying restaurant clients on retainer" — without cold DMs and without undercharging for the work.