Skip to main content
An agent’s status pill is never one switch. It’s computed from two independent things (whether outreach is on, and whether any of its lead sources are currently running), combined in a fixed order that checks whether the agent is even set up before it looks at either one.
Where
Outreach→AI Agents
Your role needs
Read access to AI Agents read-campaigns. Admin, Member and Viewer have it by default.
To create or change
create-campaigns to add one, update-campaigns to change one, on top of the permission above.
If you cannot find this in your sidebar, your workspace may have a custom menu configuration. Contact support and we will check it for you.

​
The six, in the order the product checks them

That’s seven checks for six pills: Needs setup covers two different reasons, and both stop the product from even looking at whether outreach is switched on. An agent whose outreach you switched on yourself still shows Needs setup if it has no lead source, or if its tag matches none.

​
How it behaves

​
A lead source only counts as “running” while it’s actually working

Not every source status counts toward the Active / Sourcing paused / Outreach paused decision above. A source that has hit today’s sourcing cap still counts as running. It starts again on its own tomorrow. A source that ran out of credits, hit its total company limit, finished, or that you paused by hand does not count as running.
A source that has just been created sits waiting until its underlying searches are built, and that waiting state doesn’t count as running either. So a brand-new agent can read Paused or Sourcing paused before its first source starts. Nothing can start a source whose searches do not exist yet, not you and not the product, so if one stays waiting, give it a moment and then start it from its row on Sources.
An agent can have several lead sources, and the pill only ever reports the combined picture: Sourcing paused does not say whether one source is out of credits, another is paused, and a third hasn’t started. Open Sources on the agent to see each one on its own. Even there, a source at today’s cap carries the same green Active chip as one that is searching right now; hover the chip and its tooltip says which of the two it is.

​
The header switch and the list’s filter chips only ever look at outreach

The switch next to the pause menu, on the agent’s own page, reads only Active or Paused, and it is tracking outreach alone, not the combined pill above it. An agent can show the Sourcing paused pill while that switch still reads Active, because outreach really is on; it’s the sourcing half that stopped. The same split shows up on the list. Its Active and Paused filter chips group agents by outreach only: an agent showing the Sourcing paused pill sits under Active there, not under Paused, and an agent that shows Needs setup with outreach switched on sits under Active too. Only the Needs setup chip matches the pill exactly, because that’s the one check that doesn’t depend on either switch.

​
Three scopes to pause: everything, one half, or one source

The switch, and Pause everything in the pause menu next to it, do the same thing: stop outreach and every one of the agent’s running lead sources together, with none left behind. Only sourcing stops every running lead source and leaves outreach alone; Only outreach does the reverse. Each menu item disables itself once there is nothing left in its scope to pause: Pause everything only when both outreach and sourcing are already stopped, Only sourcing whenever nothing is running, Only outreach whenever outreach is already off. The pause button on an agent’s card in the list is the same both-halves action as the switch, with no way to narrow it: the three scopes only exist on the agent’s own page. A single lead source has its own pause and resume button too, on its row in Sources. That one touches nothing else: not the other sources, not outreach.
Pausing is gated separately from reading. The switch, the pause menu and the card’s pause button need a role that can update agents; a source’s own pause button needs a role that can update sources. A read-only role sees every pill and every source status but none of these controls: they are hidden, not greyed out.

​
Resuming only undoes a pause the product could have caused

Turning the switch back on does not blindly flip everything back on. Outreach restarts, and the product then tries to start any lead source that is either waiting to start for the first time or that you paused yourself: those two and nothing else. A source stopped because it ran out of credits, hit its total company limit, or finished needs that cause fixed first (buy more credits, raise the limit) before it runs again. On its own row that source cannot even be clicked: its button is disabled, with a tooltip reading “Fix the pause reason first — see the source status”.
So resuming a Paused agent does not always land on Active. If its only source is out of credits or at its limit, outreach comes back on and the pill settles on Sourcing paused; if every source has finished, it settles on Sourcing finished. Read each source’s own status on Sources rather than assuming the resume failed.

​
Limits

Lead sources: add, edit limits, pause

Every source status this page treats as one running-or-not switch, explained on its own.

Agent alerts and what to do about them

The banners across the top of an agent’s dashboard: what triggers each one, and the action that clears it.

No sending channel connected

Start here when outreach looks on but nothing is actually going out.

No leads matched yet

Start here when sourcing is running but the lead count isn’t moving.