Sam selected option A to build the robust replacement Agentforce assistant. I used the Salesforce, Litify, Agentforce, and Superpowers workflows, checked live LITIFY_ORG, located the existing Agentforce pilot package, and staged a new read-only mobile operations action.
Created files in /Users/samaguiar/Documents/Projects/Repos/sail-litify/agentforce-builds/jon-hollan-pilot-agent:
force-app/main/default/classes/LitifyMobileOperationsAgentAction.clsforce-app/main/default/classes/LitifyMobileOperationsAgentAction.cls-meta.xmlforce-app/main/default/classes/LitifyMobileOperationsAgentActionTest.clsforce-app/main/default/classes/LitifyMobileOperationsAgentActionTest.cls-meta.xmlforce-app/main/default/genAiFunctions/Litify_Mobile_Operations_Snapshot/Litify_Mobile_Operations_Snapshot.genAiFunction-meta.xmlforce-app/main/default/genAiFunctions/Litify_Mobile_Operations_Snapshot/input/schema.jsonforce-app/main/default/genAiFunctions/Litify_Mobile_Operations_Snapshot/output/schema.jsonforce-app/main/default/genAiPlugins/Litify_Mobile_Operations_Intelligence.genAiPlugin-meta.xmlhandoffs/HANDOFF-litify-mobile-operations-agent-2026-06-14.mdThe new Apex action is bounded and read-only. It can return a compact JSON payload for mobile Agentforce prompts across matters, intakes, overdue tasks, saved conflict-check status, stale treatment updates, high-value case flags, and team workload summaries through Hub_Eligible_Attorney__mdt. It does not create, update, or delete records.
LITIFY_ORG connected as sam@kylawoffice.com, org 00D5e000005AnDpEAK.litify_pm__Matter__c read succeeded.AttorneyHubAgentforceCaseSearchAction and SamHubAgentforceExecutiveSnapshotAction patterns exist and informed the build shape.Hub_Eligible_Attorney__mdt mappings exist for the current attorney hub names.litify__AI_Conflict_Check__c rows during the pass, so the action returns a clear no-saved-conflict-checks notice instead of failing.