How to run GoHighLevel with Claude: the operator's guide

Running GoHighLevel well is less about knowing every menu and more about having a repeatable order of operations. This guide summarises the sequence we use on every new account, and where an AI assistant like Claude genuinely saves hours rather than adding noise.

1. Set the foundation

Create the sub-account, verify a sending domain, warm the email identity, and complete A2P 10DLC registration before you build anything customer-facing. Deliverability and compliance are the two failure points that quietly ruin otherwise good automations, and both are slow to fix after launch. Get them done first, document the brand and campaign details, and keep the registration evidence in one place.

2. Connect Claude through MCP

GoHighLevel exposes an official Model Context Protocol endpoint. Once you add it as a connector in Claude Desktop, Claude Code, or Claude.ai and approve the sign-in, Claude can read contacts, opportunities, calendars, and conversations for the sub-account you authorised. Always run read-only test prompts first to confirm which location you are pointed at before you let it write anything.

3. Build the Launch Five

Five workflows carry most of the revenue in a small business account: speed-to-lead, missed-call text-back, appointment reminders, review requests, and database reactivation. Build those before any clever branching. Each one has a matching directive here, so you answer a short questionnaire about your offer, tone, and hours, and paste the finished instruction into Workflow AI.

4. Standardise and snapshot

Once a build works, snapshot it. Naming conventions, pipeline stages, custom fields, and calendar settings should be identical across accounts so a snapshot restore is predictable and your team can move between sub-accounts without relearning anything. From there, improvement is incremental: pick one metric, change one thing, and let the cheat sheets keep the rest stable.