Chorus
Turn Chorus calls into product and engineering evidence with Four/Four
The Four/Four Chorus integration imports your Chorus call recordings and transcripts into Four/Four, including historical calls. Four/Four then extracts pains, needs and feature requests, groups them into themes alongside tickets, chats, emails and any other unstructured data inputs, giving product, CS, engineering and AI assistants the full evidence. Chorus stays in place for sales.
What Chorus does well, and where teams hit limits
Chorus by ZoomInfo is a mature conversation intelligence tool for revenue teams. It records and transcribes calls and meetings, scores reps with scorecards, builds coaching libraries with Smart Playlists, and tracks deal momentum in the CRM. Because it sits inside ZoomInfo, every call participant is matched to ZoomInfo contact and company data. For sales coaching and deal review, it is a strong choice.
The limits appear when the rest of the company wants the same evidence. Chorus is organised around reps, deals and accounts, so product managers struggle to see themes across hundreds of customers. Its trackers find moments that match terms set in advance, rather than discovering what customers ask for in their own words. Chorus doesn't take in support tickets or chat. ZoomInfo's MCP server answers questions about Chorus calls one account, contact or call at a time, drawing on the five most recent transcripts. And nothing in Chorus links customer evidence to the product backlog or to code.
What Four/Four adds to Chorus
Themes across every Chorus call, ticket and chat
Four/Four shows what customers ask for across all your conversations, not one deal at a time. Every imported Chorus call is broken into structured insights (jobs, pains, needs, proposed solutions and feature requests). Topic sets group those insights with evidence from Zendesk, Intercom, ServiceNow and other meetings, so you can compare themes by segment, deal stage or time period.
Evidence for product decisions
Four/Four puts the customer quotes behind each idea in front of product managers. Issues built from insights flow into product management tools like Jira Product Discovery and Productboard, with links back to the Chorus calls where customers raised them.
Answers across every customer for Claude and ChatGPT
Four/Four's MCP server answers the questions ZoomInfo's MCP isn't built for. ZoomInfo's Conversation Intelligence tool works on one account, contact or call per request, reads up to the five most recent transcripts, and ZoomInfo's own docs say topic searches such as "every call where SOC 2 came up" aren't available yet. Four/Four's MCP returns extracted insights, topic counts, CRM accounts and opportunities, product issues, and Chorus transcripts on request, across every customer and source, each linked to its origin. Assistants can also label conversations and start new topic analyses.
Reading insights instead of raw transcripts also keeps AI costs down. In a test on Four/Four's own data, answering "What are the top pains for people with a Product persona?" from 326 raw transcripts took about 2.86 million tokens. Answering it from Four/Four's extracted insights took about 194,000, 14.8 times fewer, with the same answer. Read the full test.
Checking shipped code against customer need
Four/Four closes the loop from voice of customer to code. Because the evidence sits beside the issue, engineers can review what they build against what customers said in Chorus calls, not only against the ticket.
Access for every team, without extra Chorus or ZoomInfo seats
Four/Four prices on content processed, with no per-seat fees, so product, CS, marketing and engineering can all use Chorus evidence without each needing a Chorus licence.
How it works
Connecting Chorus takes one API token from a Chorus admin.
- Start a Four/Four trial or sign in . About 2 minutes.
- Open Connections and choose Chorus. About 1 minute.
- Add a Chorus API token. A Chorus admin generates it under Settings > Personal Settings > API Access. About 2 minutes.
- Review your first insights and topics once the import has processed.
- Optional, connect Claude or ChatGPT to Four/Four's MCP server to query Chorus evidence from your AI assistant.
Use cases by team
| Team | The question they ask | What Four/Four gives them from Chorus calls |
|---|---|---|
| Product | "Which feature requests come up most, and from which industries?" | Feature requests and pains grouped into topics, with counts by industry and links to the calls, sent to Jira Product Discovery or Productboard |
| Customer success | "Which accounts are raising churn risks, and why?" | Complaints and unmet needs per account, combined with support tickets and chats, tracked over time in Monitor dashboards |
| Engineering | "Does what we're building match what customers asked for?" | The customer evidence behind each issue, so code can be reviewed against the need, not only the ticket |
| Marketing | "What words do buyers use for their problem?" | Real customer language and objections for messaging, content and outbound personalisation |
| Leadership | "What are customers telling us this quarter?" | Trends across every conversation source, plus an AI analyst that answers questions with linked evidence |
Example output
A Four/Four topic called "Usage reporting for admins" built from 28 Chorus calls and 37 Zendesk tickets over the last 90 days. It shows the number of accounts raising it, the share from enterprise customers, the average value score, three linked customer quotes, and the matching Jira Product Discovery idea.
FAQ
Do I need to replace Chorus to use Four/Four?
No. Four/Four works on top of Chorus. Your sales team keeps recording, coaching and reviewing deals in Chorus, while Four/Four imports the calls and makes the evidence available to product, CS, engineering and marketing. Nothing changes in your Chorus or ZoomInfo workspace.
Does the integration work with historical Chorus calls?
Yes. Four/Four can analyse historical Chorus call recordings as well as new ones, so you can see long-term patterns and trends from the first day.
What permissions does the Chorus integration need?
A Chorus admin generates an API token and adds it in Four/Four's Settings > Connections page. ZoomInfo may limit API access to some Chorus packages, so check with your ZoomInfo account team if you can't see API Access. Inside Four/Four, access is controlled by role-gated permissions and SSO, and PII and PCI can be redacted.
How is this different from ZoomInfo's MCP server?
ZoomInfo's MCP server includes a Conversation Intelligence tool that writes a synthesised answer about one account, contact or call, from up to five recent transcripts and five emails. It costs AI credits per question, around 10 for most. With Chorus connected to Four/Four, Claude or ChatGPT can query insights, topics and CRM records across every customer and source, and retrieve full transcripts, each linked back to the original call.
Can I combine Chorus calls with support tickets?
Yes. Four/Four connects to Zendesk, Intercom, ServiceNow, Pylon, Genesys Cloud and NiCE CXone alongside Chorus. Insights from every source share one set of topics, so a request raised on a sales call and in a ticket shows as one theme.
How much does it cost?
The Chorus integration is part of Four/Four's plans, which charge for content processed rather than seats.
What happens to my Chorus history if we leave ZoomInfo?
Calls already imported into Four/Four stay in Four/Four, with their insights and topics, so the analysis keeps its history if you move to a different call recorder later. Four/Four also imports from Gong, Fireflies, Avoma, Jiminny, Zoom, Teams and its own notetaker.