New video: 6 Ways Claude Can Be Your Motion Designer →
Muddaser

ChatGPT for Sales Setup: CRM Plugins, Prompts & Safety

Direct answer: ChatGPT for Sales is an OpenAI Sales plugin plus partner plugins that can connect sales tools such as HubSpot, Salesforce, Clay, Gong, ZoomInfo and Docusign. The Sales plugin is available globally on all ChatGPT plans, including Free, but each partner plugin can have separate plan, region, workspace, subscription and permission requirements.[1][2]

To start safely, install Sales, connect only one read-oriented tool such as your CRM, test an account brief against the source records, and require human approval for messages or CRM changes. Do not connect the entire sales stack on day one.

Quick setup checklist

  1. Open the official Sales plugin listing in the ChatGPT account or workspace you intend to use.
  2. Select Install plugin.
  3. Under Works with, choose one partner plugin—preferably the CRM your team already maintains.
  4. Select Connect, sign in to the correct work account, and review the requested permissions.
  5. Start with read access or an approval-first permission setting where available.
  6. Run one account-brief test and compare every important detail with the linked CRM records.
  7. Add write actions only after the read-only pilot is accurate and useful.
  8. Document who owns access reviews, failed actions and CRM corrections.

OpenAI recommends starting with one tool, and installing the Sales plugin does not automatically connect partner accounts or include paid partner subscriptions.[2]

What ChatGPT for Sales actually includes

The new experience has two layers:

  • OpenAI’s Sales plugin: reusable sales skills for account research, meeting preparation, outreach, follow-up and pipeline work.
  • Partner plugins: connections to the systems that contain customer, prospect, conversation, document and deal data.

OpenAI announced more than 30 new or expanded partner plugins. Its launch examples include Salesforce, HubSpot, Close CRM and monday CRM for account management; Apollo, Clay and Common Room for buyer research; Gong, Otter.ai, Granola and the Meetings plugin for conversation context; and Docusign, Ironclad, PandaDoc and ServiceNow CPQ for quotes and agreements.[1]

A plugin is not the same as an app connection. OpenAI defines a plugin as a package that can combine skills, connected apps, templates and interactive extensions. Installation still cannot bypass the connected provider’s authorization or the ChatGPT workspace’s permissions.[3]

Who can use it?

OpenAI’s current setup guide says the Sales plugin is available globally on all ChatGPT plans, including Free, through ChatGPT web, desktop and mobile.[2] That does not mean every connected workflow is free or universally available.

Access can still depend on:

  • the selected partner plugin;
  • the user’s ChatGPT plan and region;
  • workspace administrator settings;
  • whether the partner supports the current web, desktop or mobile surface;
  • an active subscription with the partner;
  • the user’s permissions inside the CRM or other source system.

If the plugin appears but a capability does not work, check the underlying app rather than repeatedly reinstalling Sales.

How to install ChatGPT for Sales as an individual user

Step 1: Open the correct workspace

Before installing anything, confirm whether you are in a personal account or your company’s managed workspace. Connecting a work CRM from the wrong workspace creates avoidable governance and offboarding problems.

Step 2: Install Sales

Open the Sales plugin listing and select Install plugin. If no install button appears, check the account, plan, region and workspace restrictions.[2][3]

Step 3: Add one partner plugin

Under Works with, select the system needed for the first test. A sensible first pilot is one CRM plus Sales—not a CRM, inbox, call recorder, file store and contract system simultaneously.

Step 4: Authorize the intended account

Select Connect, sign in to the correct provider account and inspect the requested permissions. Your provider account still determines which records the connection can access.[2][3]

Step 5: Run a source-linked test

Use a real but low-risk account with records your pilot owner understands. Ask for linked evidence, missing fields and a clear separation between facts found in the CRM and suggestions generated by the model.

Try this:

@Sales, use @[CRM] to prepare a pre-meeting brief for [account]. Include company context, active opportunities, recent activity, known stakeholders, commitments, risks, missing information and five questions to ask. Link every CRM-derived point to its source record. Do not update any record or send any message.

OpenAI’s own starter workflow tells users to check source records and review follow-up messages or CRM changes before approving a supported action.[2]

Administrator setup for Business and Enterprise

For managed workspaces, a ChatGPT Business or Enterprise administrator can:

  1. Open Admin Console.
  2. Select the intended ChatGPT workspace.
  3. Open Plugins.
  4. Select Sales and the approved partner plugins.
  5. Choose Available for installation or Installed for workspace.
  6. Review each required app separately, including access, actions and provider permissions.
  7. Test with an eligible pilot user.

OpenAI says administrators can change up to 25 plugins at a time. Default installation does not authorize each seller’s individual partner account, and plugin installation and underlying app access remain separate controls.[2][3]

Recommended pilot policy

Use the following conservative starting configuration:

  • Pilot group: three to ten sellers plus one sales-operations owner.
  • Data scope: one CRM and a small set of ordinary accounts; exclude regulated or unusually sensitive records initially.
  • Actions: read access first; no automatic email, opportunity-stage, contract or pricing changes.
  • Approvals: require confirmation before any write action.
  • Duration: five working days or enough activity to evaluate at least 20 briefs.
  • Success measures: preparation time, factual correction rate, source-link usefulness and accepted versus rejected suggestions.
  • Exit criteria: remove access if the connection cannot consistently respect permissions or sellers cannot verify the output quickly.

This is a pilot design, not an OpenAI requirement. It keeps the test reversible and produces evidence for a wider rollout decision.

Six copy-and-paste prompts

Replace bracketed text and the plugin name with the systems available in your account.

1. Account brief

@Sales, use @[CRM] to create a one-page brief for [account]. Separate verified CRM facts, missing information and your recommendations. Include links to the source records. Do not change the CRM.

2. Meeting preparation

@Sales, use @[CRM] and @[meeting-notes tool] to prepare for my meeting with [account]. Summarize previous commitments, unresolved questions, stakeholder priorities and possible risks. Give me seven questions, ordered by importance. Do not invent a budget, deadline or decision maker.

3. Follow-up draft

@Sales, turn these meeting notes into: (1) a customer-ready follow-up email, (2) an internal summary, and (3) proposed next steps with owners and dates. Mark anything not explicitly agreed as “proposed.” Do not send the email or update any record.

4. Pipeline-risk review

@Sales, use @[CRM] to review my open pipeline for [month/quarter]. Rank deals by evidence of risk, show the source signals, identify stale or contradictory fields, and suggest the smallest next action. Do not change stages, close dates or forecasts.

5. CRM hygiene check

@Sales, inspect the permitted records for [segment]. List missing next steps, overdue activities, unsupported close dates and duplicate-looking contacts. Return a review queue only. Make no changes.

6. Proposal readiness

@Sales, use @[CRM] and @[document tool] to create a proposal-readiness checklist for [account]. Include confirmed requirements, unresolved commercial questions, legal or security dependencies and the records supporting each item. Do not create or send a contract.

What not to automate first

Avoid using the first pilot for:

  • bulk outbound messages;
  • automatic opportunity-stage or forecast changes;
  • discounts, pricing promises or contract terms;
  • deletion or merging of CRM records;
  • autonomous handling of objections involving legal, security or compliance commitments;
  • unattended actions by an always-on agent;
  • importing a large prospect list without a lawful basis and internal approval.

OpenAI says a dot can use plugins and customer context to prepare briefs, track updates and propose next steps for review.[1] Treat “for review” as the important control: a recommendation is not permission to contact a buyer or modify the system of record.

Privacy and security checklist

Use least privilege

Connect the smallest useful account and data scope. A sales representative should not gain access to records they could not already view in the source system; plugins remain subject to provider authorization and workspace controls.[3]

Separate read and write actions

Reading an opportunity and changing its stage are different risks. Keep write actions disabled or approval-gated until the team has tested the read workflow.

Review every partner

OpenAI can govern its workspace and plugin layer, but information sent to a connected third party is also subject to that provider’s terms. Review each CRM, call-recording, enrichment and document vendor—not only OpenAI.

Verify the business-data policy

OpenAI states that it does not train its models on ChatGPT Business or Enterprise business data by default. It also says workspace administrators control which apps are enabled, users authenticate to connected apps, and app access respects existing organizational permissions.[4] This does not replace your own privacy, contractual or regulatory review.

Keep high-impact facts human-owned

A person should confirm prices, discounts, legal commitments, security claims, buyer identities, meeting promises and deal-stage changes. Ask the output to mark missing or conflicting evidence instead of filling gaps.

Plan offboarding

When a team member changes roles or leaves, remove access in both ChatGPT and the connected provider. Disconnecting only one layer can leave unnecessary authorization or a confusing installed plugin behind.

A practical five-day rollout

Day 1: Define the job

Choose one measurable task such as pre-meeting briefs. Write down the current process, expected output and fields that must never be guessed.

Day 2: Configure access

Install Sales and one CRM plugin. Confirm the pilot users, account scope, allowed actions and approval setting. Capture the configuration for later review.

Day 3: Test ordinary and difficult records

Run at least five accounts: complete, incomplete, stale, duplicate-prone and permission-restricted. Record errors rather than quietly correcting the prompt until it appears to work.

Day 4: Measure usefulness

Compare time saved with correction time. Track unsupported statements, missing source links, stale data and suggestions the seller rejected.

Day 5: Decide

Expand only if sellers can verify the output faster than creating it manually and the permission model is clear. Otherwise, narrow the task, improve CRM hygiene or stop the pilot.

Troubleshooting

The Sales plugin is missing

Confirm that you are in the intended account or workspace, then check plan, region and workspace availability. Managed-workspace users should ask an administrator to review the plugin and required app.[2][3]

The CRM connection fails

Verify the selected provider account, active partner subscription and required permissions. Some connections require approval from the provider’s administrator.[2]

The plugin can read but not update

The app may not support that action, the workspace may block it, or the provider account may lack permission. Do not broaden all permissions just to make one action work.

The answer contains stale details

Open the linked source record and check its last update. ChatGPT cannot repair poor CRM hygiene automatically. Ask it to label conflicting fields and send them to a human review queue.

A plugin is installed but its app is unavailable

Plugin installation and app access are separate. A skill-only part may still work while the required app-backed capability remains blocked.[3]

Frequently asked questions

Is ChatGPT for Sales a separate ChatGPT plan?

No. OpenAI describes it as a plugin experience within existing ChatGPT plans. The Sales plugin is available on all plans, while partner tools and features can have separate requirements.[2]

Is ChatGPT for Sales free?

The Sales plugin is available on the Free plan, but this does not include paid subscriptions to Salesforce, HubSpot, ZoomInfo or other partners. Usage and feature availability still depend on the relevant ChatGPT and partner plans.[2]

Does it work with HubSpot and Salesforce?

Yes. OpenAI lists both among the CRM options in the launch materials and plugin experience.[1]

Can ChatGPT update CRM records?

Some partner apps support write actions, but the action must be supported and allowed by provider authorization and workspace settings. Review every proposed change before approval during a pilot.[2][3]

Can it send sales emails automatically?

Connected tools may support actions, but autonomous outbound email is a poor first pilot. Start with drafts and human approval, then evaluate narrowly scoped actions only after accuracy and permissions are proven.

Does OpenAI train on Business or Enterprise sales data?

OpenAI says it does not use ChatGPT Business or Enterprise business data for model training by default, including information accessed through apps.[4]

Why can I see Sales but not a partner plugin?

Partner availability can vary by plan, region, workspace and supported client. The partner subscription or provider-account permission may also be missing.[2][3]

Bottom line

ChatGPT for Sales is most useful as a controlled layer over tools your team already trusts—not as a replacement for CRM ownership or seller judgment. Start with one read-oriented workflow, demand source links, measure corrections, and add write access only when the evidence supports it.

Sources

  1. Introducing ChatGPT for Sales | OpenAI
  2. Getting started with ChatGPT for Sales | OpenAI Help Center
  3. Plugins in ChatGPT | OpenAI Help Center
  4. Enterprise privacy at OpenAI


Leave a Comment