Max
A Bot bills to you, like any session you start: your included quota first, then your on-demand credits. There is no separate usage limit for a Bot on Max.Teams
A Bot bills to its creator first: it uses the creator’s included quota, then the team’s on-demand credits. A creator on a flex seat has no included quota, so all of the Bot’s usage is on-demand. The Bot’s creator and admins can set an On-demand cap, in dollars, on the Usage limits page of the Bot’s settings. It caps what the Bot adds to the team’s on-demand usage, not included quota. At the cap, the Bot runs only while its creator has included quota left. An admin can give the Bot a separate usage limit. The Bot then stops using its creator’s included quota: all of its usage is on-demand, and it stops at its cap.Enterprise
A Bot bills to its creator: its usage counts toward the creator’s own usage limit. You can cap the Bot with an ACU limit or a spending limit in dollars, depending on your contract, on the Usage limits page of the Bot’s settings. The creator can set it up to their own limit, and so can admins with the Manage ACU limits permission. At the limit, the Bot stops until the limit resets or someone raises it. Your enterprise can make limits read-only or hide their amounts. A hidden limit still applies.A Bot’s limit stops the Bot only when budgets and user limits are enabled for your enterprise. To enable them, reach out to your account team.

