Skip to content
AI Employee

How to Clone and Share Managed Agents Using Snapshots

Learn how to add Managed Agents to GHL Customer Care Snapshots, load them into subaccounts, review conflicts, refresh configurations, and verify transferred agents.

7 min read1,493 words9 explained images
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. Key Benefits of Managed Agents in Snapshots
  2. What Transfers with a Managed Agent?
  3. Managed Agents in the Snapshot Asset Selector
  4. Conflict Checking When Loading Managed Agents
  5. Refreshing a Snapshot After Updating a Managed Agent
  6. How To Set Up Managed Agents in Snapshots
  7. Create a Snapshot That Includes a Managed Agent
  8. Load the Managed Agent into Another Subaccount
  9. Verify the Managed Agent in the Destination Subaccount
  10. Frequently Asked Questions
  11. Related Articles

Managed Agents (formerly Super Agents) can be packaged inside GHL Customer Care Account Snapshots and deployed across multiple subaccounts. This helps agencies reuse proven AI configurations, streamline client onboarding, and maintain consistent agent behavior without rebuilding each agent manually. Managed Agents are available under the Agent Studio asset category during Snapshot creation, refresh, and loading workflows.

TABLE OF CONTENTS

What Are Managed Agents in Snapshots?

Managed Agents in Snapshots are reusable Agent Studio assets that can be copied from a source subaccount into other GHL Customer Care subaccounts. A Snapshot packages the selected agent configuration so agencies can deploy the same AI-powered experience across clients, locations, or standardized account templates.

When a Managed Agent is included in a Snapshot, GHL Customer Care preserves its agent structure, configuration, connected Knowledge Bases, and version state. Supporting assets must also be selected when they are needed by the agent.

Key Benefits of Managed Agents in Snapshots

Packaging Managed Agents in Snapshots reduces repetitive setup work while helping agencies deliver consistent AI experiences across multiple accounts.

  • Faster client onboarding: Deploy prebuilt Managed Agents without recreating their configuration for every new client.

  • Consistent AI experiences: Reuse tested prompts, instructions, triggers, capabilities, and agent behavior across subaccounts.

  • Scalable deployment: Distribute one or more Managed Agents to multiple clients or business locations.

  • Flexible asset selection: Include individual Managed Agents independently or package them with other Snapshot assets.

  • Simplified updates: Refresh a Snapshot after changing an agent in the source subaccount, then distribute the updated asset to linked accounts.

  • Reusable agency solutions: Share configured agents through Snapshot links or include them in broader account templates.

What Transfers with a Managed Agent?

Understanding what a Snapshot preserves helps you prepare the source subaccount and identify any supporting assets that must be selected separately.

A Managed Agent Snapshot can preserve:

  • Agent flow structure

  • Node configurations

  • Prompts and instructions

  • Triggers

  • Skills and capabilities

  • Connected Knowledge Bases when the required Knowledge Base assets are selected

  • Agent version state, such as Draft, Staging, or Production

  • Selected supporting assets

Snapshots transfer selected configuration assets rather than live account activity or customer records. Integrations, third-party connections, credentials, and other account-specific resources may require additional setup in the destination subaccount.

Important: Review the agent’s dependencies before creating the Snapshot. If the Managed Agent relies on a Knowledge Base, workflow, Custom Value, or another selectable asset, include that supporting asset in the Snapshot.

Managed Agents in the Snapshot Asset Selector

The Snapshot asset selector organizes supported assets by product category. Managed Agents appear beneath Agent Studio, allowing you to expand the category and select only the agents needed for a particular deployment.

You can use this asset selector when:

  • Creating a new Snapshot

  • Refreshing an existing Snapshot

  • Loading a Snapshot into a subaccount

  • Pushing selected Snapshot assets to linked subaccounts

GHL Customer Care also supports selecting individual assets rather than loading every asset contained in the Snapshot.

Managed Agents in the Snapshot Asset Selector (image 1 of 9) What this shows GHL Customer Care also supports selecting individual assets rather than loading every asset contained in the Snapshot. What this shows Illustrates the "Managed Agents in the Snapshot Asset Selector" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Managed Agents in the Snapshot Asset Selector" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: GHL Customer Care also supports selecting individual assets rather than loading every asset contained in the Snapshot. This part of the guide covers 4 fields, listed below. Immediately after, the guide continues: Conflict checking helps identify selected Snapshot assets that may overlap with assets already present in the destination subaccount. Reviewing conflicts before loading reduces the risk of unintentionally replacing an existing…. Image 1 of 9 What this coversGHL Customer Care also supports selecting individual assets rather than loading every asset contained in the Snapshot.
Fields in this part of the guide Creating a new SnapshotRefreshing an existing SnapshotLoading a Snapshot into a subaccountPushing selected Snapshot assets to linked subaccounts
Buttons and menus referenced Agent Studio
Next stepConflict checking helps identify selected Snapshot assets that may overlap with assets already present in the destination subaccount. Reviewing conflicts before loading reduces the risk of unintentionally replacing an existing configuration.
All 4 steps in this procedure
  1. Creating a new Snapshot
  2. Refreshing an existing Snapshot
  3. Loading a Snapshot into a subaccount
  4. Pushing selected Snapshot assets to linked subaccounts

Conflict Checking When Loading Managed Agents

Conflict checking helps identify selected Snapshot assets that may overlap with assets already present in the destination subaccount. Reviewing conflicts before loading reduces the risk of unintentionally replacing an existing configuration.

The asset-selection screen provides two options:

  • Proceed to check conflicts: Continue to the conflict-review step before loading the selected Managed Agents.

  • Proceed without conflict check: Start the load without reviewing possible conflicts first.

Use conflict checking when loading a Snapshot into an active subaccount that may already contain a related agent or earlier version. General Snapshot loading supports reviewing conflicting assets and deciding which selected items should be applied. 

Conflict Checking When Loading Managed Agents (image 2 of 9) What this shows Use conflict checking when loading a Snapshot into an active subaccount that may already contain a related agent or earlier version. What this shows Illustrates the "Conflict Checking When Loading Managed Agents" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Conflict Checking When Loading Managed Agents" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: Use conflict checking when loading a Snapshot into an active subaccount that may already contain a related agent or earlier version. General Snapshot loading supports reviewing conflicting assets and deciding which selected items should be applied. Immediately after, the guide continues: After choosing to check conflicts, expand the destination subaccount to review the identified items and select the assets you want to apply. Image 2 of 9 What this coversUse conflict checking when loading a Snapshot into an active subaccount that may already contain a related agent or earlier version. General Snapshot loading supports reviewing conflicting assets and deciding which selected items should be applied. Next stepAfter choosing to check conflicts, expand the destination subaccount to review the identified items and select the assets you want to apply.
All 2 steps in this procedure
  1. Proceed to check conflicts: Continue to the conflict-review step before loading the selected Managed Agents.
  2. Proceed without conflict check: Start the load without reviewing possible conflicts first.

After choosing to check conflicts, expand the destination subaccount to review the identified items and select the assets you want to apply.

Conflict Checking When Loading Managed Agents (image 3 of 9) What this shows After choosing to check conflicts, expand the destination subaccount to review the identified items and select the assets you want to apply. What this shows Illustrates the "Conflict Checking When Loading Managed Agents" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Conflict Checking When Loading Managed Agents" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: After choosing to check conflicts, expand the destination subaccount to review the identified items and select the assets you want to apply. Immediately after, the guide continues: Snapshots do not update automatically when an agent changes in the source subaccount. Refreshing the Snapshot captures the latest selected configuration and creates an updated Snapshot version for future loads or pushes. Image 3 of 9 What to chooseAfter choosing to check conflicts, expand the destination subaccount to review the identified items and select the assets you want to apply. Next stepSnapshots do not update automatically when an agent changes in the source subaccount. Refreshing the Snapshot captures the latest selected configuration and creates an updated Snapshot version for future loads or pushes.
All 2 steps in this procedure
  1. Proceed to check conflicts: Continue to the conflict-review step before loading the selected Managed Agents.
  2. Proceed without conflict check: Start the load without reviewing possible conflicts first.

Refreshing a Snapshot After Updating a Managed Agent

Snapshots do not update automatically when an agent changes in the source subaccount. Refreshing the Snapshot captures the latest selected configuration and creates an updated Snapshot version for future loads or pushes.

To refresh a Managed Agent:

  1. Make the required changes to the agent in the original source subaccount.

  2. Return to Agency View > Account Snapshots.

  3. Locate the Snapshot and click its Refresh icon.

  4. Expand Agent Studio.

  5. Select the updated Managed Agent.

  6. Select any new or modified supporting assets.

  7. Click Refresh.

  8. Wait for GHL Customer Care to finish fetching the selected assets.

Refreshing a Snapshot After Updating a Managed Agent (image 4 of 9) What this shows Make the required changes to the agent in the original source subaccount. What this shows Illustrates the "Refreshing a Snapshot After Updating a Managed Agent" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Refreshing a Snapshot After Updating a Managed Agent" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: Make the required changes to the agent in the original source subaccount. Return to Agency View > Account Snapshots. Locate the Snapshot and click its Refresh icon. Expand Agent Studio. Select the updated Managed Agent. Select any new or modified supporting assets. Click Refresh. Wait for…. The navigation path used here is Agency View > Account Snapshots. Immediately after, the guide continues: After refreshing, use the applicable Snapshot loading or push-update workflow to distribute the selected changes. Updates pushed from an agency Snapshot are available to linked subaccounts within that agency; external recipients generally…. Path: Agency View > Account SnapshotsImage 4 of 9 What to chooseMake the required changes to the agent in the original source subaccount. Return to Agency View > Account Snapshots. Locate the Snapshot and click its Refresh icon. Expand Agent Studio. Select the updated Managed Agent. Select any new or modified supporting assets. Click Refresh. Wait for GHL Customer Care to finish fetching the selected assets.
Buttons and menus referenced Agency View > Account SnapshotsRefreshAgent Studio
Next stepAfter refreshing, use the applicable Snapshot loading or push-update workflow to distribute the selected changes. Updates pushed from an agency Snapshot are available to linked subaccounts within that agency; external recipients generally need an updated shared Snapshot.
All 8 steps in this procedure
  1. Make the required changes to the agent in the original source subaccount.
  2. Return to Agency View > Account Snapshots.
  3. Locate the Snapshot and click its Refresh icon.
  4. Expand Agent Studio.
  5. Select the updated Managed Agent.
  6. Select any new or modified supporting assets.
  7. Click Refresh.
  8. Wait for GHL Customer Care to finish fetching the selected assets.
Refreshing a Snapshot After Updating a Managed Agent (image 5 of 9) What this shows Make the required changes to the agent in the original source subaccount. What this shows Illustrates the "Refreshing a Snapshot After Updating a Managed Agent" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Refreshing a Snapshot After Updating a Managed Agent" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: Make the required changes to the agent in the original source subaccount. Return to Agency View > Account Snapshots. Locate the Snapshot and click its Refresh icon. Expand Agent Studio. Select the updated Managed Agent. Select any new or modified supporting assets. Click Refresh. Wait for…. The navigation path used here is Agency View > Account Snapshots. Immediately after, the guide continues: After refreshing, use the applicable Snapshot loading or push-update workflow to distribute the selected changes. Updates pushed from an agency Snapshot are available to linked subaccounts within that agency; external recipients generally…. Path: Agency View > Account SnapshotsImage 5 of 9 What to chooseMake the required changes to the agent in the original source subaccount. Return to Agency View > Account Snapshots. Locate the Snapshot and click its Refresh icon. Expand Agent Studio. Select the updated Managed Agent. Select any new or modified supporting assets. Click Refresh. Wait for GHL Customer Care to finish fetching the selected assets.
Buttons and menus referenced Agency View > Account SnapshotsRefreshAgent Studio
Next stepAfter refreshing, use the applicable Snapshot loading or push-update workflow to distribute the selected changes. Updates pushed from an agency Snapshot are available to linked subaccounts within that agency; external recipients generally need an updated shared Snapshot.
All 8 steps in this procedure
  1. Make the required changes to the agent in the original source subaccount.
  2. Return to Agency View > Account Snapshots.
  3. Locate the Snapshot and click its Refresh icon.
  4. Expand Agent Studio.
  5. Select the updated Managed Agent.
  6. Select any new or modified supporting assets.
  7. Click Refresh.
  8. Wait for GHL Customer Care to finish fetching the selected assets.

After refreshing, use the applicable Snapshot loading or push-update workflow to distribute the selected changes. Updates pushed from an agency Snapshot are available to linked subaccounts within that agency; external recipients generally need an updated shared Snapshot.

How To Set Up Managed Agents in Snapshots

Preparing the source agent and selecting its required assets helps ensure that the destination subaccount receives a complete, usable configuration. Review the agent before creating the Snapshot, then verify its settings after loading.

Create a Snapshot That Includes a Managed Agent

  1. Open the source subaccount and confirm that the Managed Agent contains the configuration you want to reuse.

  2. Switch to Agency View.

  3. Navigate to Account Snapshots.

  4. Click Create New Snapshot.

  5. Enter a descriptive Snapshot name.

  6. Select the source subaccount containing the Managed Agent.

  7. Continue to the asset-selection step.

  8. Expand Agent Studio.

  9. Select the Managed Agent or Managed Agents you want to include.

  10. Select any supporting assets required by the agents, such as applicable Knowledge Bases, workflows, or Custom Values.

  11. Review the selected assets.

  12. Click Create to save the Snapshot.

GHL Customer Care creates Snapshots from assets already configured in a source subaccount; the Snapshot itself is not built independently from scratch.

Create a Snapshot That Includes a Managed Agent (image 6 of 9) What this shows GHL Customer Care creates Snapshots from assets already configured in a source subaccount; the Snapshot itself is not built independently from scratch. What this shows Illustrates the "Create a Snapshot That Includes a Managed Agent" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Create a Snapshot That Includes a Managed Agent" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: GHL Customer Care creates Snapshots from assets already configured in a source subaccount; the Snapshot itself is not built independently from scratch. Immediately after, the guide continues: From Agency View, open Sub-Accounts. Locate the destination subaccount. Open its three-dot menu and select Manage Client. Open Actions and select Load Snapshot. Choose the Snapshot containing the Managed Agent. Select the destination…. Image 6 of 9 What this coversGHL Customer Care creates Snapshots from assets already configured in a source subaccount; the Snapshot itself is not built independently from scratch.
Buttons and menus referenced Agency ViewAccount SnapshotsCreate New SnapshotAgent StudioCreate
Next stepFrom Agency View, open Sub-Accounts. Locate the destination subaccount. Open its three-dot menu and select Manage Client. Open Actions and select Load Snapshot. Choose the Snapshot containing the Managed Agent. Select the destination subaccount when prompted. At the Assets step, expand Agent Studio. Select the Managed Agents you want to load. Choose one of the following: When using conflict checking, expand the destination subaccount and review the available selections. Click Proceed to start loading the selected assets. Wait for the loading process to finish.
All 12 steps in this procedure
  1. Open the source subaccount and confirm that the Managed Agent contains the configuration you want to reuse.
  2. Switch to Agency View.
  3. Navigate to Account Snapshots.
  4. Click Create New Snapshot.
  5. Enter a descriptive Snapshot name.
  6. Select the source subaccount containing the Managed Agent.
  7. Continue to the asset-selection step.
  8. Expand Agent Studio.
  9. Select the Managed Agent or Managed Agents you want to include.
  10. Select any supporting assets required by the agents, such as applicable Knowledge Bases, workflows, or Custom Values.
  11. Review the selected assets.
  12. Click Create to save the Snapshot.

Load the Managed Agent into Another Subaccount

  1. From Agency View, open Sub-Accounts.

  2. Locate the destination subaccount.

  3. Open its three-dot menu and select Manage Client.

  4. Open Actions and select Load Snapshot.

  5. Choose the Snapshot containing the Managed Agent.

  6. Select the destination subaccount when prompted.

  7. At the Assets step, expand Agent Studio.

  8. Select the Managed Agents you want to load.

  9. Choose one of the following:

    • Click Proceed to check conflicts to review possible conflicts.

    • Click Proceed without conflict check to continue directly.

  10. When using conflict checking, expand the destination subaccount and review the available selections.

  11. Click Proceed to start loading the selected assets.

  12. Wait for the loading process to finish.

Load the Managed Agent into Another Subaccount (image 7 of 9) What this shows From Agency View, open Sub-Accounts. What this shows Illustrates the "Load the Managed Agent into Another Subaccount" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Load the Managed Agent into Another Subaccount" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: From Agency View, open Sub-Accounts. Locate the destination subaccount. Open its three-dot menu and select Manage Client. Open Actions and select Load Snapshot. Choose the Snapshot containing the Managed Agent. Select the destination subaccount when prompted. At the Assets step, expand Agent…. Immediately after, the guide continues: Open the destination subaccount. Navigate to AI Agents > Agent Studio. Open the Managed Agents tab. Confirm that the transferred agent appears in the list. Open the agent and review its: Test the agent in the destination account. Publish…. Image 7 of 9 What to chooseFrom Agency View, open Sub-Accounts. Locate the destination subaccount. Open its three-dot menu and select Manage Client. Open Actions and select Load Snapshot. Choose the Snapshot containing the Managed Agent. Select the destination subaccount when prompted. At the Assets step, expand Agent Studio. Select the Managed Agents you want to load. Choose one of the following: When using conflict checking, expand the destination subaccount and review the available selections. Click Proceed to start loading the selected assets. Wait for the loading process to finish.
Buttons and menus referenced Agency ViewSub-AccountsManage ClientActionsLoad SnapshotAssetsAgent StudioProceed to check conflictsProceed without conflict checkProceed
Next stepOpen the destination subaccount. Navigate to AI Agents > Agent Studio. Open the Managed Agents tab. Confirm that the transferred agent appears in the list. Open the agent and review its: Test the agent in the destination account. Publish or activate it when it is ready for use.
All 12 steps in this procedure
  1. From Agency View, open Sub-Accounts.
  2. Locate the destination subaccount.
  3. Open its three-dot menu and select Manage Client.
  4. Open Actions and select Load Snapshot.
  5. Choose the Snapshot containing the Managed Agent.
  6. Select the destination subaccount when prompted.
  7. At the Assets step, expand Agent Studio.
  8. Select the Managed Agents you want to load.
  9. Choose one of the following:
  10. When using conflict checking, expand the destination subaccount and review the available selections.
  11. Click Proceed to start loading the selected assets.
  12. Wait for the loading process to finish.

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 and description

    • Triggers

    • Skills

    • Capabilities

    • Knowledge Base configuration

    • Instructions

    • Required integrations or account-specific connections

  6. Test the agent in the destination account.

  7. Publish or activate it when it is ready for use.

Some copied assets may require integrations, permissions, approvals, credentials, or destination-specific configuration before they can operate correctly.

Verify the Managed Agent in the Destination Subaccount (image 8 of 9) What this shows Some copied assets may require integrations, permissions, approvals, credentials, or destination-specific configuration before they can… What this shows Illustrates the "Verify the Managed Agent in the Destination Subaccount" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Verify the Managed Agent in the Destination Subaccount" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: Some copied assets may require integrations, permissions, approvals, credentials, or destination-specific configuration before they can operate correctly. The navigation path used here is AI Agents > Agent Studio. This part of the guide covers 7 fields, listed below. Immediately after, the guide continues: Q: Can I include more than one Managed Agent in a Snapshot? A: Yes. Expand the Agent Studio category and select the individual agents you want to package. Path: AI Agents > Agent StudioImage 8 of 9 What this coversSome copied assets may require integrations, permissions, approvals, credentials, or destination-specific configuration before they can operate correctly.
Fields in this part of the guide Name and descriptionTriggersSkillsCapabilitiesKnowledge Base configurationInstructionsRequired integrations or account-specific connections
Buttons and menus referenced AI Agents > Agent StudioManaged Agents
Next stepQ: Can I include more than one Managed Agent in a Snapshot? A: Yes. Expand the Agent Studio category and select the individual agents you want to package.
Example values
Name and description
Priya Raman

Illustrative values showing the expected format. They are not read from the screenshot.

All 7 steps in this procedure
  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:
  6. Test the agent in the destination account.
  7. Publish or activate it when it is ready for use.
Verify the Managed Agent in the Destination Subaccount (image 9 of 9) What this shows Some copied assets may require integrations, permissions, approvals, credentials, or destination-specific configuration before they can… What this shows Illustrates the "Verify the Managed Agent in the Destination Subaccount" section of "How to Clone and Share Managed Agents Using Snapshots". This screenshot appears in the "Verify the Managed Agent in the Destination Subaccount" section of "How to Clone and Share Managed Agents Using Snapshots". The text alongside this image reads: Some copied assets may require integrations, permissions, approvals, credentials, or destination-specific configuration before they can operate correctly. The navigation path used here is AI Agents > Agent Studio. This part of the guide covers 7 fields, listed below. Immediately after, the guide continues: Q: Can I include more than one Managed Agent in a Snapshot? A: Yes. Expand the Agent Studio category and select the individual agents you want to package. Path: AI Agents > Agent StudioImage 9 of 9 What this coversSome copied assets may require integrations, permissions, approvals, credentials, or destination-specific configuration before they can operate correctly.
Fields in this part of the guide Name and descriptionTriggersSkillsCapabilitiesKnowledge Base configurationInstructionsRequired integrations or account-specific connections
Buttons and menus referenced AI Agents > Agent StudioManaged Agents
Next stepQ: Can I include more than one Managed Agent in a Snapshot? A: Yes. Expand the Agent Studio category and select the individual agents you want to package.
Example values
Name and description
Priya Raman

Illustrative values showing the expected format. They are not read from the screenshot.

All 7 steps in this procedure
  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:
  6. Test the agent in the destination account.
  7. Publish or activate it when it is ready for use.

Frequently Asked Questions

Q: Can I include more than one Managed Agent in a Snapshot?
A: Yes. Expand the Agent Studio category and select the individual agents you want to package.

Q: Do I need to include every Snapshot asset when copying a Managed Agent?
A: No. Snapshot asset selection is granular. Select the Managed Agent and any supporting assets it needs rather than loading unrelated assets.

Q: Why is my transferred agent missing its Knowledge Base content?
A: Confirm that the required Knowledge Base was selected when the Snapshot was created or refreshed. Snapshots package the assets selected in the asset picker.

Q: Should I use conflict checking when loading a Managed Agent?
A: Conflict checking is recommended when the destination account may already contain a related agent or earlier version. It gives you an opportunity to review possible overlaps before the selected assets are applied.

Q: Does editing the source Managed Agent automatically update the Snapshot?
A: No. Refresh the Snapshot and select the modified agent to capture its latest configuration.

Q: Will a transferred Managed Agent run immediately?
A: Review and test the agent after loading. Account-specific integrations, permissions, credentials, or other connections may need to be configured in the destination subaccount before the agent can operate as intended. 

Q: Can I push an updated Managed Agent to multiple subaccounts?
A: Yes. After refreshing the Snapshot, use the push-update workflow to select linked subaccounts and the assets that should receive the update.

Q: Can Managed Agents be distributed through shared Snapshots?
A: Agent Studio agents can be packaged for distribution through Snapshot links, and the dedicated Agent Studio Snapshot workflow also supports broader sharing or Marketplace use. Review all dependencies before distributing the Snapshot.

Frequently asked questions

What Transfers with a Managed Agent?
Understanding what a Snapshot preserves helps you prepare the source subaccount and identify any supporting assets that must be selected separately. A Managed Agent Snapshot can preserve: Agent flow structure Node configurations Prompts and instructions Triggers Skills and capabilities Connected Knowledge Bases when the required Knowledge Base assets are selected Agent version state, such as Draft, Staging, or Production Selected supporting assets Snapshots transfer selected configuration assets rather than live account activity or customer records. Integrations, third-party connections, credentials, and other account-specific resources may require additional setup in the destination subaccount. Important: Review the agent’s dependencies before creating the Snapshot. If the Managed Agent relies on a Knowledge Base, workflow, Custom Value, or another selectable asset, include that…

Was this guide helpful?

Related guides

Overview of Flow Agents in Agent Studio5 min read · 6 imagesAgent Studio - Setting Up Triggers for Flow Agents5 min read · 4 imagesHow to Setup Flow Agents in Agent Studio6 min read · 9 imagesAgent Studio - Router Tool (AI & Conditional Router)8 min read · 14 images