Question 350
At Westmoor Sports, a consumer membership desk is improving membership renewals after a knowledge-policy revision (SF-A15-02). The administrator observes that an agent explains case policy correctly but cannot execute an approved follow-up Flow. Any fix must ensure that member records cannot be exposed to other members. Which action best addresses the issue while preserving the stated requirement?
Explanation
Correct Answer
The documented failure is that an agent explains case policy correctly but cannot execute an approved follow-up Flow. Expose the existing supported Flow as an agent action with mapped inputs and output handling for Westmoor Sports's membership renewals workflow (SF-A15-02) while respecting that member records cannot be exposed to other members. Its outcome is not established merely by changing instructions: In a controlled Contact acceptance test, a test conversation invokes the Flow with the intended case ID and receives its status; the record is retained under Westmoor Sports's rollout (SF-A15-02). The underlying reason is that Actions let agents execute governed Salesforce automation beyond text generation. In this membership renewals scenario, this separates supported agent behavior from assumptions about the AI model.
Incorrect Answers
The action “Configure the applicable standard topic and action instead of duplicating a custom implementation; implement it with least-privilege execution” addresses a separate source case: A customer asks for a common supported case status operation already provided by a standard Agentforce topic. The correction must ensure that part inventory decisions use approved current records. Its underlying reason is: Standard agent topics can be reused when they already fit the task. This question instead describes an agent explains case policy correctly but cannot execute an approved follow-up Flow. The correction must ensure that member records cannot be exposed to other members. The original answer “Expose the existing supported Flow as an agent action with mapped inputs and output handling; implement it within the documented Salesforce configuration” targets that failure because actions let agents execute governed Salesforce automation beyond text generation.
The action “Enforce the amount and eligibility constraints before allowing the action; implement it with traceable change approval” addresses a separate source case: A refund action accepts an unverified customer amount and bypasses the approved amount limit. The correction must ensure that member records cannot be exposed to other members. Its underlying reason is: Natural-language instructions alone are weaker than deterministic protected-action controls. This question instead describes an agent explains case policy correctly but cannot execute an approved follow-up Flow. The correction must ensure that member records cannot be exposed to other members. The original answer “Expose the existing supported Flow as an agent action with mapped inputs and output handling; implement it within the documented Salesforce configuration” targets that failure because actions let agents execute governed Salesforce automation beyond text generation.
The action “Design and validate the email channel integration for asynchronous delivery and authorization; implement it with least-privilege execution” addresses a separate source case: A team assumes an asynchronous support email flow has the same state and latency as an interactive web chat. The correction must ensure that billing adjustments require verified eligibility. Its underlying reason is: Channel context changes how an agent receives messages and maintains interaction. This question instead describes an agent explains case policy correctly but cannot execute an approved follow-up Flow. The correction must ensure that member records cannot be exposed to other members. The original answer “Expose the existing supported Flow as an agent action with mapped inputs and output handling; implement it within the documented Salesforce configuration” targets that failure because actions let agents execute governed Salesforce automation beyond text generation.