Home/HighLevel/Features/AI Employee/HighLevel guide to cloning and sharing managed agents

AI

HighLevel guide to cloning and sharing managed agents

In short

Managed Agents can be packaged inside HighLevel Account Snapshots, allowing agencies to copy a configured AI agent from one subaccount to many others. The snapshot stores the agent’s flow, prompts, triggers, skills, connected Knowledge Bases and version state for consistent deployment.

AreaAI Employee · Agent Studio
Used forMarketing agency, Real estate brokerage, Health clinic network
Setup steps40 steps in 4 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Agency owners who manage multiple client accounts benefit by reusing proven agent configurations, cutting setup time.
  • Marketing teams that run similar campaigns across locations can ensure each subaccount uses the same AI prompts and triggers.
  • Support departments that rely on Knowledge Base linked agents can deploy identical assistants to new branches without rebuilding connections.

02Managed Agents in snapshots, explained

Managed Agents stored in Snapshots act as reusable assets. When a snapshot is created, HighLevel captures the agent’s structure, prompts, triggers, skills, connected Knowledge Bases and its version (Draft, Staging, Production). The snapshot can then be shared or loaded into other subaccounts.

The snapshot workflow is accessed from Agency View under Account Snapshots. In the asset selector, Managed Agents appear under the Agent Studio category. Loading, refreshing and conflict checking are performed through the same Snapshot interface, allowing agencies to move agents between accounts without leaving the platform.

03How businesses use Managed Agents in snapshots

  • Marketing agency. The agency creates a Snapshot of a lead capture Managed Agent, then loads that Snapshot into each client subaccount. After loading, the agency tests the agent and publishes it, delivering a uniform chat experience across all clients.
  • Real estate brokerage. The brokerage packages a property listing Managed Agent together with its required Knowledge Base in a Snapshot. Loading the Snapshot into new office subaccounts preserves the Knowledge Base link, allowing each office to use the same listing assistant.
  • Health clinic network. The network bundles an appointment scheduling Managed Agent and related custom values into a Snapshot. The Snapshot is loaded into each clinic location subaccount, where the agent is tested and activated for patient booking.

04How to set up and use Managed Agents in snapshots in HighLevel

Create a snapshot that includes a Managed Agent

  1. Open the source subaccount and verify the Managed Agent has the desired configuration.
  2. Review the agent’s dependencies and include any required Knowledge Bases, workflows, or Custom Values before creating the Snapshot.
  3. Switch to Agency View.
  4. Navigate to Account Snapshots.
  5. Click Create New Snapshot.
  6. Enter a descriptive name for the Snapshot.
  7. Select the source subaccount that holds the Managed Agent.
  8. Proceed to the asset selection step.
  9. Expand the Agent Studio category.
  10. Select the Managed Agent or Agents to include.
  11. Select any supporting assets such as Knowledge Bases, workflows, or Custom Values.
  12. Review the selected assets for completeness.
  13. Click Create to save the Snapshot.

Load the Managed Agent into another subaccount

  1. From Agency View, open Subaccounts.
  2. Locate the destination subaccount.
  3. Open its three dot menu and choose Manage Client.
  4. In the Actions menu, select Load Snapshot.
  5. Pick the Snapshot that contains the Managed Agent.
  6. Confirm the destination subaccount when prompted.
  7. At the Assets step, expand Agent Studio.
  8. Select the Managed Agents you want to load.
  9. Click Proceed to check conflicts to review overlaps, or click Proceed without conflict check to skip review.
  10. If checking conflicts, expand the destination subaccount and examine the listed items.
  11. Click Proceed to start loading and wait for the process to finish.

Refresh a Managed Agent snapshot after updating the source agent

  1. Make the required changes to the agent in the original source subaccount.
  2. Return to Agency View > Account Snapshots.
  3. Locate the existing Snapshot and click its Refresh icon.
  4. Expand the Agent Studio category.
  5. Select the updated Managed Agent.
  6. Select any new or modified supporting assets.
  7. Click Refresh.
  8. Wait for HighLevel to finish fetching the selected assets.

Verify the Managed Agent in the destination subaccount

  1. Open the destination subaccount.
  2. Navigate to AI Agents > Agent Studio.
  3. Open the Managed Agents tab.
  4. Confirm that the transferred agent appears in the list.
  5. Open the agent and review its name, description, triggers, skills, capabilities, Knowledge Base configuration, instructions, and required integrations.
  6. Test the agent in the destination account.
  7. If any required integrations, permissions, or credentials are missing, configure them in the destination subaccount.
  8. Publish or activate the agent when it is ready for use.

05What it looks like in HighLevel

06Things to know before you rely on it

  • Snapshots do not update automatically when the source Managed Agent changes; you must refresh the Snapshot to capture updates.
  • Integrations, third party connections, credentials and other account specific resources are not transferred and must be set up in the destination subaccount.
  • Conflict checking is optional but recommended when the destination account may already contain a similar agent or an earlier version.
  • Managed Agents appear under the Agent Studio category in the Snapshot asset selector.

07How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

When you have a set of AI Agents that work well for a specific service or industry, packaging them in a Snapshot can simplify deploying the same agents to new client accounts.

If your clients need highly customized integrations or each account has unique credentials, the feature may not deliver enough value. You’ll still have to redo the connection work after each load, which can reduce the efficiency gain.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about Managed Agents in snapshots.

Can I include more than one Managed Agent in a Snapshot?

Yes. Expand the Agent Studio category and select each individual agent you want to package.

Do I need to include every Snapshot asset when copying a Managed Agent?

No. You can select the Managed Agent and only the supporting assets it requires, rather than loading unrelated assets.

Why is my transferred agent missing its Knowledge Base content?

Make sure the required Knowledge Base was selected when the Snapshot was created or refreshed, because only selected assets are packaged.

Should I use conflict checking when loading a Managed Agent?

Conflict checking is recommended when the destination account may already contain a related agent or an earlier version, allowing you to review overlaps before applying assets.

Does editing the source Managed Agent automatically update the Snapshot?

No. After editing the source agent, you must refresh the Snapshot and select the modified agent to capture the latest configuration.

Will a transferred Managed Agent run immediately?

After loading, review and test the agent. Account specific integrations, permissions, credentials or other connections may need to be configured before the agent can operate as intended.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.