The agent list and access
The agent list
The Agents section fits the window: the header with New agent, the toolbar and the table take the whole height, the rows scroll inside the table, and the column headers and pagination stay in place. On horizontal scroll the agent name stays pinned on the left and the row menu ⋯ on the right. The table columns:- Name — a link into the builder. An agent on a realtime model carries a Realtime badge.
- Folder — shown only when the list is not grouped by folder.
- Visible to members — Visible or Hidden (see Who sees the agent).
- Status — Published, Unpublished changes, No publications or Archived; the icon tells them apart by shape, not only by colour. A published agent, and one with unpublished changes, also shows the number of its live version, e.g.
v3. - Last modified — when the draft was last edited and by whom.
Search, filters and view
The toolbar above the table:- Search by name… — narrows the list as you type.
- Modified at — a date or a range in the calendar, or a preset: 24h, 7d, 30d.
- Filters — status (several values at once) and visibility. The status filter uses the same status as the column: an agent with unpublished changes counts as Unpublished changes, not as Published. With no status selected, the list shows every agent except archived ones.
- Folder — the folder filter, on a narrow screen only; on a wide one the folders are in the panel on the left (see Folders).
- View — Group by folder (the default), visibility, status or None, and Rows per page: 10, 25 (the default), 50 or 100.
- No agents yet — the organization has no agents; New agent creates the first one.
- This folder has no agents yet — the selected folder is empty; New agent creates the agent right in it.
- No agents match — nothing fits the search and filters; Clear all brings the list back.
- All agents are archived — Show archived switches the status filter to the archive.
Row actions
The ⋯ menu of a row:- Open — open the agent in the builder.
- Rename and Duplicate — the copy’s name is prefilled with the first free
<name>-copy,<name>-copy-2and so on. The copy takes the draft and the canvas layout without the publication history and lands in the same folder. - Move to — a folder, No folder, or New folder, which creates the folder and moves the agent into it.
- Visibility — Visible or Hidden for members.
- Share demo link… — the demo link dialog: each link shows its term and how many calls it has used, and contract findings on the agent’s published version are shown right in the dialog.
- Archive and Delete — both after a confirmation. An archived agent keeps its versions and history but stops taking calls, and it loses its telephony bindings — the notification lists the ones removed. Deletion erases the publication history; session history is kept.
Renaming an agent carries its settings with it. The agent’s webhook endpoints, its component and observer bindings, its phrase fixups and its campaigns in every state all follow the new name in the same operation.


Folders
Folders are one level deep, and an agent sits in at most one of them; folders are visible only inside their own organization. They live in the Folders panel to the left of the table:- one click on All agents, a folder, or No folder filters the table;
- every folder is listed, empty ones included, with a counter of its agents;
- with more than 10 folders, Search folders appears at the top of the panel;
- a folder’s ⋯ holds Rename folder and Delete folder;
- New folder creates one.
A folder is workspace arrangement, not a property of the agent. Moving an agent does not create a flow version and does not change edit attribution. Deleting a folder moves its agents to No folder and deletes none of them. A link to a deleted folder opens all agents without an error.
Selecting several agents
A checkbox in each row, Select all on this page in the table header and a checkbox on each group header pick agents for a bulk action. A floating bar Selected: N offers Move, Archive and Delete (the last two after a confirmation); archived agents in a selection can only be deleted. The result comes in a single notification: how many agents were changed and how many were not, with the reason — for example, an agent with active campaigns.Who sees the agent
An organization accumulates drafts, old copies and test agents, and a member choosing an agent for a campaign could not tell a working one from a rough sketch — the list offered all of them. Visible to members is the explicit answer to that: the column in the agent list shows Visible or Hidden, the switch is under Visibility in the row menu ⋯ — and the list can be filtered and grouped by it. In the builder the same setting is the Hide from members switch in the agent settings, Additional → Access; while the agent is hidden, the toolbar shows a Hidden from members pill. The setting applies immediately, without publishing, and does not touch the draft. Hidden means hidden from the choice, not switched off:- a hidden agent keeps making and taking calls, and stays available through the Web API — campaigns already running on it are not interrupted;
- members do not see it in the campaign wizard or the campaign dialog — the option is absent rather than greyed out;
- administrators and developers see every agent, with a
· Hidden from memberssuffix on the option; - the agent filters in History and Incidents list hidden agents too. Finding the old calls of an agent you have withdrawn is not the same act as choosing one for a new campaign.
agent_hidden next to the familiar “agent not published”, and choosing that agent for a new campaign is refused by the server, not just left out of the list.
A new agent becomes selectable at its first publication. Members are only offered published agents, so an unpublished draft is invisible to them anyway — and the moment you publish it, it appears in their list. That is why an agent still being built is hidden before the first publication rather than after. A duplicate inherits the setting of the agent it was copied from, so a copy of a hidden test agent does not surface on its own; renaming keeps it.


