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.
How it behaves
The number is a share, not a quota
The (1) info icon in the header says it in one line: daily limits move on their own, new accounts warm up gradually, limits follow inbox health, and they are split evenly across every active agent using the same account. That is why the headline per-day figure (3), each budget in the caption and the “left” figure in the status line all carry a leading ≈. The count of what the agent has already sent today does not. That one is exact. What moves underneath differs by channel:- Email’s share is built from the current Smart Daily Limit of each attached mailbox, and an hourly pass revisits those limits, so an email figure can hold steady for a while and then step once that pass has run. Only mailboxes that are active and still managed by Smart Daily Limit count towards it: switch a mailbox to a manual daily limit and it stops contributing to this figure at all.
- LinkedIn and WhatsApp have no equivalent pass. Their ramp step is read from the account’s own age at the moment of the request, so the figure climbs by itself as soon as an account crosses into the next step, with no job to wait for.
One row per attached channel, and only channels this agent uses
A channel gets a row when this specific agent has at least one account of that kind attached to it: its own email accounts (or the whole workspace roster, if it is set to send from all of them), its own LinkedIn account, its own WhatsApp account. An account connected somewhere else in the workspace but not given to this agent does not add a row here. If the agent is set to send from every email account in the workspace, the card waits for that full roster to finish loading before it decides whether there is a channel at all, rather than flashing No sending channel yet at an agent that has plenty. This card only answers “how much room is left”. Whether a lead can be reached on a channel at all is a different question: WhatsApp only messages leads with a phone number on record, LinkedIn only leads with a LinkedIn URL, regardless of what this card shows.LinkedIn and WhatsApp split their row into separate budgets
Email only ever has one number. LinkedIn and WhatsApp meter more than one kind of action, so their headline is a total, and a row with more than one budget adds the caption (2) that breaks it apart:- LinkedIn’s three action types (invitations, messages and InMails) are independent budgets, and the row lists only the ones actually configured on the attached accounts; a type with nothing set up does not show a stray “0” for it. The big number is the sum of whichever types are configured, so a single configured type leaves the row with one budget and no caption.
- WhatsApp splits differently: the headline is the messages budget alone. New chats (the budget for opening a conversation with a lead who has not replied yet) is shown separately and is not part of the headline figure, because it caps something different. Replies inside an existing conversation flow from minute one; starting a brand-new one is what the ramp and the post-connect cooldown gate. An agent can show plenty of message budget and still open nothing new when its new-chat budget is at zero.
The status line says why, not just how much
Under the bar, each row prints one line naming the state that figure is in:
Warming and blocked look similar (both mean the channel is not sending), but they resolve
differently. Warming means at least one attached account is still ramping up and the figure climbs
on its own. Blocked means the channel has accounts but nothing to send today for a reason warm-up
will not fix, such as every attached account being paused or in an error state. WhatsApp reports its
new-chat gate as warming rather than blocked when a warming account is the cause.
The footnote adds the one thing the rows cannot
Below the list, at most one line of small print appears, and it is chosen, not accumulated: if any attached account on any channel is still warming up, the card says so and that the limits rise by themselves: nothing to do. Only when nothing is warming does it fall back to naming how many other active agents share the account, which is why a slice can look small when nothing is wrong. If neither applies, there is no footnote.No channel yet
With no account of any kind attached, the whole card collapses to one message: No sending channel yet, and the line under it (1) asks you to add at least one channel (a mailbox, a LinkedIn or a WhatsApp account), so the agent can start sending. Add a channel (2) opens this agent’s own Settings tab and scrolls to its Channels section, the same place the setup checklist’s channel row points to.Warming shows in place of a live figure
The line at (1) is what a row shows when the channel’s figure is zero specifically because an attached account has not finished ramping, as opposed to zero for any other reason, which reads as blocked instead. Expect it right after connecting a brand-new mailbox, LinkedIn account or WhatsApp account: sending starts small and climbs as the account ages, with nothing to configure in the meantime. For email that includes the opening period in which a new mailbox is held at zero.Limits
Related
Smart Daily Limit: how your sending limit is calculated
What actually sets each mailbox’s number, and how often it is revisited.
LinkedIn action limits, schedule and ramp-up
Invitations, messages and InMails on their own: how each is capped and ramped.
WhatsApp daily limits, new-chat budget and warm-up
The message budget and the new-chat budget explained on their own.
Daily limit is set to 0 during quarantine
Start here when a channel’s figure is smaller than you expected.