Why is Query Records the Correct Answer?
In Agentforce, thePlanner Serviceis responsible for interpreting user requests and selecting the appropriateCopilot Actionto fulfill them. When a user issues a command like:
"Show me all the customers in New York",
the system must retrieve a list of customers filtered by location.
TheQuery Recordsaction is designed precisely for this purpose.
Key Features of Query Records in Agentforce:
Retrieves Data Based on Specific Field Values
This action fetches Salesforce records that match a set of criteria, such as customers located in New York.
Uses standard or custom object fields (e.g., BillingState = 'New York').
Works with Large Language Models (LLMs) and Copilot Actions
When a user asks for filtered data, Query Records is the default action assigned by the Planner Service.
Optimized for Structured Data Retrieval
Why Not the Other Options?
❌B. Fetch Records
This isnot a standard termin Einstein Copilot or Agentforce.
No defined Agentforce action exists under this name.
❌C. Select Records
Select Recordsis used to pick records from analready presentedlist, not to retrieve them initially.
If the user had already retrieved records and wanted to refine their selection, Select Records might be appropriate.
However, since the user's request is toretrieve records, Query Records is the correct action.
Agentforce Specialist References
This information is confirmed from theSalesforce AI Specialist MaterialandQuestions Document, where theQuery Recordsaction is explicitly defined as the appropriate standard action for retrieving filtered CRM records.
Submit