You are here:
Flex Credits Billable Usage Types for Slackbot
Usage of certain Slackbot features impacts Flex Credits consumption when Slack is connected to a Salesforce org that has Flex Credits. To monitor usage, access your org’s Digital Wallet.
Usage of certain Slackbot features impacts Flex Credit consumption when there is a supported connection to a Salesforce org that has Flex Credits. To monitor Flex Credits usage, access your org's Digital Wallet. Slackbot Consumption draws on Flex Credits only after your Slack plan's pre-allocated message allowance is exhausted. For more information on how Flex Credits usage is billed, refer to your contract or contact your account executive.
Review your org’s licenses and Digital Wallet to determine how your org is billed.
- Flex Credits billing is supported only for connections to production Salesforce orgs that have Flex Credits. Slack doesn't currently support drawdown from Sandbox orgs, since there's no sandbox equivalent for Slackbot today.
- For plan-level Slackbot inclusion details, see Slackbot limits and credit usage in Slack Help.
The number of Flex Credits consumed is based on the number of units of each usage type used, multiplied by the multiplier listed on the Flex Credits rate card for the usage type.
Messages and Actions
A single message to Slackbot doesn't always equal a single billable action. One message can trigger multiple actions depending on what it asks Slackbot to do.
For example, asking Slackbot "Can you find a message that I sent to Mr. Smith?" might run several underlying tool calls (a search plus a user lookup), but is billed as just 1 Standard Action, since all the calls serve one outcome and the lookup is accessory to the search.
A message can also span both action types. Asking Slackbot to "Find our latest updates on Project X and put them into a slide deck" runs Slack search calls (consolidated into 1 Standard Action) plus a Create Slides call (1 Advanced Action). This is billed as 1 Standard Action and 1 Advanced Action.
How Slackbot Actions Are Billed
Each time you send a message and Slackbot responds, that’s one turn. Slackbot bills actions according to these rules.
- Only user-visible actions are billed. Internal and system actions aren’t metered.
- Each unique tool is billed once per turn. Tool-call errors aren’t billed.
- Multiple create or update calls toward the same outcome in one turn count as a single action.
- Actions are grouped by outcome, not by implementation. A tool that's later split or refactored internally still bills the same way.
- All MCP tool calls count as one Standard Action, except Salesforce MCP tool calls, which are unmetered.
- Every turn bills at least one Standard Action, even with zero tool calls, or when only unmetered tools were invoked.
Flex Credits Usage Types for Slackbot
In Digital Wallet, Slackbot consumption for customers with Flex Credits is tracked on the Flex Credits consumption card in these usage types. To check multipliers for each usage type, see the Slackbot section within the Flex Credits Rate Card. Your contract determines the cost per credit.
| Digital Wallet Consumption Card | Usage Type | Usage Type Description | Notes |
|---|---|---|---|
| Flex Credits | Slackbot Standard Action | The default billable unit for a user-visible tool call. Covers most native Slack and Salesforce actions, including search, reads, and writes to records, canvases, lists, calendars, automations, and messages, along with MCP tool calls other than Salesforce MCP calls, which aren’t metered. | The meter runs once per unique tool per turn. Multiple calls toward the same outcome, such as three searches to find the right thread, are grouped and billed as one action. |
| Flex Credits | Slackbot Advanced Action | Premium, higher-value functionality, including deep research, report and dashboard creation, reading Salesforce files, and creating or editing slides, documents, or spreadsheets in third-party tools. | Advanced Actions bill in addition to any Standard Actions in the same turn. A single message can generate both. |
Some Slackbot actions are unmetered. Internal or system-level actions, such as tool discovery or MCP routing, are not billed, because they aren't user-visible outcomes. Accessory tool calls that only support billable actions, such as a user lookup that enables a search, also aren't charged separately.
