The claim
On 17 November OpenAI launched ChatGPT for Sales: an OpenAI-built Sales plugin plus more than 30 new and enhanced partner plugins for account research, meeting preparation, follow-up, and pipeline reviews. Salesforce, HubSpot, Close CRM, and monday CRM supply account and deal context. ChatGPT Business and Enterprise administrators switch the plugins on, and availability varies by plan, region, and workspace settings (OpenAI, vendor, as reported by Unite.AI).
The line that matters to a Salesforce owner: OpenAI’s plugin directory lists the Sales plugin with read and write capabilities, and ChatGPT can draft changes to customer records for review (OpenAI, vendor, as reported by Unite.AI). We could not read OpenAI’s announcement itself from our environment, so every launch detail here comes through that report and OpenAI’s OpenAI sales page.
Two ways into Salesforce
There are now two routes from ChatGPT into a Salesforce org, and they are built differently.
- OpenAI’s Salesforce plugin in ChatGPT for Sales. OpenAI’s sales page says plugins connect context from Salesforce, HubSpot, and Gmail, and that CRM updates can be delegated to agents (OpenAI, vendor). It publishes no objects, permission model, or pricing for that path.
- Salesforce’s own Agentforce Sales app in ChatGPT. In open beta since December 2025 through the ChatGPT app directory, it runs through the Agentforce Trust Layer and respects existing Salesforce permissions (MarTech, independent; SalesforceDevops.net, independent). Sellers can view uncontacted leads, reassign leads, update opportunity stage, and save account plans back to Salesforce (MarTech; Salesforce Ben, independent). It needs an Agentforce for Sales Add-on or Agentforce 1 Edition licence; general availability was expected in early 2026 (SalesforceDevops.net, independent). We have not confirmed its status today.
One secondary write-up says the Salesforce plugin in ChatGPT for Sales includes Salesforce’s Agentforce Sales app (AIera, independent blog, citing other reports). If that holds, the two routes are one. Nobody we read has confirmed it from OpenAI or Salesforce.
The test: six questions, two routes
We put the six questions a Salesforce owner asks before allowing writes against what each route has published. A question counts only if a source we read answers it.
| Question | OpenAI plugin | Agentforce Sales app |
|---|---|---|
| Which objects and fields can it write? | Not published. “Draft changes to customer records” only | Leads, opportunity stage, account plans (MarTech) |
| Whose permissions does a write run under? | Not published | Existing Salesforce permissions (SalesforceDevops.net) |
| Is there a review step before a write? | Yes: drafts for review (Unite.AI) | Not stated in what we read |
| Who can switch it on? | Business and Enterprise admins (Unite.AI) | Eligible customers with the licence (SalesforceDevops.net) |
| What licence or price applies? | Not published | Agentforce for Sales Add-on or Agentforce 1 (SalesforceDevops.net) |
| Where are writes logged? | Not published for the plugin. Activity View is described for dots | Not stated in what we read |
| Answered | 2 of 6 | 4 of 6 |
The counts are our maths on the sources linked in each cell. Assumption: a question is answered only by a published statement, not by a demo or a sales call. Neither route publishes where a write is logged. That is the gap to close before anything is switched on.
What to set in Salesforce
Whichever route your workspace uses, the write lands in your org through mechanisms you already own.
- The OAuth app. An external tool authenticates through a connected app or External Client App. Set it so only admin-approved users can authorise it, assign those users through a permission set, and check the app’s OAuth usage in Setup to see who has connected.
- Whose identity. If each seller signs in as themselves, their profile, permission sets, sharing, and field-level security apply to every write. If the connection uses one shared integration user, every write carries that user’s access and name, and the audit trail loses the seller.
- Your own rules still run. Validation rules and record-triggered flows fire on API writes, so stage gates you enforce for people apply to the agent too. Test that they do.
- The log. Field History Tracking records old and new values on the fields you track. Track Stage, Amount, Close Date, and Next Step before agents touch them. Event Monitoring adds API activity by app, at extra cost.
Plugin hosting is OpenAI’s job. What an agent may change in your pipeline is ours.
Where this breaks
- The primary was unreadable. OpenAI’s announcement page returned an error from our environment. The launch facts come from Unite.AI’s report of OpenAI’s material, which is itself AI-assisted with editorial review.
- The 65% figure is one customer’s estimate. NeoBid’s co-founder estimated around 65% less manual effort with HubSpot and ChatGPT for Sales across prospect research, CRM enrichment, prioritisation, and outreach (vendor, as reported by Unite.AI). No method was published. Do not plan headcount on it.
- Drafting is not writing. “Draft changes for review” is a good default. It holds only if your workspace settings keep it that way for every seller.
- We have not tested the plugin. Nothing here is measured by Prestanda.
Five steps before sellers write from ChatGPT
- Step 1. Find out which route your workspace uses. OpenAI’s Salesforce plugin, Salesforce’s Agentforce Sales app, or both. Owner: Salesforce platform owner with the ChatGPT workspace admin.
- Step 2. Start read-only with a pilot group. Enable the Sales plugin for a named group, and keep writes behind review in the workspace settings. Owner: ChatGPT workspace admin.
- Step 3. Lock the OAuth app. Admin-approved users only, assigned by permission set, each seller signing in as themselves. Owner: Salesforce admin.
- Step 4. Turn on the log. Field History Tracking on Stage, Amount, Close Date, and Next Step; decide on Event Monitoring. Owner: Salesforce admin with revenue operations.
- Step 5. Ask the six questions in writing. Send the table above to OpenAI and your Salesforce account team, and widen the pilot only when the answers are on paper. Owner: sales operations lead with procurement.
Missing
- OpenAI’s announcement read in full.
- The Salesforce objects, fields, and OAuth scopes the OpenAI plugin uses.
- Whether the Salesforce plugin is Salesforce’s Agentforce Sales app.
- Where either route logs a write, and for how long.
- Pricing for the Sales plugin. None was published.
- A Prestanda test of either route.
Frequently asked questions
Can ChatGPT for Sales change records in Salesforce?
It can draft changes to customer records for review, and OpenAI's plugin directory lists the Sales plugin with read and write capabilities, as reported by Unite.AI from OpenAI's launch material. OpenAI has not published which Salesforce objects and fields the plugin can write, or which OAuth scopes it requests.
Is the Salesforce plugin in ChatGPT for Sales the same as Salesforce's Agentforce Sales app?
Not confirmed. One secondary write-up says the Salesforce plugin includes Salesforce's Agentforce Sales app, which runs through the Agentforce Trust Layer, respects existing Salesforce permissions, and needs an Agentforce for Sales Add-on or Agentforce 1 Edition licence. Ask OpenAI and your Salesforce account team in writing which one your workspace uses.
What should a Salesforce admin set before allowing ChatGPT to write to the CRM?
Limit the OAuth app to admin-approved users assigned through a permission set, make sure writes run as each seller rather than a shared integration user, turn on Field History Tracking for the fields an agent may change, and decide whether you need Event Monitoring to see API activity by app.
Living page. Last updated 18 Nov 2026. We update this note when OpenAI publishes the plugin’s scopes and objects, when Salesforce confirms how its app relates to ChatGPT for Sales, or when we run Step 1 ourselves. Want a second pair of eyes on your org before sellers write from ChatGPT? Talk to us.