Considerations for Setup with Agentforce (Beta)

General

• To use Setup with Agentforce, you must delete any agents created with the Agent for Setup tile or Enhanced Agent For Setup (Pilot) tile.
• Only objects that are available in Object Manager and searchable can be referenced in conversations and retrieved in responses. To make a custom object searchable, admins must enable the Allow Search attribute in Object Manager when creating or editing a custom object. Any custom objects created via Agentforce are searchable by default.
• Components generated in the canvas, such as list views, record pages, and metadata previews, don’t automatically update to reflect changes in other tabs. For example, you have a list view of users that shows each user’s name and email address. If you open one of the user records in another tab and update the email address, the list view still shows the original email address. To refresh your list view with the updated information, click to refresh.
• For more accurate results, use specific and deterministic language in your requests. For example, instead of “Show details of John,” use “Show user details of John Smith” or “Show phone number field of user John Smith.”
• Changes you make via the Setup agent are tracked in the Setup Audit Trail.

Navigation

• Each conversation tab has a unique chat session ID embedded in the browser URL. If you click between conversation tabs, you can see the chat IDs change in the browser URL. When a conversation with the agent is in progress, right-clicking the browser tab and selecting Duplicate to copy the conversation session into a new browser tab links both tabs to the same conversation chat ID. This means that the second browser tab is aware of questions or prompts from the original active conversation tab, and vice versa. However, the message history isn’t shared between the browser tabs, so updates made in one tab don’t appear in the other. Copying a conversation browser tab link and pasting it into a new browser tab doesn't maintain the connection between the conversation sessions.
• When working in Setup with agent tabs open, if you open Lightning Experience via the App Launcher and then navigate back to Setup, it opens in the default state with only the Home and Object Manager tabs present. Previous Setup agent chat sessions and tabs are lost. To avoid this, open Lightning Experience in a new browser tab and keep Setup open in the original tab.

Records

• To add fields to a displayed record, request the additional field information in the chat. The record then updates to include them.
• If a record contains many fields, scroll within the form to view all the field information without leaving the page.
• When a request matches multiple records, the agent displays a list of possible matches. The specific record details or form appear only after you select and confirm a record.

List Views

Setup with Agentforce uses list views to show records for users, flows, and other Setup-related objects. For example, if you ask to see users that have a specific permission assigned, then Agentforce provides those users in a list view with columns that include the relevant record fields.

List views in Agentforce-enabled Setup have some differences from list views in other areas of Salesforce. Keep these considerations and limitations in mind.

• A list view loads 12 records per page. The maximum total number of records a list view can retrieve varies based on the associated object.
• A list view can contain up to 15 columns.
• To refine or filter a generated list view in the conversation, enter a prompt with your requirements.
• List views don’t support actions and views like sort by multiple columns, charts, and alternative displays.
• You can navigate directly to a user record from a list view. To navigate to a specific record for any other supported object, enter a prompt with your request.
• Not all objects support search within a list view.
• Inline edit isn’t supported.

Language and Locale Support

Setup with Agentforce supports these languages and locales.

Note If you talk with the agent in a language that doesn't match the language on your user profile, the language the agent uses in responses can be inconsistent.

Large Language Model Support

Setup with Agentforce supports only the Salesforce Default model option. Choosing or switching to a different Agentforce model prevents enablement or causes the feature to be disabled.

Einstein Trust Layer Service Support

Setup with Agentforce supports the Trust Layer services provided on the Salesforce generative AI platform, as described in Einstein Trust Layer.

Usage Types Consumed by Setup with Agentforce

Setup with Agentforce uses generative AI and Data 360 to ingest, store, and process data. Setup with Agentforce doesn’t consume Agentforce credits but does consumes Data 360 credits.

You’re billed in these Data 360 categories when you use Setup with Agentforce. Work with your Salesforce account team to confirm license availability and plan credit usage.