Mention @ChatGPT in a Slack or Teams thread and teammates can refine the answer without their own license. Business and Enterprise plans only.
The deal already lives in the channel. The pricing question, the competitor rumor from this morning's call, the scramble over a security questionnaire — that conversation happens in Slack or Teams, and getting ChatGPT involved used to mean copying it out, pasting it somewhere else, and pasting the answer back. The license line is the part that changes the math for a rep: a sales engineer, a deal desk reviewer and a manager can all push on the same answer in the same thread without each holding a ChatGPT seat. That moves the assistant out of a private window and into a thread where the people who actually know the account can correct it in front of everyone.
"Mention @ChatGPT in a channel" means typing @ChatGPT the way you would tag a colleague. It answers in the thread, everyone in the thread sees the answer, and anyone can reply to push it further.
"Tools connected by your admin" is the plumbing that lets it reach systems outside the chat window — the connections your IT or ops team has already set up. "Your own tools with your permissions" means that when it acts for you, it is limited to what your account can already see, not everything the company has.
"Without needing an individual ChatGPT license" means the seat belongs to the workspace rather than the person. The colleague who never signed up can still correct the answer in the thread.
The short version: you can tag ChatGPT into a deal thread, and the people in that thread can argue with it without buying anything.
OpenAI announced at DevDay 2026 on September 29, 2026 that ChatGPT can be mentioned directly inside Slack and Microsoft Teams. In OpenAI's words, you "Mention @ChatGPT in a channel, thread or DM to get help with your team's work." The assistant "can use tools connected by your admin or your own tools with your permissions," and "Teammates can add context and refine the results in the same conversation without needing an individual ChatGPT license."
Announced: September 29, 2026, at OpenAI DevDay 2026.
Availability: "Available to all Business and Enterprise plans." No rollout timeline or phased dates stated.
Price: Not stated.
Regions: Not stated.
What it doesn't do: OpenAI does not say the integration writes anything back to a CRM. It names no chat platform other than Slack and Microsoft Teams. It does not extend to Free, Plus or Pro plans. It states no retention, residency or compliance terms for the messages the assistant reads in a channel. The tools it can reach are the ones an admin connected or ones the individual authorized — nothing in the announcement grants it access on its own.
SDR — Your fastest use is the inbound triage thread. When a lead lands and the channel starts guessing whether it is worth a call, tag @ChatGPT with the lead's own words and ask it to list what you still don't know before you dial. The gap list is the output, not the pitch. Don't have it write your first touch in a public channel, where a manager will read a generic opener with your name on it.
AE — Use it where the thread already holds the facts: a long deal channel with pricing pushback, a legal objection and three half-answers. Ask it to separate what the buyer actually committed to from what the team inferred. Then correct it in the thread, out loud, so the correction becomes part of the record. Everything it says in a channel is visible to your manager, which makes accuracy worth more than speed here.
Manager — The license line is your lever: a whole deal team can work with the assistant without a seat each, so pilot it in two live deal channels instead of buying broadly. Watch the failure mode it creates — a confident summary of a deal that nobody on the call verified, now sitting in the channel looking authoritative. Make it a standing rule that any claim about what a buyer committed to gets confirmed by the person who was on the call.
RevOps — Two sentences in this announcement decide your risk: which tools the admin connects, and whether per-user permissions genuinely scope what it can see. OpenAI states nothing about retention or data residency for channel messages, so get that from your account team before the assistant is reading a channel full of pricing and named accounts. Decide now how any of it reaches the CRM, because the announcement does not say it does.
A channel conversation is worst at telling you what you still don't know about the account. Run this on the thread to get a brief that names the gaps, then take those gaps back into the channel and ask the people who were on the calls.
Two minutes, once a week. What changed in AI, and what to run because of it.