You are here:
Considerations and Limitations for Agentforce for Pharmacy Benefits Reverification
To use Agentforce for Pharmacy Benefits Reverification, consider supported functionality, usage, limitations and allowances, limits, and other issues.
Required Editions
| Available in: Enterprise, and Unlimited Editions with Health Cloud or Life Sciences Cloud licenses and Agentforce for Life Sciences Cloud or Agentforce for Health Cloud, Flex Credits Metering, Agentforce Employee Agent, Genie Data platform, Einstein GPT Platform, Einstein GPT Copilot, and Einstein GPT Prompt Builder add-on licenses |
Feature Language and Locale Support
Agentforce for Life Sciences supports English in this locale.
| LOCALE | CODE |
|---|---|
| English (United States) | en_US |
Feature Large Language Model Support
Agentforce for Pharmacy Benefits Reverification supports the models supported on the Salesforce generative AI platform, as described in Large Language Model Support.
Einstein Trust Layer Service Support
Agentforce for Pharmacy Benefits Reverification supports the Trust Layer services provided on the Salesforce generative AI platform, as described in Einstein Trust Layer. Ask your system administrator about which Einstein Trust Layer services are enabled in your org and available for Agentforce for Pharmacy Benefits Reverification.
For Life Sciences features that use AI agents, see Trust and Agentforce.
Billing Considerations for Agentforce for Pharmacy Benefits Reverification
Use of the Draft or Revise Email and Summarize Patient Response for Benefits Reverification actions impacts credit consumption. These actions rely on Einstein Requests, and invoke generative AI through Agentforce to draft emails and to summarize patient responses.
| DIGITAL WALLET CARD | USAGE TYPE | DESCRIPTION | NOTES |
|---|---|---|---|
| Einstein Requests | Standard Einstein Request | Usage is calculated based on the number of calls to the LLM gateway if the gateway uses a Salesforce LLM. | This usage type isn’t billed when it's associated with a generative AI action that qualifies as unmetered human context usage. For more information, see Generative AI Usage and Billing. |
| Flex Credits | Standard Action | Usage is determined by the number of standard agent actions. Each standard agent action includes the processing of up to 10,000 tokens. Tokens are units of data processed by AI models. Actions exceeding this limit are counted as a separate standard action each time the 10,000 token limit is exceeded. For example, processing 20,001 tokens is 3 standard actions. Actions involving lengthy prompts sent to the LLM can be counted as multiple actions where the 10,000 tokens per action limit is exceeded. 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
has been purchased for each user that accesses these actions, such as a subscription to
Einstein for Sales Add-on or Einstein 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 is not technically enforced yet, users who don’t have the required add-on
license will lose access to such actions for which they don’t have a license when the
requirement is enforced. |
NA |
For more information on how usage is billed, refer to your contract or contact your account executive.
