# ChatGPT for Sales: Setup, Permissions and Your First Account Brief

The Sales plugin brings CRM and call context into ChatGPT, but a useful first workflow depends on which accounts and actions you actually connect.

By Paras Madan | 2026-11-18


OpenAI launched ChatGPT for Sales on November 17, combining a Sales plugin with new and expanded partner integrations. You can use it to prepare for calls and work through account information. Before asking it to manage your pipeline, I would start with one account brief and check every source.

## What the Sales plugin adds

The [launch announcement](https://openai.com/index/introducing-chatgpt-for-sales/) describes sales-specific workflows alongside more than 30 new or enhanced partner plugins. CRM records, customer conversations and prospect research can become inputs to the same task, rather than material you manually assemble in a prompt.

For a founder, the useful starting point is a meeting you already have. A brief grounded in the buyer's previous questions is more valuable than another company summary assembled from its homepage.

OpenAI's [sales directory](https://openai.com/business/solutions/sales/) lists tools including Salesforce, HubSpot, Gong, Granola and Clay. Pick the systems that hold your actual account history. You do not need to connect the whole directory to find out whether the workflow helps.

## Install the plugin, then connect the right accounts

In ChatGPT, open Plugins and find Sales. Review what it includes and complete installation where available. Install the relevant partner plugin too, then finish any account-connection prompts. OpenAI's [plugin setup guide](https://help.openai.com/en/articles/20001256-plugins-in-chatgpt) explains that installation and provider authorization are separate steps.

You can select an installed plugin through an @ mention or the plugin controls shown in your composer. Features can differ by plan, region, workspace and product surface, so a directory listing alone is not proof that your account can use every advertised feature.

For Business and Enterprise teams, the launch instructions direct administrators to Admin Console, select the intended workspace, then open Plugins. Make Sales and the required partner plugins available, or install them for the workspace. Members still complete the connections required for their accounts.

## Check access before allowing changes

There are three questions to resolve: who can use the app, which actions it supports and allows, and when it asks for approval. OpenAI's [admin controls documentation](https://help.openai.com/en/articles/11509118-admin-controls-security-and-compliance-for-plugins-and-apps) treats these separately from provider authorization.

An installed plugin may still depend on a disabled app. A connected CRM account may lack access to the opportunity you need. Where action controls are supported, administrators can distinguish reading from writing; not every app exposes the same controls.

For the first trial, I would keep the task read-only. Preparing a follow-up and sending it should be separate decisions. A seller should also review proposed CRM changes before an incorrect close date or speculative buyer commitment becomes part of the team's forecast.

## Try this first-account-brief prompt

Here is a proposed starting prompt, not a tested result:

> Prepare a meeting brief for [company] using the connected CRM and the latest available customer-call notes. Confirm the exact company and opportunity first. Give me the buyer's stated problem, the people involved, commitments from the last conversation, unresolved questions and the next step currently recorded. Link each important fact to its source and include the source date. Separate direct customer statements from your interpretation. If sources disagree or are unavailable, say so. Do not send messages or change records.

Use an account you know well enough to judge. Check whether the brief distinguishes the buyer's request from your colleague's suggestion, and whether it finds the latest conversation rather than an older, more detailed one.

I would reject a polished brief that invents certainty. “Budget is approved” and “the buyer plans to seek budget approval” lead to very different sales conversations. Your first evaluation should catch that difference.

## If the account brief is missing information

Follow the specific failure rather than repeatedly reconnecting everything. The [troubleshooting guide](https://help.openai.com/en/articles/20001497-troubleshooting-plugins-and-apps-in-chatgpt) separates app availability, account authorization, content retrieval and action failures.

If the app is missing, check the workspace, plan and supported surface. If the connection fails, verify the provider account and required permissions. If an account record cannot be found, confirm that the connected user can open it in the CRM itself. Finding a file name also does not establish that its contents were retrieved.

For an uncertain email send or CRM update, inspect the destination before retrying. Otherwise, a temporary error can become two follow-ups or a duplicated record change.

## Expand only after the brief is reliable

Compare the brief with your own preparation across a few familiar accounts. Track missing commitments, unsupported claims and the time you spend correcting it. Those observations will tell you more than the number of integrations you enabled.

Then try drafting the post-call follow-up from verified notes. The useful progression is from reliable account context to a specific action you can review, with enough evidence to understand why it was proposed.

I'm Paras. I work across AI, engineering and distribution.

I help technical founders turn product knowledge and customer insight into clear stories people want to read.

[Book a 30-minute call](https://cal.com/paras-madan/30min).
