Loading
Prepare for Email to Become the Default Login ExperienceRead More
US/Canada Toll-Free Callers Experiencing Silence After Agentforce Voice GreetingRead More
About Digital Wallet
FAQ: Digital Wallet Credits and Entitlements

FAQ: Digital Wallet Credits and Entitlements

Explore common questions regarding how consumption data is calculated and represented in Digital Wallet.

Does Digital Wallet enforce limits or block services when I exceed my entitlement?

No. Digital Wallet helps you monitor and manage account utilization but it doesn’t:

  • Block or throttle any Salesforce service or feature.
  • Turn off functionality when your consumption reaches 100%.
  • Prevent users from accessing products or features.

Salesforce avoids disabling services to prevent negative business impacts and disruptions to you or your customers. However, you can pause Data 360 services upon receiving consumption alerts. For technical details on implementing this workaround via Flow, see this third-party blog article, Pause Data 360 Credit Consumption with Flow.

Can I see which specific Agentforce agents or actions are consuming Flex Credits?

Yes, you can see consumption for all agents, including your custom agents.

Digital Wallet provides Flex Credits usage breakdown through standard consumption tags. How to retrieve these insights:

  • Out-of-the-box dashboards — Use the Consumption Insights or Consumption Analytics dashboard for pre-built views by agent and action.
  • Custom reports — Query the TenantEnrichedUsageEvent DLO and build a report or visualization with the relevant fields.

If creating your own custom report, be sure to include a filter that indicates “Root Resource Type equals BotDefinition.” See the Consumption by Agent report in Access and View the Consumption Insights Dashboard for a list of filters included in the out-of-the-box report.

Standard Consumption Tag What It Shows Where to Find It
Agent (root resource) Which Agentforce agent triggered the usage Consumption Insights by Agent report, or Root Resource ID or API Name in TenantEnrichedUsageEvent data lake object (DLO)
Action (resource) Which specific action consumed credits (prompt, service reply, and so on) Consumption Insights by Action report, or Resource ID or API Name in TenantEnrichedUsageEvent DLO
Feature name Category of AI feature (AI Agents, prompt templates, service replies) Consumption Insights by Feature report

For more information:

Get Actionable Insights with Standard Consumption Tags

Track Consumption for Generative AI Prompts for Flex Credits

Consumption Analytics Consumption Explorer

I see small usage occurring, but my Credits Consumed total hasn't changed. Why?

Digital Wallet displays credits as whole numbers on the card homepage. Small usage amounts are tracked internally but aren’t reflected in the credits consumed total until they accumulate to greater than or equal to 1 credit. Even when the total shows 0, your usage is being recorded in the Salesforce system for billing purposes.

For more information:

Data Aggregation Types and Calculations in Digital Wallet

Why doesn’t “Units Consumed × Multiplier” equal Credits Consumed in the Consumption By Type table?

In Digital Wallet, we round Credits Consumed to the nearest whole number. How Digital Wallet calculates and rounds display values:

  • Credits Consumed is calculated precisely, then rounded to the nearest whole number.
  • Units Consumed is back-calculated as: Credits Consumed (rounded) ÷ Multiplier, then displayed with 2 decimal places.

The underlying billing data uses full precision. However, in Digital Wallet, both values are independently rounded, so the displayed math doesn’t always align with a manual calculation.

Displayed Units Consumed in Digital Wallet Actual Units Consumed Multiplier Actual Credits Consumed Displayed Credits Consumed in Digital Wallet
47.65 47.6467 2000 95,293.47 95,293

My prompt template is categorized differently than expected, such as Standard instead of Basic. Why?

The prompt tier classification that determines the Flex Credits multiplier is based on the LLM model used at execution time, not necessarily what you configured in setup.

Common causes of unexpected classification:

  • The model resolved at runtime differs from configuration (model fallback behavior)
  • Model tier assignments are updated periodically — a model that was "Basic" is now "Standard"
  • Some models have different billing tiers than their naming suggests

How to verify:

  • Check the current Generative AI Large Language Model Support help for the latest model-to-tier mapping.
  • Note the Prompt ID and execution dates.
  • Contact Salesforce Customer Support if the classification doesn't match the documented tier for your model.

For more information:

Digital Wallet-Enabled Consumption-Based Products

 
Loading
Salesforce Help | Article