Considerations for Collections and Recovery Assistance for Employees

Keep these considerations in mind when using the Collections and Recovery Assistance template to create a collections agent.

Required Editions

Available in: Lightning Experience
Available in: View product and edition availability.

Language and Locale Support

Agentforce Collections and Recovery Assistance template supports English in these locales.

Language Locale Code
English English (United States) en_US
English English (United Kingdom) en_GB

Large Language Model Support

Agentforce Collections and Recovery Assistance template supports this Large Language Model.

Model
OpenAI GPT-4o

Einstein Trust Layer Service Support

Agentforce Collections and Recovery Assistance template supports the Trust Layer services supported by Agentforce Employee Agent.

Usage Types Billed by Collections and Recovery Assistance

Collections and Recovery Assistance extends the Agentforce Employee Agent template. Agentforce Employee agents use generative AI in prompt executions and use Data 360 to ingest, store, and process data. Use of Agentforce Employee agents impacts the consumption of billing credits in these usage types.

Agentforce Employee agent usage is either metered or unmetered, depending on the permissions assigned to the interacting user. For more detailed information on how usage is billed, see Considerations for Agentforce Employee Agent.

Before deployment, work with your Salesforce account team to confirm license availability and plan credit usage.

Tip
Tip This feature has access to Digital Wallet, a free account management tool that offers near real-time consumption data for enabled products across your active contracts. Access Digital Wallet and start tracking your org's usage. To learn more, see About Digital Wallet.

Collections and Recovery Assistance Limitations

After an agent action is run, the resulting status message is shown twice.

Other Limitations

  • The agent can't process a request accurately if the request contains combined utterances from multiple subagents. For example, the request "Show the balance and recent transactions" may not be processed as intended.
  • The QueryRecords action can't run complex aggregation queries, such as "Get all financial accounts for Julia Green."
  • The agent input confirmation screen shows the input values entered by a user without their corresponding labels.
  • The agent actions currently support only the Dollar currency.
  • The Identify Record By Name agent action provides the most accurate results when used from a specific account record page, as this gives the agent the necessary context to find the correct record.