--- schema_version: "1" id: 1457737400dd767ec43a3b3f5daab3284c969da13a44c48ea3bc727c3f3d582d title: Agentforce Engagement Billing and Usage collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/sales_agents_lead_generation.md canonical_url: https://help.salesforce.com/s/articleView?id=sales.sales_agents_lead_generation.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: c29d4f755627e94e6fca7dda08b8bca7fb1a0dadb7d43d90656171109a33ea7c description: Agentforce Engagement use generative AI and Data Cloud to ingest, store, and process data. You’re billed in these categories for metered usage when you use Agentforce Engagement. products: - Sales Cloud - Agentforce release: "264" --- # Agentforce Engagement Billing and Usage Agentforce Engagement use generative AI and Data Cloud to ingest, store, and process data. You’re billed in these categories for metered usage when you use Agentforce Engagement. ### Required Editions

Available in: Lightning Experience in Enterprise, Performance, and Unlimited Editions with Sales and Einstein for Sales.

DiGitaL Wallet Card	Usage Type	Description
Flex Credits	Standard Action	Usage is determined by the number of standard actions called by the agent in a text conversation. Currently, every standard action called by the agent is metered as one standard action, irrespective of the number of tokens processed. Standard agent actions are actions that are available out-of-the-box. To check the list of Standard actions, see Standard Action Reference. Note Use of some standard agent actions require that a subscription is purchased for each user that accesses these actions, such as a subscription to Agentforce for Sales add-on or Agentforce for Service add-on. To determine which subscription is required for such standard actions, see Standard Action Reference at Standard Action Reference. While this requirement isn’t technically enforced yet, users who don’t have the required add-on license loses access to such actions for which they don’t have a license when the requirement is enforced.
Flex Credits	Custom Action	Usage is determined by the number of custom actions called by the agent in a text conversation. Currently, every custom action called by the agent is metered as one custom action, irrespective of the number of tokens processed.
Leads Worked	The Leads Worked usage type measures unique people instead of the number of conversations, messages, or agent responses that other billing types measure. A person is a lead, contact, individual, or an unidentified website visitor associated with a device ID.	The first qualifying agent response starts a rolling 30-day period for that person. More qualifying responses to the same person don't create another lead worked during that period. After the 30-day period ends, a new qualifying response to the same person counts as another lead worked. For more information about Leads Worked usage, see Leads Worked Billable Usage Types.

DiGitaL Wallet Card

Usage Type

Description

Flex Credits

Standard Action

Usage is determined by the number of standard actions called by the agent in a text conversation. Currently, every standard action called by the agent is metered as one standard action, irrespective of the number of tokens processed.

Standard agent actions are actions that are available out-of-the-box. To check the list of Standard actions, see Standard Action Reference.

Note Use of some standard agent actions require that a subscription is purchased for each user that accesses these actions, such as a subscription to Agentforce for Sales add-on or Agentforce for Service add-on. To determine which subscription is required for such standard actions, see Standard Action Reference at Standard Action Reference. While this requirement isn’t technically enforced yet, users who don’t have the required add-on license loses access to such actions for which they don’t have a license when the requirement is enforced.

Flex Credits

Custom Action

Usage is determined by the number of custom actions called by the agent in a text conversation. Currently, every custom action called by the agent is metered as one custom action, irrespective of the number of tokens processed.

Leads Worked

The Leads Worked usage type measures unique people instead of the number of conversations, messages, or agent responses that other billing types measure. A person is a lead, contact, individual, or an unidentified website visitor associated with a device ID.

The first qualifying agent response starts a rolling 30-day period for that person. More qualifying responses to the same person don't create another lead worked during that period. After the 30-day period ends, a new qualifying response to the same person counts as another lead worked.

For more information about Leads Worked usage, see Leads Worked Billable Usage Types.