Two kinds of account context
A sales rep preparing a call needs two things from the AI. The facts: who the contacts are, which deal is open, what stage it is in, when the last activity was. And the context around the facts: what the buyer said about budget, which objection came up twice, which discount the sales lead allows for this segment, why the last proposal stalled.
The first kind lives in the CRM. The second mostly lives in people: in call notes nobody reads, in Slack, and increasingly in each rep’s own AI chats.
| Where it lives | Does the AI of a colleague see it? | |
|---|---|---|
| Contacts, deals, stages, activities | CRM | Yes, through a connector, within that colleague’s CRM permissions |
| Proposals, decks, notes in files | Drive, SharePoint | Yes, if connected and shared with them |
| What the buyer said on the call | Call notes, the rep’s head | Only if someone wrote it down in a shared place |
| How the team sells (discount rules, positioning) | Playbook document, the sales lead’s head | Only if it is in a shared project or document |
| What the rep told their AI last week | The rep’s personal AI memory and chats | No |
Getting the facts in: CRM connectors
- HubSpot with Claude. HubSpot launched its connector for Claude on 29 July 2025. A Super Admin, or someone with App Marketplace permissions, sets it up first; then every rep with a HubSpot user and a paid Claude plan (Pro, Max, Team or Enterprise) connects their own account. Since November 2025 it can view, create and update CRM records and log activities, but not delete; it also reads the engagement history (emails, calls, meetings, tasks and notes). It respects each user’s HubSpot permissions and cannot reach properties marked as sensitive.
- Salesforce with Grok. An admin adds the Salesforce connector in the xAI console with your OAuth credentials; each member then connects at grok.com/connectors. Grok can explore objects, query records, and create or update leads, opportunities, accounts and cases, always within the rep’s Salesforce profile, role, sharing rules and field-level security. xAI states it queries in real time and does not store your records.
- Shared sources in ChatGPT. In a ChatGPT project you can add Google Drive files and folders and Slack channels as sources, and connected apps work in project chats.
Getting the context in: the harder half
Connectors can also retrieve account context recorded in the CRM: HubSpot’s Claude connector accesses emails, calls, meetings, tasks and notes. Context that exists only in a rep’s private AI chats still needs a shared place. That knowledge is created in conversations, and AI memory keeps it per person. OpenAI states that ChatGPT Business memories are tied to each account and cannot be transferred to other users, even in the same workspace. Claude’s memory works per user too, with a separate memory per project.
The practical fix inside one tool is a shared project per account or segment, with a short account brief as a file and the team’s selling rules as instructions. A shared ChatGPT project uses project-only memory, so its context does not mix with personal memories. Someone has to keep the brief current after each important call.
The common misunderstanding
Teams expect that connecting the CRM makes the AI “know the account”. It knows the fields. The reason a deal is stuck is rarely in a field. And because every rep’s AI only reads what that rep may see, two reps can get different answers about the same account, both correct within their permissions.
What this means for a sales team
When a rep leaves or an account changes hands, the CRM history stays and the conversational context goes. The same happens when the team uses different tools: a brief in a Claude project is invisible to the rep who prepares in ChatGPT or Grok. For consistent messaging across a go-to-market team, see how to keep AI-written messaging consistent; for call prep, how to automate pre-call account research.
Where Bombos fits
Bombos is a plugin that gives every AI tool your team uses one shared memory. For sales, that is the context around the CRM: what was learned about an account, the rules the team sells by, and what already sits in mail and documents, available to every rep’s Claude, ChatGPT, Grok or Copilot, with a trace to where it came from. It runs in our cloud or on your own server, and one rep can try it first with their own agents.
Related questions
Can the HubSpot connector for Claude update deals?
Yes. The HubSpot connector for Claude can create and update contacts, deals and other supported CRM records, and log activities, within the connector's approved access and the user's HubSpot permissions. It cannot delete records.
Does Grok copy our Salesforce data?
xAI states that Grok queries Salesforce in real time, does not copy or store records on its servers and does not train on the data. The connector can also create and update records, within your Salesforce profile, role, sharing rules and field-level security.
Will a rep see deals they cannot see in the CRM?
No, for both connectors described here. HubSpot says its Claude connector respects the user permissions in HubSpot; xAI says Grok can never access more than the connected Salesforce user may see or modify.
Can a shared ChatGPT project hold account notes for the team?
Yes. A shared project draws on its chats, files and instructions for everyone in it, and OpenAI states shared projects use project-only memory. It only helps people who work in that ChatGPT project.
Sources
- HubSpot Developers: HubSpot connector for Claude (29 July 2025)
- HubSpot Knowledge Base: Set up and use the HubSpot connector for Claude
- HubSpot Developers: Claude write access to CRM (20 November 2025)
- xAI docs: Salesforce connector for Grok
- OpenAI Help: Projects in ChatGPT
- OpenAI Help: Memory FAQ (Business version)
- Claude Help Center: Use Claude's chat search and memory
