Connect CRM and support tools | Docs

Your CRM knows the stage of a deal. Your support tool knows what customers complained about. Fivo adds what was actually said on calls and in email, and links all of it to the right account so you can ask about a customer rather than about a tool.

CRM

Fivo connects to HubSpot, Pipedrive, Salesforce, Attio, Close and Zoho CRM.

Your CRM stays your system of record. Fivo does not replace it. It reads companies, contacts, deals and notes so that the graph can place every call, email and ticket on the right account, and so that your answers include CRM facts next to conversational ones.

What this gives you:

Account briefs that combine CRM data with calls and email: the buying committee, open objections, promises made and the last thing the buyer said. See Build a 360º brief of an account.
Pipeline questions in plain language: which deals mentioned a competitor this month, with the quote behind each one.
Signals: a new decision-maker, a budget freeze or a long silence surface on the account timeline.

Attio does not support asking for "what changed since", so Fivo re-reads the account on each pass. This is handled for you, but it is why a very large Attio workspace syncs more slowly.

Support

Fivo connects to Intercom and Zendesk.

Tickets become sources for customer requests and complaints. Each ticket's lifecycle (opened, replied, resolved) is kept, so the graph knows not only what was asked but what happened to it. Combined with Linear or Jira and GitHub, a request can be followed from the ticket to the feature that shipped. See Connect code and project tools.

Intercom and Zendesk cannot tell Fivo who on your team can read a ticket. With organization scope their material is visible to the organization owner and to the agents who took part in each conversation.

Billing: Stripe

Fivo connects to Stripe with a restricted, read-only key that you create in Stripe. Fivo uses it to enrich companies and people with subscription facts: who is a paying customer, what plan they are on, when they renewed.

Stripe cannot report "what changed since" either, so each pass re-reads the account. A change without a new date (a price edit, for instance) waits for the next dated event before it is applied.

Scope and visibility

CRM, support and billing tools are usually company sources, so they are normally connected with organization scope by the organization owner. Whatever the scope, each fact carries its source. For CRMs, visibility follows ownership and membership as the connector reads them: material is readable by the people who are active users or owners in the CRM, matched by email to members of your organization. Per-record sharing rules, team partitions and territories of the CRM are not evaluated, so a user hidden from a record by those rules is still counted as a reader. Keep this in mind when choosing scope. See Permissions: what your Brain can see.

Following up in the original tool

Every fact that comes from a connector keeps a link to its origin. When your AI assistant answers "the CFO raised an objection on 18 Sep", it can give you the HubSpot record or the Zendesk ticket to open, and act there with its own tools if it has them. Reading into the Brain never writes anything to your systems. The only writes are the ones a user triggers by sharing a meeting report or tasks to a contact or deal from Fivo, if that integration offers it.

Suggested setup for a sales team

Connect your calendar so your sales calls reach Fivo as reports, then your email, then one CRM. From the first few calls, Fivo starts linking accounts. Add Intercom or Zendesk when you want customer success to see what sales promised.

Step-by-step guides

Each integration has its own guide with permissions, steps and troubleshooting.

CRM:

Support:

Billing:

Connect Stripe

integrations
crm
hubspot
support