Every operational playbook below also has a dedicated, short question page with a copy/paste AI Agent Prompt (lead tab) and ghl-tools MCP CLI command:
PLAYBOOK T01 · VOICE AI & KB
Stopping Voice AI Price Guessing & Robotic Cadence
Problem: Voice AI recites markdown bullets over the phone or invents service prices when callers ask off-script questions.
Fix: Never share a text prompt with Voice AI. Use short sentences, commas for pauses, and zero markdown. Load 20+ real customer Q&A pairs in the caller's exact words before going live, and define EMPTY as a mandatory human-transfer state so the receptionist never guesses a figure.
PLAYBOOK T02 · OFFER & PRICING
Selling the Paid Assessment Before Quoting Software
Problem: Pitching a $297/month chatbot subscription in cold DMs attracts price-shoppers and churns within 60 days.
Fix: Sell a paid workflow assessment of one recurring process first: (1) 45-minute owner interview, (2) written stall map, (3) first-change specification, and (4) review call. Once the process is scoped, run contacts and follow-up in GoHighLevel behind a $2,500/month retainer.
PLAYBOOK T03 · CONVERSATION AI
Eliminating Conversation AI Loops & Bad Replies
Problem: Unsupervised SMS/Instagram bots loop on multi-part questions or message VIP contacts who expect the owner.
Fix: Run Conversation AI in Auto-Suggest mode for the first 50 threads so a human taps send. Place a workflow guard in front of every AI node that immediately halts automation when a contact carries the vip-human-only, angry, or ai-conv-paused tag.
PLAYBOOK T04 · ROBOCALL DEFENSE
Blocking Google Business Robocallers with a 1-Step DTMF IVR
Problem: Automated scrapers call new Google Business tracking numbers and burn hundreds of paid Voice AI minutes.
Fix: Place a 1-step DTMF Call-Screening IVR in front of the forward or Voice AI agent: play a 4-second prompt ("Thanks for calling, press 3 to connect"), wait 5 seconds for digit 3, and drop calls that fail to press a key. Real callers connect; bots drop at zero AI cost.
PLAYBOOK T05 · DNS & DELIVERABILITY
Fixing Client DNS Delays & Configuring Apple Branded Mail
Problem: Client onboarding stalls for two weeks because CNAME records fail or outbound emails land in spam.
Fix: Verify authoritative RFC 1035 DNS resolution before sending a single campaign. Check for duplicated root domains in GoDaddy/Cloudflare host fields, enforce DMARC at p=quarantine or p=reject, and publish a square 1024×1024 SVG Tiny-PS logo for BIMI brand indicators.
PLAYBOOK T06 · SNAPSHOT SAFETY
Preventing Snapshot Overwrites on Active Client Sub-Accounts
Problem: Blind-pushing an updated agency snapshot overwrites a client's custom funnel copy, calendar links, or workflow steps.
Fix: Treat sub-accounts like versioned code. Maintain one declarative manifest per location, compute a SHA-256 diff of live workflows, custom fields, and funnel layouts before pushing, run a --dry-run check first, and read back the live state after applying changes.
PLAYBOOK T07 · MISSED-CALL ARCHITECTURE FOR HOME SERVICES
Built-In Missed-Call Checkbox vs. Custom 5-Step Workflow (Plumbing, HVAC & Roofing)
Problem: The built-in missed-call text-back checkbox fires at 0 seconds—even when a plumber or roofer wipes his hands and calls right back 15 seconds later—and sends a generic "Sorry we missed your call, how can we help?" message that gives a homeowner with an active leak zero direction.
Fix: Turn off the native checkbox and run a 5-step custom workflow: (1) Trigger on incoming Call Status in Busy, No-Answer, Voicemail, (2) Wait 45 seconds so the owner can dial back first, (3) Exit if an outbound call or manual SMS happened during the wait (using either a Workflow Goal Event on Outgoing Call/SMS or a tiny companion workflow that removes the contact on outbound touch), (4) Send a trade-specific intake text asking if it is an urgent repair or an estimate plus their street address, and (5) Trigger an owner push alert + Call Connect once they reply.
PLAYBOOK T08 · iOS 18+ LIVE VOICEMAIL & CALL TIMEOUT DIAGNOSTIC
Why iPhone Live Voicemail Breaks Missed-Call Text-Back (& The 2-Setting Fix)
Problem: When a GoHighLevel tracking number forwards to an owner's or technician's iPhone with the default 20–30 second timeout, Apple iOS 18+ Live Voicemail answers the call locally on the iPhone at ~18 seconds. The carrier reports 200 OK (Answered) to HighLevel, so Missed-Call Text-Back never runs and the lead lands in the tech's personal iPhone voicemail.
Fix: Apply two settings on every forwarded number: (1) Set Incoming Call Timeout to 15 seconds (Settings → Phone Numbers → Edit Number) so HighLevel pulls the call back before iOS intercepts at 18 seconds, and (2) Enable Call Whisper / Press 1 to Accept so even if the tech hits "Send to Voicemail" early, iOS voicemail cannot press 1 to bridge the call.
PLAYBOOK T09 · BRICK-AND-MORTAR DESK PHONE + VOICE AI TOPOLOGY
Using GoHighLevel Voice AI With an Existing Office Desk Phone (Zero GBP Number Swap)
Problem: Replacing a brick-and-mortar business's main phone number across Google Business Profile, trucks, and yard signs just to put GoHighLevel Voice AI in front of their office desk phone creates NAP consistency headaches and forces every repeat caller through a bot first.
Fix: Keep the shop's main phone number on Google Business Profile and let it ring the front-desk phone first for 3 rings (15 seconds). Configure Conditional Call Forwarding (*71 / Busy + No-Answer) on their existing carrier or VoIP desk phone to roll unanswered and after-hours calls into a dedicated GoHighLevel Voice AI number, while keeping GHL tracking numbers strictly on paid ad campaigns.
PLAYBOOK T05 · A2P 10DLC APPROVAL CHECKLIST
Getting A2P 10DLC Approved on the First Try
What Usually Happens: A2P submissions often come back as "Website Unreachable" if your domain bounces through extra redirects or Cloudflare blocks the automated review bot, and pre-checked SMS consent boxes get rejected every time.
How We Fix It: Temporarily turn off Cloudflare Bot Fight Mode while the review is pending, make sure the SMS checkbox starts completely unchecked when the page loads, and put the business name and a direct link to the Privacy Policy right next to the checkbox.
PLAYBOOK T11 · FAST VOICE AI SETUP
Making Voice AI Calls Feel Fast & Natural (With Retell or Vapi)
What Usually Happens: When a voice bot takes 1.5 seconds to answer, callers think the line went dead, start talking again, and then the bot talks right over them.
How We Set It Up: Put a quick 4-second greeting in HighLevel first ("Press 3 to book") to block spam robocalls, connect Retell or Vapi when a client needs sub-second responses, keep voice prompts in short everyday sentences, and send a 3-bullet call summary back into HighLevel notes when the call ends.
PLAYBOOK T10 · NATIVE WORKFLOWS & GHL MCP FIRST
Why Most Automations Belong Inside Native HighLevel Workflows or Our GHL MCP (Not n8n or Make)
What Usually Happens: Agencies often bolt on external n8n or Make scenarios for simple field formatting, math, or routing—which adds webhook delays, duplicate-contact race conditions, and an extra monthly bill when HighLevel can already do it natively.
What Works for Us: Use HighLevel's built-in Format Data, Math Operation, Goal Events, and Inbound/Outbound Webhooks inside a single native workflow so all history stays on the contact card—and use our ghl-tools MCP & Rust CLI when you need 30-second sub-account audits, snapshot diffs, or draft funnel updates.
PLAYBOOK T02 · WORKING WITH LOCAL CONTRACTORS
The Saturday 6 PM Call Check & Simple Starter Setup for Local Trades
What We've Seen: Plumbers, roofers, and HVAC owners almost always say no to $2,500/month AI pitches because they don't trust a bot with an emergency repair call and don't want complicated software.
What Works Better: Do a simple Saturday 6 PM test call to see if their phone goes to voicemail, show them how many weekend calls slip away to the next shop on Google, and start with a $297–$497/month missed-call text-back setup. Saving just one job pays for the whole year.
PLAYBOOK T09 · KEEPING CLIENT KEYS ORGANIZED
Keeping Client Sub-Account API Keys Organized & Safe
What Usually Happens: Keeping dozens of client API tokens in loose text files on a laptop makes it easy to mix up client accounts or accidentally paste the wrong key.
How We Handle It: Give each client sub-account its own separate token and folder, and always run a quick read-check first to make sure you're connected to the right client location before updating anything.
PLAYBOOK T03 · CHAT BOT SETUP
Keeping Chat Bots From Making Up Prices or Looping
What Usually Happens: When a chat bot on SMS or Instagram starts making up 50% discounts or repeating the same question over and over, the main prompt is usually trying to do too much at once.
How to Fix It: Take all prices and policies out of the main prompt and put them into the Knowledge Base Q&A instead, give the bot a clear rule to never guess unlisted prices ("Let me have our manager text you an exact quote"), and add a workflow rule that pauses the bot right away if someone texts "human" or "call me."
PLAYBOOK T04 · PHONE & VOICE AI
Using a Quick "Press 1" Screen to Block Robocalls
What Usually Happens: If a phone number connects straight to Voice AI, spam callers and Google listing bots will easily burn $100+ a month talking to your AI and fill your CRM with junk transcripts.
What Works for Us: Play a quick 4-second greeting first ("Thanks for calling, press 1 to speak with our team"). Real customers press 1 and connect right away, while robocalls can't press buttons and drop off after 5 seconds at zero AI cost.
PLAYBOOK T12 · EMAIL & DELIVERABILITY
Keeping Cold Email Separate From Your Main Business Domain
Why It Matters: Sending cold outreach from your main business domain is risky because once enough strangers hit "Report Spam," Google flags your whole domain—and real client invoices and calendar invites start going to junk mail.
How We Separate Them: Save your main domain strictly for real clients and billing, use 2–3 separate backup domains for cold outreach, warm new inboxes for two weeks, and keep volume around 30 plain-text emails a day per inbox.
PLAYBOOK T06 · AGENCY SNAPSHOTS
Updating Client Accounts Without Wiping Out Their Custom Work
What Usually Happens: Pushing a full snapshot update across active client sub-accounts can accidentally overwrite a client's custom workflows, phone numbers, calendar links, or funnel edits if two items share the same name.
What Works for Us: Whenever we customize a workflow for a specific client, we duplicate it and add [Custom] to the name so snapshot updates skip it. When pushing updates, uncheck Custom Values, Custom Fields, and Funnels, and only select the specific new workflow you want to add.
PLAYBOOK T07 & T08 · AI CODING TOOLS & SAFETY
Connecting Claude Code or Cursor to HighLevel Safely
Why It Matters: Giving an AI coding tool unrestricted access to your whole agency account is risky if it misunderstands a prompt and deletes real contacts or turns off a live workflow.
Our Setup: Create a separate token for just the single sub-account you're working on, keep permissions read-only by default for checking settings and contacts, preview any changes before they happen, and require human approval before anything gets deleted.
PLAYBOOK T01 · VOICE AI CALL QUALITY
Fixing Voice AI Interruptions & Lag on Cell Phone Calls
What Usually Happens: When a voice bot cuts people off mid-sentence or takes 3 seconds to reply, it's usually because the pause timer is too sensitive or the bot is trying to read long paragraphs with bullet points.
How to Fix It: Bump the pause timer up slightly (to around 400ms) so callers can take a breath without getting cut off, keep every spoken reply under 20–25 words so it loads fast, and write the voice prompt in plain sentences with commas instead of bullet points.
PLAYBOOK T05 · DOMAIN & EMAIL SETUP
Fixing the GoDaddy Double-Domain Mistake & Easing Into DMARC
What Usually Happens: Typing the full domain (link.agency.com) into GoDaddy or Namecheap's Host box turns it into link.agency.com.agency.com and breaks the SSL certificate, while starting straight on a strict DMARC "reject" setting can bounce normal emails.
How to Fix It: Only put the first word (like link) into the Host box, turn off Cloudflare's orange cloud so HighLevel can verify the certificate, and start DMARC on p=none for the first two weeks to make sure everything is passing cleanly before tightening it up.
PLAYBOOK T10 · BULK UPDATES & WEBHOOKS
Calming Down Bulk Webhook Spikes Between HighLevel & n8n
What Usually Happens: Bulk-tagging contacts or importing a CSV in HighLevel fires off hundreds of webhooks at the exact same second, which can overwhelm n8n or Make and create duplicate rows in your database.
How We Smooth It Out: Add a simple 1-minute Wait step in HighLevel right before the webhook to bundle rapid updates together, and use an "update if Contact ID exists" rule in your database or sheet so duplicate rows never show up.
PLAYBOOK T02 · LOCAL SERVICE OUTREACH
Why We Lead With a Missed-Call Check Instead of a $2,500 AI Pitch
What We've Seen: Local plumbers and HVAC owners don't care about AI buzzwords—they just care about not losing an $8,000 water heater or AC job to the shop down the street because their phone went to voicemail.
What Works Better: Do a quick Saturday 6 PM test call, show the owner what happens when a weekend emergency caller hits voicemail, and start with a simple $297–$497/month missed-call text-back setup that pays for the whole year on the very first saved job.
PLAYBOOK T11 · VOICE PRONUNCIATION & TRANSFERS
Fixing Trade Word Pronunciations & Warm Call Transfers
What Usually Happens: Nothing gives away an AI voice faster than mispronouncing a local street name or a trade word like "PEX" or "BTU," or dropping a customer into dead air during a blind transfer.
How We Set It Up: Instead of spelling words funny inside the prompt, add a simple pronunciation list inside ElevenLabs or Retell, use a warm transfer that gives the tech a 5-second heads-up before connecting the caller, and pull the caller back to take a message if the tech can't answer within 15 seconds.
PLAYBOOK T03 · SMS COMPLIANCE & OPT-OUT
Stopping Chat Bots from Replying After Customers Opt Out
What Usually Happens: When a lead texts STOP or CANCEL, an un-guarded AI replies with friendly conversational text ("Sorry to see you go! Is there anything else I can fix?"), which directly violates carrier 10DLC rules and risks A2P campaign suspension.
How We Fix It: Trigger HighLevel's native DND status on opt-out words, add an instant ai-conv-paused tag check before every chat prompt, and let the single standard carrier confirmation receipt serve as the only outgoing response.
PLAYBOOK T01 & T11 · VOICE AI & TELEPHONY
Navigating External Phone Menus with Automated Tone Dialing
What Usually Happens: When a voice receptionist transfers a caller to an outside supplier or doctor's office, the AI tries talking to the automated phone tree ("Press 1 for Dispatch") instead of sending touch-tones, resulting in dropped calls and dead air.
How We Fix It: Pre-program automated DTMF tones (e.g. +1-800-555-0199,,1,2) with 800ms pause commas for known phone trees, keep the caller on a reassuring hold during the handshake, and add a 12-second fallback to pull the caller back if the outside line doesn't connect.
PLAYBOOK T12 · OUTBOUND DELIVERABILITY & DOMAINS
Isolating Custom Tracking Domains for Safe Cold Email
What Usually Happens: Sending cold email with shared vendor tracking links or invisible open-rate tracking pixels triggers spam filters across Google and Microsoft, while pushing high volume on a fresh inbox burns domain reputation.
How We Fix It: Add a custom CNAME tracking subdomain (like track.domain.com) matching your sender identity, turn off open tracking pixels on the first cold step, cap secondary inboxes at 25–30 cold emails a day, and keep your primary business domain completely firewalled.
PLAYBOOK T01 & T13 · MULTI-LOCATION VOICE AI
Routing Multi-Office Patients with Area Filters & Partitioned Calendars
What Usually Happens: Cramming 10 clinic locations, 25 provider schedules, and differing weekend hours into one huge voice prompt confuses the AI, causing patients to get booked at the wrong office across town.
How We Fix It: Prompt the AI to ask "Which clinic is most convenient for you—Downtown or North?" before checking appointment slots, keep hours in separate location Knowledge Bases, connect Round Robin team calendars, and text an instant Google Map pin upon booking.
PLAYBOOK T02 & T13 · AGENCY ONBOARDING & OPERATIONS
The 45-Minute "Live Setup Sprint" vs. the 3-Week Form
What Usually Happens: Sending new clients a 40-question Google Form and asking for DNS passwords over email creates endless homework and delays, causing clients to stall for 3 weeks before seeing any results.
How We Fix It: Replace the long questionnaire with one 45-minute screen-share call right after payment, delegate DNS and call forwarding live on Zoom in under 5 minutes, and launch Phase 1 within 48 hours with Missed-Call Text-Back to score immediate weekend wins.
PLAYBOOK T10 · NATIVE WORKFLOW CONSOLIDATION
Stop Paying the $492/Month "Frankenstein Stack" Tax
What Usually Happens: Paying for separate Zapier, Make, Calendly, and ManyChat subscriptions on top of HighLevel adds $195/month in extra bills per location and creates four fragile webhook hops where a single expired token silently drops leads.
What Works for Us: Run date/name formatting, math calculations, inbound/outbound webhooks, round-robin Stripe booking, and Instagram/Facebook comment-to-DM natively inside HighLevel Workflows for $0 extra and one unified execution log.
PLAYBOOK T15 · REPUTATION MANAGEMENT & GOOGLE REVIEWS
Getting 5-Star Google Reviews Without Annoying Unhappy Customers
What Usually Happens: Waiting three days to email a generic review link gets ignored by happy homeowners, while blasting every contact blindly invites an unhappy customer to post a 1-star review on Google before you even know something went wrong.
What Works for Us: Trigger a quick personal check-in text 2 hours after an invoice is paid or a job is marked complete ("Did everything look good with the repair today?"). If they reply positively, send the direct Google review link and let HighLevel's Reviews AI reply to the posted review automatically; if they mention an issue, alert the owner privately first.
PLAYBOOK T16 · CALENDARS V2, CONFLICT SYNC & NO-SHOW RECOVERY
Cutting Calendar No-Shows From 38% to 4% & Stopping Double-Bookings
What Usually Happens: Connecting a technician's Google Calendar as one-way without enabling conflict checks causes HighLevel to book jobs right over personal appointments, and email-only or passive reminder texts still leave 1 in 3 slots empty.
What Works for Us: Set Google or Outlook as both the Linked Calendar and Conflict Calendar, send a two-way SMS asking the customer to "Reply C to keep your slot" 3 hours ahead, or add a $0-charged Stripe card hold with waitlist text auto-fill.
PLAYBOOK T17 · MOBILE FUNNELS & PARTIAL-FORM CAPTURE
3-Field Mobile Forms & Recovering Half-Finished Quote Requests
What Usually Happens: Asking for 8 or 9 fields on a mobile landing page causes most cell phone visitors to bounce before hitting submit, wasting paid ad clicks.
What Works for Us: Keep the mobile hero form to 3 fields max (First Name, Mobile Phone, and 1 service button), collect the street address on Step 2 or by text, and use a 10-minute workflow check with a Goal Event to text anyone who finished Step 1 but didn't finish booking.
PLAYBOOK T18 · PHOTO ESTIMATES, PROPOSALS & TEXT-TO-PAY
Turning 2 Driveway Photos Into Paid Apple Pay Deposits in 10 Minutes
What Usually Happens: Driving 45 minutes to quote a tire-kicker wastes half the afternoon, and plain PDF quotes sent by email sit unread while the homeowner gets three other bids.
What Works for Us: Text the homeowner to reply with 2 photos of the job area, send back a mobile estimate link with a 20% HighLevel Text2Pay deposit button so they can pay with 1-tap Apple Pay / Face ID, and auto-unlock the crew calendar the second the deposit clears.
PLAYBOOK T19 · SMART LISTS, PIPELINES & DATABASE REACTIVATION
Waking Up Dead Lead Spreadsheets with Smart List Drip Mode (50/Hr)
What Usually Happens: Blasting 2,000 old leads at the exact same minute with a promotional link gets your phone number flagged by carriers and overwhelms the front desk.
What Works for Us: Filter contacts in a Smart List (no activity in 90+ days, DND off, no open deal), enroll them in Drip Mode at 50 contacts per hour during business hours with a simple conversational question (zero links), and let a workflow move positive replies straight into the Reactivated pipeline stage.
PLAYBOOK T21 · AD MANAGER, META CAPI & OFFLINE CONVERSIONS
Training Meta & Google Ads on Real Booked Jobs (Not Raw Form Fills)
What Usually Happens: When your ad pixel only fires on form submission, Meta and Google optimize for cheap clickers who never pick up the phone instead of customers who actually book and pay.
What Works for Us: Capture fbclid and gclid automatically on HighLevel forms and Lead Ad syncs, then fire the native Facebook Conversion API (CAPI) and Google Offline Conversion workflow steps only when the pipeline card moves to Appointment Booked or Job Won.
