How to Set Up GoHighLevel for an Agency: A Practical Checklist

Prepare the process and its owners.

Start with a written client need. A lead arrives, someone owns the follow-up. The next action is visible. Record the entry event, required fields, decision rules and stopping rule. Avoid installing a large template. Do this before you know which parts the client actually needs.

Prepare approved firm details, the people who administer the account, allowed brand assets, domain control and the services already in use. Name who can approve DNS changes, linked accounts and billing. Keep credentials out of the shared brief. A link should be linked by its approved owner through the planned account flow.

This is a documentary setup plan, checked against public docs on 29 Oct 2026. No agency, client account, DNS record or workflow was configured for this article. The checks below are proposed work for an approved owner, not a report of a successful installation.

Confirm the plan and running budget.

Use the current HighLevel selector to check account caps and the exact features your client service requires. Do not infer that every tier includes every branding, resale or mobile-app option. Older Pro terminology in help copy and the current selector’s Founder label are not sufficient proof of identical limits.

The billing guide separates tool plan and wallet-funded usage. Name messages and extra products before enabling them. The AI pricing guide also splits coverage by product. Phone charges can remain split from Voice AI, and Agent Studio Flow Agents use pay-per-use billing across AI Employee plans.

Prepare a split client workspace.

Use a clearly named client workspace with only the required staff and test material. If you already have an approved snapshot, HighLevel documents an Agency Admin route through Account Snapshots to Create New Account to Add Sub-Account. Inspect the chosen snapshot and account facts before creating it. This route requires the snapshot to exist. It is not a recipe for copying a live client’s entire firm. Create a client account from a snapshot.

The snapshot overview excludes contacts, bookings, conversation history and third-party links. Reconnect the planned services and review the copied assets. The creation guide says copied funnels and sites remain drafts until the required domain link and publication. Treat a snapshot as setup reuse, not a data backup or auto move.

Inspect users, firm identity, time zone, pipeline names, custom fields and destinations. Replace sample copy and remove unused flows from the working plan before involving client records. Keep client facts separated and have the owner check the actual access granted to each role.

Choose the sending vendor before changing DNS.

Review the actual client account vendor in Agency Settings to Email Services to Location Settings. The provider-management guide splits LC Email and other vendors and explains domain assignment or fallback. When deciding how much CRM belongs in your automation stack, compare GoHighLevel vs ActiveCampaign. Do not assume every agency must buy Mailgun, or that changing a vendor leaves a current campaign unaffected.

For LC Email, the dedicated sending-domain guide describes Settings to Email Services to Dedicated Domain and IP to Add Domain. Use an unused sending subdomain and the DNS values generated for that account. Add or check the records through the documented route. Third-party SMTP uses a split setup. A sending domain and a dedicated IP are other purchases and setups.

Preserve the current DNS record set before a change. Have the domain owner check that the chosen subdomain does not host a current mailbox or other service. Do not delete the firm’s working mail records merely to make a check warning disappear. Stop and resolve a conflict with the responsible vendor. Check the chosen From and reply target without promising inbox placement.

Build a small draft workflow.

Define the lead route on paper first. In the workflow builder, add the planned trigger and its filters, then configure the actions. The official walkthrough splits triggers, actions and Draft/Publish states. Saving and publishing are split decisions. Keep the draft scoped to the exercise until the owner has approved the route.

Check the full path.

For an illustrative service lead, specify the form, planned contact fields, assigned owner and next follow-up task. If an email belongs in the path, prepare approved content and an allowed recipient. Check duplicate submissions, missing fields and a person who should be excluded. A visually linked canvas is not proof that every branch is correct.

Limit linked services.

If bookings, payments or messaging are required, document the account owner, vendor, access and sign-off check apart. Check current signup, consent and vendor needs before sending. Do not connect every service just. This is because it appears in a template. A webhook or payment step needs its own review of target and effects.

Review test behavior before running it.

The builder documents Test Workflow to select a contact to Run Test and warns that this test is imperfect, particularly with a reused contact. Do not treat that button as a guarantee of a harmless sandbox. Inspect each action and use only records, inboxes and linked destinations you are approved to exercise.

Separate evidence from assumptions. A test result does not certify all future contacts or email clients. Any later live validation needs a deliberately limited audience, monitoring and an approved stop procedure. This guide does not ask you to enable a live campaign simply to finish the checklist.

Hand over the running process.

Give the client a concise record of the active services, account owners, billing tasks, key daily actions and support route. Have the planned owner explain how a lead is handled and what they do. This applies when a step fails. Keep the previous process open during a staged switch.

Before enabling the real flow, resolve every open sign-off issue and obtain the appropriate approval. Review logs and costs after the first approved traffic. For product scope, see the HighLevel review. For re-bill and stop-order planning, use the trial test checklist. If the required process does not justify this setup, check alternatives by the job you need to replace.