Agents
Levels and leads
The three levels an agent can have, the switch that lets it read leads, and how to stop an agent at once.
When you connect an agent you choose what it may do. There are three levels and one switch.
The three levels
Section titled “The three levels”Each level includes the one before it.
| Level | The agent may | Same as the role |
|---|---|---|
| Read | See flows, queues, meeting types and settings. Change nothing. | Basic |
| Build | Also write draft flows, queues and meeting types, and test a draft. | Editor |
| Publish | Also publish, pause and delete flows, and change what a live visitor gets: forms, sites, working hours and settings. | Admin |
“What a live visitor gets” covers publishing, pausing and deleting a flow, which flow a form runs, the sites, the working hours and the settings. Sending a rep their calendar link and starting a HubSpot sync also need Publish, as they need an admin in the app.
A level maps onto a role the app already has. So a rule that holds for a person holds for an agent, with no second set of rules.
Which tools need which level
Section titled “Which tools need which level”| Level | Examples |
|---|---|
| Read | get_started, list_flows, get_flow, list_node_types, list_queues, list_meeting_types, get_settings |
| Build | create_flow, save_flow_draft, dry_run_flow, restore_flow_version, save_queue, save_meeting_type |
| Publish | publish_flow, pause_flow, delete_flow, set_form_flow, add_site, set_working_hours, update_settings, send_calendar_link |
All tools gives the level for every tool.
When a tool is refused, its answer names the level it needs and says what to do next.
Never more than your own role
Section titled “Never more than your own role”You can give an agent no more than your own role allows:
| Your role | The highest level you can give |
|---|---|
| Admin | Publish |
| Editor | Build |
| Basic | Read |
The agent acts with the lower of two things: the level you gave, and your role today. If an admin gives Publish and is later made an editor, the agent drops to Build on its next call.
The leads switch
Section titled “The leads switch”Reading leads is a separate switch. It is off by default, at every level.
Leads are kept apart for two reasons:
- A lead holds personal data: a name, an email address, what the person wrote.
- A lead’s text was typed by a stranger. An agent that reads it must treat it as data, never as an instruction.
With the switch on, the agent can use list_leads and get_lead, and so can say why a lead went where it did. With it off, those tools are refused.
Turn it on only for the work that needs it.
Stop an agent
Section titled “Stop an agent”Open Agents in the app and press Disconnect by the agent. It stops at once: the agent’s next call is refused, and it cannot renew its sign-in.
Signalbox checks every call an agent makes as it arrives. An agent is also stopped at its next call when:
- the person who connected it leaves the workspace
- that person’s account is deactivated
- the workspace is locked
An admin sees every agent connected to the workspace and can disconnect any of them. Other people see and disconnect their own.
What is recorded
Section titled “What is recorded”Connecting an agent and disconnecting one are both written to the workspace’s audit.
So is every change an agent makes: a flow made or saved, a flow published, a queue changed, a setting changed. The entry names you and the agent, for example “Rosa Admin (via Claude)”. The Flows list shows the same name against a draft the agent saved last.
An admin reads the audit under Settings. An agent at Publish can read it with list_audit.
API keys
Section titled “API keys”An agent that signs in by API key gets its level and its leads switch from the key. See Authentication.