Organize Voice AI Agents with Folders

TL;DR

Users can now create folders to organize Voice AI agents within HighLevel sub-accounts. This is a standard update; assess its relevance to your current Voice AI agent usage.

Who this affects

HighLevel has not confirmed who is affected by this update. If you use Voice AI agents, this update may be relevant for organization. If you do not use Voice AI agents, you can ignore this update.

What changed

Users can now create folders to group and manage Voice AI agents. Folders can organize up to 100 Voice AI agents within a HighLevel sub-account. Grouped or ungrouped agents can be assigned to folders. Users can navigate folder breadcrumbs. Folder contents can be edited. The agent library can be sorted alphabetically, by last updated date, or 'Folder First'. HighLevel has not confirmed any limits or plan gating for this feature. HighLevel has not confirmed the rollout status for this feature.

Where to find it

This feature is located when accessing the Voice AI agent list. HighLevel has not published a specific navigation path yet, but it will appear within the interface where Voice AI agents are managed.

How agencies will use this

An agency managing multiple client sub-accounts, each with its own set of Voice AI agents, can now apply a consistent organizational structure. For example, within a single sub-account, an agency might create a 'Lead Qualification' folder for agents handling initial prospect calls, a 'Customer Support' folder for agents assisting existing clients, and a 'Campaign Specific' folder for agents used in short-term marketing efforts. This allows for quicker identification and management of agents, especially when a sub-account approaches the 100-agent limit, avoiding a flat, unmanageable list. Agents can be moved between these folders as their purpose evolves or as new campaigns are launched. This organization can also be snapshotted, potentially simplifying setup for new sub-accounts.

Our take

This is a standard update focused on organization. It addresses a common need for managing growing numbers of assets within HighLevel. If your agency is heavily utilizing Voice AI agents across many sub-accounts, or if individual sub-accounts have a large number of agents, this feature will be useful. For agencies with minimal Voice AI agent usage, this is a minor update that likely doesn't require immediate action.