Use casesUse case

A shared memory for a sales team and its AI tools

A sales team keeps one engine for its accounts: each salesperson's AI tool saves customers, people, meetings, decisions and open tasks as they work, and anyone on the team can ask about an account and get an answer that cites what was saved.

What it does

Account knowledge is spread over inboxes, call notes and people’s heads, and each salesperson’s AI tool knows none of it. In one engine for the team, every AI tool saves the customer, the people at it, each meeting, the decisions made and why, and the open tasks with an owner and a due date. The next person, or the next AI tool, starts from all of it.

Set it up

  1. Make one engine for the sales team, with a purpose: accounts, contacts, calls, decisions and next steps, and what does not belong.
  2. Drop account plans and past proposals into Files.
  3. Each salesperson connects the AI tool they already use at Can read and save.
  4. Invite the team: managers as admin, the team as members, anyone who only reads as viewer. People are free on every plan.
  5. Use Ask for an account, Summaries for the week, and the Map for how it all links.

Partners can follow the step-by-step sales team memory playbook, which takes about an afternoon with the client.

Questions

Does Context Engine replace our CRM?

No. It is the memory your AI tools read and save to. Where the team uses a CRM or a call recorder, their own AI tool reaches it through its own connectors.

What does a salesperson see before a call?

Ask "what do we know about this account?" in the app or in their AI tool. In the app, the answer names the memories it came from, and the Map shows how people, customers and decisions link.

In the help