Why is Query Records the Correct Answer?

In Agentforce, the Planner Service is responsible for interpreting user requests and selecting the appropriate Copilot Action to 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.

The Query Records action 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

Ensures AI retrieves relevant CRM records quickly and accurately.

Why Not the Other Options?

B. Fetch Records

This is not a standard term in Einstein Copilot or Agentforce.

No defined Agentforce action exists under this name.

C. Select Records

Select Records is used to pick records from an already presented list, 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 to retrieve records, Query Records is the correct action.

Agentforce Specialist Reference

This information is confirmed from the Salesforce AI Specialist Material and Questions Document, where the Query Records action is explicitly defined as the appropriate standard action for retrieving filtered CRM records.