Diagnose Agentforce Email Agent Issues

1. Checks whether the agent produced a reply at all. In one case the agent was writing a good reply, so the fault lay further along.
2. Traces the delivery path. In that case Gmail rejected the outbound email because Salesforce servers were not authorized to send from that address (SPF/DKIM). MeshMesh proposed moving the Email-to-Case routing address to a custom domain with proper DNS records, or testing with a non-Gmail recipient.
3. Checks what triggers the agent. In one case a Flow filter on case origin let only web cases through, so cases created by email never reached the agent. MeshMesh confirmed the REST API path worked by creating a test case.
4. Fixes the reply logic where it is wrong and tests it. In one demo it added escalation detection before the LLM call in the REST API path, broadened the phrase lists, deployed the updated classes and ran test cases that passed.
5. Leaves the final check or decision to a human, such as verifying end to end in the inbox UI or deciding whether to extend the Flow to email cases.

Building or extending the email agent itself is covered in Build Agentforce Email Agents.