| Ingests from your CRM | Surfaces inside your CRM | |
|---|---|---|
| What it does | Reads accounts, contacts, activity to build the graph | Puts the warm path on the record the rep is already looking at |
| Rep behaviour | Open a second tab, remember to check | Sees it without deciding to |
| Failure mode | Used in week one, forgotten by week six | None, if the data is good |
Almost every vendor does the first. Fewer do the second, and the demo rarely makes the difference obvious, because in a demo someone is already looking at the tool.
Documented integrations: Salesforce, HubSpot, Google Workspace, Office 365, Gong, Outreach, Slack and Teams.
CRM connections use OAuth rather than credentials. The Salesforce integration requests the standard id, profile, email, address, phone and api scopes; Google Workspace connects read-only through domain-wide delegation, with no capability to write or modify anything.
There is also a Model Context Protocol server, so paths can be pulled directly from an AI assistant without opening any UI at all.
Relationship intelligence competes for attention with every other tab a rep has open. A warm path that requires someone to remember to go looking for it is, in practice, a warm path nobody finds.
That is why the integration question is really an adoption question, and why it should be answered on your CRM with your records in front of you - not in a slide.