> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dovetail.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Revenue intelligence
> How sales and customer success teams use Dovetail to analyze calls, enrich contacts from a CRM, and rank what matters by revenue.
Sales and customer success calls contain detailed information about why deals stall and why accounts churn, but that information is hard to use while it sits in individual recordings. This page covers importing those calls into Dovetail and analyzing them together.
There are four steps: import the calls, connect your CRM so revenue context is attached to each contact, use Channels to rank what the calls raise, and configure agents for the recurring reporting. The CRM step is the one most often skipped. Without it, feedback is ranked by how frequently something is mentioned. With it, ranking reflects the revenue represented by the accounts raising each idea.
***
## Get the calls in
[Gong](/integrations/gong) feeds two workflows from one connection. Stream transcripts into a channel when you have more calls than anyone can read. Import them into a [project](/help/projects) when you want to play back, highlight, and tag a focused set, like a win/loss study or a churn post-mortem.
The two workflows import different things. Channels takes the transcript, Gong’s call brief, and metadata — not the media. Projects takes the recording itself and transcribes it, so you can play it back.
[Zoom](/integrations/zoom) cloud recordings import into a project. For Teams calls, connect [Outlook Calendar with Teams as the video source](/integrations/microsoft-teams#set-up-to-import-teams-recordings) so recorded meetings land in a project without anyone uploading anything. Reps continue running calls the way they do now.
***
## Connect your CRM
Dovetail knows what was said and who said it. It doesn’t know that the person saying it runs a \$400k account and renews in six weeks. That lives in your CRM.
Map Salesforce contact and account fields onto your Dovetail contacts.
Map HubSpot contact and associated company properties onto your Dovetail contacts.
Both match records on an email field you nominate, and both pull one way — Dovetail never writes back, so your CRM records are unchanged.
A workspace can connect only one CRM enrichment source at a time. Salesforce and HubSpot are mutually exclusive, so decide which is your source of truth for account data before you start.
Map only the fields you’ll actually rank, filter, or segment by: ARR, plan tier, account, industry, renewal date. Create them in your [contacts database](/help/contacts) first, because you can’t add Dovetail fields during mapping. Turn on daily syncing — an ARR figure from nine months ago mis-ranks everything downstream.
[Contact automation](/help/contact-automation-settings) is a separate feature that builds contact records from your call transcripts. It creates the person, CRM enrichment attaches the revenue. Run both.
***
## Rank ideas by revenue
[Channels 2.0](/help/channels) groups incoming feedback into Ideas, ranked by your business context, how often something comes up, how many accounts are affected, and how much ARR sits behind it. Every idea rolls up its data points, sources, contacts, and total ARR.
That roll-up is the whole point of the CRM step. It turns “12 people mentioned SSO” into “12 people across \$1.8M of ARR mentioned SSO”, which is an argument product can act on. You can open the Evidence behind an idea to see which accounts are counted in it.
Roll-ups are driven by your contact identifiers, configured in `Settings` → `Contact settings` → `Contact identifiers`. Missing ARR on your ideas usually traces back here.
Filter the feed by ARR, contacts, or intent, sort by custom roll-ups like plan or industry, and save the combination as a view so each account team returns to its own slice instead of asking you to pull it.
***
## Ask about specific deals
[Chat](/help/chat) answers the question you have right now, with citations back to the calls it drew from, so an answer used in a deal review links to the recording it came from.
* “What objections came up most in the deals we lost last quarter?”
* “What did we promise this account during the sales cycle?”
* “What are accounts renewing in the next 90 days complaining about?”
* “Which competitor comes up most in stalled deals?”
Ask the same questions from Slack or Teams, without opening Dovetail.
***
## Automate the rest
[Agents](/help/agents) run on a schedule, on a Dovetail event, or from a webhook fired by a Salesforce Flow, and can read and write connected tools during a run. Deal briefs, closed-lost debriefs, renewal risk scans, and competitive digests are all recurring work an agent can own.
Because an agent writes to the tools your team already uses, its output arrives where the work happens: a digest posted to a Slack channel, a direct message to the account owner when renewal risk appears, or a Salesforce field updated with competitive context.
Lead briefings, objection loaders, deal debriefs, stalled deal analysis.
Renewal risk, churn digests, health reviews, expansion signals.
***
## Close the loop
Send an idea to Jira or Linear and the ticket stays linked to the feedback that prompted it, so you can trace a deal-blocking objection through to the change that shipped. When the idea moves to Resolved, use `Notify customers` to draft an update to the contacts whose feedback drove it.
Set up end to end, the workflow produces three things you can bring to a forecast review or a QBR: a ranked view of what is costing revenue with the accounts named, answers that link to the calls they came from, and briefs that reach reps on schedule without anyone writing them.