How to hire a GoHighLevel VA that actually works.

Most agency owners hire a GoHighLevel VA backwards. They hand over admin access to a live account, drop a few Loom links in Slack, and hope. Two weeks later the pipelines are a mess, tags have multiplied, and the VA is waiting on replies instead of shipping.

I have trained 70+ students and VAs through daily live lessons, run a community where VAs access my resources and recorded breakdowns, and stayed alongside placed VAs for as long as they remain with the client. The hires that last share one thing: the setup around them. This is that setup, in the order I would do it.

1. Scope one outcome before you post the job

Bad job post: "Need GHL VA for everything." Good job post: "Own calendar management, inbox triage, and weekly pipeline cleanup for two subaccounts." A VA succeeds when one outcome defines done. Name the subaccounts, name the workflows they may touch, and name what stays with you: strategy, offers, client calls.

Also decide which kind of VA you need. A task VA works the inbox, calendar, and pipeline. A builder-level VA edits workflows, forms, and integrations. They are different hires with different risk, so write the post for one of them.

2. Give them a subaccount built for handoff

Never onboard a VA into the account you built by trial and error. Start from a clean snapshot, verify domains and calendars, and document the pipeline stages in plain language. My test: if a new hire cannot explain what each pipeline stage means after reading one page, the system is not ready for them.

3. Limit what they can touch

HighLevel gives each sub-account user one of two roles, Admin or User. Admin has full access. A User gets only the modules you switch on, and the same page lists granular permissions for areas like Workflows and Calendars. Two settings matter most for a new VA:

• Module access. Turn on Conversations, Contacts, and Calendars for a task VA. Leave Workflows off until they have earned it.
• Only Assigned Data. This limits a user to the leads and opportunities assigned to them. Use it if the VA should not see the whole book of contacts.

One catch from the same documentation: if you disable a module for a user, workflows that use it still run. Keep at least one person with full access who can manage those automations.

4. Replace Looms with a QA checklist

Looms explain; checklists enforce. Every repeating task gets steps and a definition of done: calendar checked for double-booking, tags match your naming glossary, opportunities moved the same day the contact replies. The VA self-checks before marking anything complete, and you spot-check instead of redoing the work.

Give a builder-level VA one more rule: nothing goes live until it has been tested with a test contact. Then use the workflow Execution Logs and Enrollment History to confirm the contact moved through each step and no action shows an error.

5. Keep a record of who changed what

Mistakes will happen. What hurts is not being able to tell which change caused one. HighLevel's Audit Logs record time-stamped actions with the user, module, and action. They keep entries for 60 days, so if something looks wrong, check it within that window and save what you need.

6. Keep them inside a training loop

The VAs who last keep learning after the hire. Daily or weekly troubleshooting beats a one-time onboarding call. In my community, placed VAs keep access to resources, recorded tips, and breakdowns, and I stay available while they hold the seat. Live huddles are optional; results are not.

7. Agree on output, review it weekly

Settle the rate and the hours before interviewing, not during. Then review one or two measures a week that match the job post: inbox cleared daily, pipelines current every Friday, new leads contacted within the window you set. A few measures reviewed weekly beat ten measures reviewed never.

Your first-week checklist

• One outcome written down, with subaccounts and off-limits items named.
• A clean subaccount with a one-page pipeline explainer.
• VA added as a User with only the modules they need, and Only Assigned Data decided.
• QA checklist for each repeating task.
• Someone with full access owns every live workflow.
• First weekly review on the calendar.