Agentforce · Agent Builder16 tasks
Diagnose Agentforce Record Context Issues
When an agent on a record page ignores the record the user is looking at, or asks which record to use, MeshMesh finds out why and changes the agent so it picks up that record.
Method
How MeshMesh does it
- Starts from the symptom the user reports. Examples are a compliance review agent that kept asking which grantee to assess and an assistant that asked for an account name instead of using the record page.
- Traces the cause in the agent setup and writes an implementation plan for the fix.
- Works out how the record reaches the agent. In one case that meant finding the name the record ID variable must use and that visibility comes from permission sets.
- Adds an Apex action that resolves the current record to the value the agent needs.
- Rewrites topic or reasoning instructions so the agent uses the record first. This was done through the Tooling API in one case and as a step-by-step resolution flow in another.
- Publishes and activates a new agent version through the Builder UI.
- Hands steps back to the user when access limits block them, such as deactivating the active agent. Testing on the real record page was also left open.