The right pattern for AI prospecting in Salesforce is read-only by default, with writes gated by human review. The agent reads accounts, opportunities, and activity through the Salesforce REST API, drafts a brief and a proposed next step, and the rep edits before any field updates. Einstein and Agentforce sit on the same plumbing. Every CRM write carries attribution back to the source.
The workflow
1. Pull account context, do not push first. Query the Salesforce REST API: account, open opportunities, last 90 days of activities, contacts. Gong adds call transcripts. ChatGPT or Claude summarize into a one-page brief. Nothing written back yet. For which accounts deserve this effort, see AI ICP scoring.
2. Draft the research, not the update. The agent produces a structured brief: org changes, product fit, 3 personalization angles, proposed next step. Clay enrichment fills firmographic gaps. The rep edits before it touches Salesforce.
3. Propose field updates with attribution. When the agent suggests a CRM change (next step, close date, stage, competitor), the proposal is logged with reasoning and sources. Salesforce Agentforce can be configured this way; an Apex trigger reading from a queue works too. No silent writes.
4. Pipeline review reads the briefs, not just the stage. During forecast calls, the AE pulls up the agent brief alongside the opportunity. Einstein opportunity scoring shows the model's signal; the brief shows the narrative. Disagreements are the most useful conversation in the review.
5. Close the loop on the call. After a discovery, Gong or a Claude summarizer drafts the recap, next step, and field updates. The rep edits. Salesforce gets the clean version with a link back to the recording.
Worked example: AE working a top-of-funnel account
A mid-market AE picks up a re-engaged account. The agent pulls 18 months of Salesforce history, recent Gong calls from the previous cycle, and LinkedIn org signals. It drafts: "Last lost to Competitor X over data residency. New VP of Eng started 4 months ago, posted about consolidating vendors." Proposed next step: warm intro through the original SDR. The AE edits the angle, accepts the next step, and Salesforce records the activity with a pointer to the brief.
The persistent-state pain
The CRM record holds the outcome but not the interpretation. The stage moved to Discovery; nobody can see why. The competitor field is "Competitor X"; nobody can see which call surfaced it. Reps stop trusting fields they cannot audit, then stop updating them, and the CRM cleanup project starts again next quarter.
One way to solve this is a workspace like Dock for sales that holds the agent's interpretation around the deal: the research brief, the personalization rationale, the proposed next step, the post-call summary. Each Dock row carries salesforce_account_id and salesforce_opportunity_id pointers. Salesforce stays the system of record for the account, contact, and stage. Dock stores what the agent thought and why, with the agent identity on every write so reviewers can trace it.
Why this matters
HBR reports only 3% of company data meets basic quality standards. CRM pollution is an attribution problem. Workflows that compound are the ones where every agent write can be traced.
Read the full pillar: AI sales prospecting that actually compounds.
FAQ
Should the AI agent write directly to Salesforce fields? Not by default. Have the agent propose updates with the source brief attached. A rep accepts or edits. Direct writes are reserved for low-risk fields like activity logs and call recordings.
Where does Salesforce Agentforce fit in? Agentforce handles the in-Salesforce surface: side panel, suggested next step, draft email. The brief, the call summary, and the reasoning still need a store with audit and compliance trails.
How do we keep the agent from inventing competitor or budget data? Require source citations on every claim. The Salesforce REST API returns structured records; pair them with Gong transcripts. If the agent cannot cite a source, the field stays empty.
What about Einstein opportunity scoring? Useful as a second signal during pipeline review. Treat the score and the agent brief as independent reads. When they disagree, that is the conversation worth having on the forecast call.