Prompt Builder is explicitly required to create AI-generated summary fields via prompt templates. These fields use natural language instructions to extract or synthesize information (e.g., summarizing contract terms). Time-to-close estimations (A) and lead scores (C) are typically handled by predictive AI (e.g., Einstein Opportunity Scoring) or analytics tools, which do not require Prompt Builder.
Reference:
Salesforce Help Article: Create AI-Generated Fields with Prompt Builder ("Summary Field Generation" example).
Einstein GPT for Sales Guide: "Automating Contract Summaries."

Comprehensive and Detailed In-Depth Explanation:
UC's development team needs to identify a core component of a Custom Agent Action in Agent Builder. Let' s assess the options.
* Option A: Action Triggers"Action Triggers" isn't a term used in Agentforce Custom Agent Action configuration. Actions are invoked by topics or plans, not standalone triggers, making this incorrect.
* Option B: InstructionsInstructions are a core component of a Custom Agent Action in Agentforce.
Defined in Agent Builder, they guide the Atlas Reasoning Engine on how to execute the action (e.g., what to do with inputs, how to process data). Reviewing the instructions helps the team understand the action's purpose and logic, making this the correct answer.
* Option C: Output TypesWhile outputs are part of an action's result, "Output Types" isn't a distinct configuration element in Agent Builder. Outputs are determined by the action's execution (e.g., Flow or Apex), not a separate setting, making this less core and incorrect.
Why Option B is Correct:
Instructions are a fundamental component of Custom Agent Actions, providing the AI's execution directives, as per Salesforce documentation.
References:
Salesforce Agentforce Documentation: Agent Builder > Custom Actions - Highlights instructions as key.
Trailhead: Build Agents with Agentforce - Details configuring actions with instructions.
Salesforce Help: Create Custom Actions - Confirms instructions' role.

Comprehensive and Detailed In-Depth Explanation:
UC has created a custom flow for processing returns and linked it to a new Agent Action for the Agentforce Service Agent, an AI-driven agent for customer service tasks. The agent must have the ability to execute this flow. Let's assess the options.
* Option A: Recreate the flow using the Agentforce agent user.Flows are authored by admins or developers, not "recreated" by specific users like the Agentforce agent user (a system user for agent operations). The issue isn't the flow's creation context but its execution permissions. This option is impractical and incorrect.
* Option B: Assign the Manage Users permission to the Agentforce Agent user.The "Manage Users" permission allows user management (e.g., creating or editing users), which is unrelated to running flows. This permission is excessive and irrelevant for the Service Agent's needs, making it incorrect.
* Option C: Assign the Run Flows permission to the Agentforce Agent user.The Agentforce Service Agent operates under a dedicated system user (e.g., "Agentforce Agent User") with a specific profile or permission set. To execute a flow as part of an Agent Action, this user must have the "Run Flows" permission, either via its profile or a permission set (e.g., Agentforce Service Permissions). This ensures the agent can invoke the custom flow for processing returns, aligning with Salesforce's security model and Agentforce setup requirements. This is the correct answer.
Why Option C is Correct:
Granting the "Run Flows" permission to the Agentforce Agent user is the standard, documented step to enable flow execution in Agent Actions, ensuring the Service Agent can process returns as intended.
References:
Salesforce Agentforce Documentation: Agent Builder > Custom Actions- Requires "Run Flows" for flow- based actions.
Trailhead: Set Up Agentforce Service Agents- Lists "Run Flows" in agent user permissions.
Salesforce Help: Agentforce Security > Permissions- Confirms flow execution needs.

When creating a custom action for Einstein Bots in Salesforce (including Agentforce), Action Instructions are critical for defining how the bot processes and executes the action. These instructions guide the bot on the logic to follow, such as API calls, data transformations, or conditional steps. Testing and iterating on the instructions ensures the bot understands how to handle dynamic inputs, external integrations, and decision- making.
Salesforce documentation emphasizes that Action Instructions directly impact the bot's ability to execute workflows accurately. For example, poorly defined instructions may lead to incorrect API payloads or failure to parse responses. The Einstein Bot Developer Guide highlights that refining instructions is essential for aligning the bot's behavior with business requirements.
In contrast:
* Action Name (A) is a static identifier and does not affect functionality.
* Action Input (B) defines parameters passed to the action but does not dictate execution logic.
Thus, iterating on Action Instructions (C) ensures the action performs as expected.
Reference:
Salesforce Help Article: Create Custom Actions for Einstein Bots
Einstein Bot Developer Guide: "Custom Action Configuration Best Practices" (Section 4.3).

WhenUniversal Containers' AI data masking rulesdo not meet organizational privacy and security standards, the Agentforce Specialist should configure thedata maskingrules within theEinstein Trust Layer.
TheEinstein Trust Layerprovides a secure and compliant environment where sensitive data can be masked or anonymized to adhere to privacy policies and regulations.
* Option A, enabling data masking for sandbox refreshes, is related to sandbox environments, which are separate from how AI interacts with production data.
* Option C, adding masking rules in the LLM setup, is not appropriate because data masking is managed through theEinstein Trust Layer, not the LLM configuration.
The Einstein Trust Layer allows for more granular control over what data is exposed to the AI model and ensures compliance with privacy regulations.
Salesforce Agentforce Specialist References:
For more information, refer to:https://help.salesforce.com/s/articleView?id=sf.
einstein_trust_layer_data_masking.htm