Source: ai-research/ghl-2026-05-01/support-solutions-articles-155000005412-listing-conversation-ai-and-voice-ai-templates-on-the-marketplace.md, ai-research/ghl-listing-conversation-ai-voice-ai-templates-refresh-2026-07-03.md (2026-07-03 refresh — the live page was modified by HighLevel 2026-06-19, materially after the original snapshot)

Agency owners and admins can package a Conversation AI or Voice AI agent — together with its workflows, calendar, custom fields, custom values, and optional Knowledge Base — and sell it on the HighLevel Marketplace as a template. Buyers install the whole bundle in one click and the supporting assets land in their account ready to use. This article walks the three-step publish flow, what’s in the bundle, and the IP-protection caveats around snapshots.

Key Takeaways

  • The whole agent ships, not just the prompt: prompts, actions (workflow triggers, appointment creation, SMS, call transfers), and the underlying assets (workflows, calendars, custom fields/values) install automatically when a buyer purchases the template.
  • Knowledge Base is opt-in. During publish you choose Include or Exclude. If included, the KB is bundled and installs automatically with the agent.
  • Sell this Template/Agent on Marketplace is visible only to Agency Owners and Admins, not sub-account admins or users.
  • Three-step publish: (1) generate marketplace link from the agent page, (2) paste link in developer portal under Modules → ConversationAI or Voice AI, (3) fill basic info, app profile, pricing, support → submit.
  • Editable in the listing: use cases, agent description, available actions, suggested test questions for buyers. Non-editable (auto-fetched from the agent): supported channels (SMS, email, Instagram, calls).
  • Updated 2026-07-03: template updates now go through App Versioning, not a link swap. As of a HighLevel change (page modified 2026-06-19), AI Agent templates on a Live app version are no longer directly editable — see “Updating an existing template” below for the current flow. The old “click Copy Link for Marketplace and replace the link” process is superseded.
  • IP-protected snapshot caveat. Assets imported as part of an IP-protected snapshot cannot be included in agent templates. Restricted/IP-protected assets are blocked by HighLevel.

Three-step publish flow

In HighLevel, on the Conversation AI or Voice AI page:

  1. Select the agent.
  2. Click Sell this Template/Agent on Marketplace. (Only Agency Owners and Admins see this option.)
  3. Choose Knowledge Base treatment: Include (bundles the KB with the agent) or Exclude (publish without KB).
  4. The system redirects you to the Developer Portal with a special link carrying the agent’s package.

The exported package contains:

  • The agent’s prompts
  • Configured actions (trigger workflow, create appointment, SMS blast, call transfer)
  • Underlying assets: workflows, calendars, custom fields, custom values
  • Knowledge Base (if Include selected)

IP-protection check: before publishing, verify none of your bundled assets (workflows, calendars, custom fields) were imported from an IP-protected snapshot. HighLevel blocks IP-protected assets from inclusion in agent templates.

Step 2 — Complete Your App Details

In the Developer Portal at https://marketplace.gohighlevel.com/apps:

  1. Navigate to Modules → ConversationAI or Voice AI.
  2. Paste your link.
  3. Click Submit to fetch the package.
  4. Fill in editable fields:
    • Use cases (e.g., lead qualification, appointment booking)
    • Agent description
    • Available actions (workflows, appointments, SMS blasts, call transfers)
    • Suggested test questions — buyers can ask these against the agent in the Marketplace before purchasing
  5. Review non-editable fields (auto-fetched): Supported channels (SMS, email, Instagram, calls).

Step 3 — Finalize and Submit

  1. Fill in the standard app fields: Basic Info, App Profile, Pricing, Support.
  2. Submit for review.
  3. On approval, the listing goes live for all agency users and sub-accounts.

Pricing follows the standard Marketplace pricing models — free, subscription, one-time, freemium, with optional free trial. See Marketplace App Listing for pricing details.

What’s in the bundle

A buyer purchasing your agent template gets:

AssetDescription
Agent promptsThe core instructions/system message powering the AI
ActionsTriggers wired to workflows, appointment creation, SMS, call transfer
WorkflowsThe HighLevel workflows the actions invoke
CalendarCalendars the agent can book against
Custom fieldsStructured data fields the agent reads/writes
Custom valuesVariables the agent references in prompts/messages
Knowledge BaseOptional — bundled if Include selected during publish

The combined package is what installs automatically — buyers don’t manually wire up workflows or set up calendars; the template imports a working configuration.

Updating an existing template

Superseded 2026-07-03. AI Agent templates now follow the same Marketplace app-versioning workflow as the rest of an app — HighLevel’s own framing: “AI Agent templates on a Live app version are no longer directly editable.” The current flow:

  1. Go to Manage → Versions in the developer portal.
  2. Clone the Live version as a Draft.
  3. Make your Conversation AI or Voice AI template changes inside the Draft version.
  4. Publish the Draft using the appropriate version bump (see below).

This routes AI Agent template updates through the same controlled Draft → In Review → Live lifecycle as any other app change (see Developer Marketplace § App Versioning) — it replaces the older “Copy Link for Marketplace, swap the link, resubmit” flow this article previously described.

Major vs. Minor version bump for template changes:

ChangeVersion type
Agent name, description, use case, supported channels, actions, template configuration, template link changes, disabling/re-enabling an existing template linkMinor (default)
Adding a Conversation AI or Voice AI template to a Live app for the first timeMajor (new module capability)

Try It

  • Build a focused agent for one use case (lead qualification, appointment booking) — narrow templates outperform generic ones in the marketplace.
  • Decide on Knowledge Base inclusion early. Bundled KBs add value but increase the package size and complexity.
  • Audit every workflow, calendar, and custom field tied to your agent for IP-protected snapshot origins. If any came from an IP-protected snapshot, replace with non-restricted equivalents.
  • Curate 5-10 strong suggested test questions before submitting — these are the buyer’s first impression in the marketplace listing.
  • Use a clear use-case description (e.g., “Books dental appointments via SMS for general practice clinics” beats “AI agent for healthcare”).
  • Test the install end-to-end on a clean sub-account before going live: install the template, run a real conversation, confirm workflows fire and the calendar books correctly.
  • Set up a feedback loop with early buyers — agents need iteration based on real conversation data.

Open Questions

  • Whether bundled Knowledge Base content is editable by the buyer post-install, or locked to the template’s version.
  • Refund and revenue-share behavior for AI-template purchases (do they follow the standard 0%-commission Marketplace rules, or is there a different split for AI templates?).
  • IP-protected snapshot enforcement — what error a developer sees if they try to publish a template with restricted assets, and whether partial bundles are allowed. (researched 2026-07-02: still open — the general “Assets Protected Snapshots” mechanism (help.gohighlevel.com/…/155000002852) confirms restricted assets are marked “Restricted (Assets Protected)” and silently excluded when creating a snapshot from a protected sub-account, but no source documents the specific error text or partial-bundle behavior for the AI-agent-template publish flow specifically.) (researched 2026-07-03: still open — the AI-template listing article’s own FAQ and asset list were checked directly (page re-fetched; modified by HighLevel 2026-06-19) and confirm the same blanket rule verbatim (“Restricted/IP protected assets cannot be included in the AI agents”) but still stop short of the literal publish-time error string or explicit partial-bundle-vs-hard-block behavior. The now-versioned publish flow (Draft → In Review → Live, see “Updating an existing template” above) is a plausible place such a validation error would surface, but no source documents it at that step either. Likely requires triggering the flow directly in a live developer account to observe.)