What Folders Do
A folder is a label applied to agents for organizational purposes. Selecting a folder in the sidebar filters the agent list to show only agents in that folder. Folders have no effect on call behavior, routing, or agent configuration.| Folder behavior | Detail |
|---|---|
| Filtering | Selecting a folder shows only agents assigned to it. “All Agents” shows everything. |
| Counts | Each folder shows the number of agents it contains. |
| No nesting | Folders are a single level. Sub-folders are not supported. |
| No routing effect | Moving an agent into or out of a folder does not change call behavior, phone number assignment, or published version. |
Creating a Folder
Click New Folder
Find the New Folder button in the folder sidebar or the action menu at the top of the Agents list. Click it.
Moving Agents into a Folder
Find the agent
In the Agents list, locate the agent you want to move. You can be in “All Agents” view or inside a different folder.
Renaming a Folder
Click the three-dot menu next to the folder name in the sidebar and select Rename. Enter the new name and confirm. The new name appears everywhere the folder is referenced.Deleting a Folder
Check the folder contents
Before deleting, open the folder and decide what to do with the agents inside. Deleting a folder does not delete the agents in it, but they will appear under “All Agents” without a folder assignment.
Good Folder Schemes
Pick a folder structure that matches how your team searches for agents.Use case
Examples: Qualification, Reminders, Collections, Support Intake, Surveys. Best for teams that search by what the agent does.
Customer or project
Useful for agencies or teams running separate customer deployments. One folder per client keeps things clean.
Environment
Examples: Production, QA, Archived. Separates agents ready for live traffic from agents still being tested.
Team ownership
Examples: Sales Ops, Support Ops, Growth. Helps teams find agents they own without searching across everyone else’s work.
Using Folders for Environment Separation
A common pattern is to use folders as an environment indicator alongside your naming convention. For example:- Folder:
Productioncontaining agents namedLead Qual - English,Appointment Reminder - Hindi - Folder:
QAcontaining agents namedLead Qual - English [TEST],Appointment Reminder - Hindi [TEST] - Folder:
Archivecontaining old experiments and deprecated versions
Environment folders are an organizational convention, not a technical enforcement layer. DialNexa does not prevent you from assigning a “QA” folder agent to a production phone number. Enforce environment discipline through team process and naming.
Folder Questions
Does moving an agent change its behavior?
Does moving an agent change its behavior?
No. Folder placement is purely organizational. The agent’s prompt, published version, phone number assignment, workflow connections, and all other configuration are unaffected by folder moves.
Can a folder replace workspace separation?
Can a folder replace workspace separation?
No. Workspaces are isolated environments with separate billing, phone numbers, and API keys. Folders organize agents within a single workspace. Use workspaces for true isolation and folders for agent organization inside one workspace.
Can the same agent be in multiple folders?
Can the same agent be in multiple folders?
No. Each agent belongs to one folder at a time. To “copy” an agent across folders, duplicate the agent and assign the duplicate to a different folder.
What happens to agents when a folder is deleted?
What happens to agents when a folder is deleted?
The agents remain in the workspace and are accessible under “All Agents”. They lose their folder assignment but retain all their configuration, version history, and routing.
Is there a limit on the number of folders?
Is there a limit on the number of folders?
There is no documented hard limit on folders, but very large numbers of folders can make navigation harder rather than easier. A flat structure of 5 to 15 folders covers most workspace needs.
Keep Folders Useful Over Time
Use names people would search for
The folder label should be obvious to someone new to the workspace. Avoid internal codes or abbreviations that only one person understands.
Move agents after creation
New agents land outside any folder by default. Move them into the right folder before handing off to someone else.
Archive by moving, not deleting
Move old experiments into an Archive folder before deleting them outright. This gives you a recovery window if you need the configuration later.
Related Reading
Agents Overview
Understand the full agent list and how agents are managed.
Agent Versions and Publishing
Manage draft and published versions of agents inside folders.
Agent Templates
Create new agents faster with pre-built templates.
Import Agents
Import agent configurations from other workspaces.