Considerations for Agentforce Banking Service Employee Assistance
Before creating an agent using the Banking Service Employee Assistance template, consider supported functionality, usage, limitations and allowances, limits, and other issues.
Required Editions
| Available in: Lightning Experience |
| Available in: Professional, Enterprise, and Unlimited Editions with the Agentforce for Financial Services add-on license or included in Agentforce 1 Financial Services Edition. Requires each user to have the Agentforce for Financial Services add-on to access the action. |
Language and Locale Support
Agentforce Banking Service Employee Assistance 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 Banking Service Employee Assistance supports these models. Agent actions can make calls to other predefined LLMs. Bringing your own model isn’t supported, but custom actions that execute prompt templates can use any Salesforce-managed model. See Large Language Model Support.
| Model |
|---|
| OpenAI GPT-4o |
Einstein Trust Layer Service Support
Agentforce Banking Service Employee Assistance supports the Trust Layer services supported by the Agentforce Employee Agent type.
Banking Service Employee Assistance Limitations
- Any modification to input and output contracts of an Integration Procedure (IP) isn't currently supported. However, users can modify the internal business logic and the IP's name using the Config IP override mechanism.
- When the agent shows a list of records for selection, the default output is an unformatted, comma-separated string of values that might appear clipped within the UI, requiring users to hover to see the full details. This string often includes unlabeled data and system IDs.
- The subagents and actions are currently context-specific to the Account object. They must be initiated from an Account record page to function correctly. Initiating them from other record pages, including Financial Accounts, isn't currently supported.
- When real-time transactions are retrieved using a Mulesoft API, users might observe inconsistent date and timezone formatting in the agent window when compared to the Case details record page.
- The agent currently displays a generic error message with a session ID for troubleshooting.
- User profiles with Agentforce Employee Agent access must have read permissions on the fields applicable to service processes.
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" is not processed as intended.
- The Query Records agent 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.
- To use currency related subagents, such as Financial Account Balances and Financial Account Transactions, enable multiple currencies.
- 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.
Did this article solve your issue?
Let us know so we can improve!
