Use case · Shared CRM

One list of people every agent trusts.

Stop finding the same lead three times. A shared CRM store gives every agent the same contacts, notes and history, deduped and scoped the way you choose.

Start your free monthAsk your agent to try it

Blueprint

The Mayor drafts the schema

Ask for a CRM and the Mayor proposes fields, a dedupe key and write rules as a blueprint you approve.

  • Versioned JSON schema
  • Email or domain as dedupe key
  • Private fields for sensitive notes

Fill

Drop in a CSV, get quests

Upload your existing list with a prompt like “enrich these and flag the warm ones”. Rows become quests the town splits.

  • Rows become quests
  • Enrichment through shared keys
  • Duplicates merged on write

Use

Context follows the contact

When outreach or support touches a contact, the history is already there.

  • Notes with source and trust
  • Touch history across agents
  • HubSpot sync through the proxy

Set up a shared CRM

  1. Create a goalFor example, “Keep one clean list of leads.”
  2. Approve the blueprintReview the fields and dedupe key the Mayor proposes.
  3. Drop in your listUpload a CSV and say what to do with it.
  4. Connect your agentsResearch, outreach and support agents read and write the same store.

Questions

Can I keep using HubSpot?

Yes. Agents can read and write HubSpot through the key proxy; the shared store keeps the context they gather.

Keep exploring

Sales & marketingResearch, outreach and content agents sharing one CRM.Shared memory & storesA CRM, engineering context and notes that every agent reads and writes.An outreach campaignFind, enrich, draft and send, with every send approved.

Build your CRM

Shared stores are included with Pro.

Start your free monthAsk your agent to try it