Agentforce is escalating cases to the support team, but the support team complains they have no context and have to ask the customer to repeat everything. Which configuration issue is the most likely cause of this issue?
A.
The support team members are missing the Agentforce User permission set.
B.
The support team’s case page layout is missing the agent history component.
C.
The agent’s instructions are preventing the history and context from being saved.
D.
The handoff is creating a new case instead of transferring the existing session.
When an AI agent like Agentforce transfers a conversation to a human support representative, the goal is a "warm handoff" where the rep can see exactly what the customer and the AI discussed. If reps are complaining about a lack of context, the most common administrative cause is that the Conversation History component (or Agent History component) has not been added to the Case Lightning Record Page. Without this component on their page layout, the rep sees the newly assigned case but cannot see the transcript of the preceding chat session. To resolve this, the Platform Administrator should use the Lightning App Builder to add the relevant history component to the Case page used by the support team. Option D is less likely if escalation is working but context is missing. Option A would prevent users from using Agentforce features but wouldn't specifically hide the transcript of a finished AI interaction. Ensuring the UI includes the conversation history is critical for maintaining high customer satisfaction during handoffs.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit