Chorus by ZoomInfo

The removal test leaves something saleable and it is emphatically not what is sold. Strip the model layer and a customer retains a call and meeting recorder with storage, a searchable archive and a two way sync of contacts and communications into their record system, which was roughly the 2015 product.

What disappears is everything the page actually sells: transcription, topic and competitor detection, objection identification, engagement analytics, deal momentum scoring, coaching signals derived from winning behaviours, and aggregation of customer language across a whole book of business into market intelligence.

The vendor's own framing rests on the inference rather than the capture, describing the product as backed by fourteen technology patents leveraging proprietary machine learning, which is a claim about models rather than about recording infrastructure.

This sits alongside the other established conversation intelligence records in this index rather than with the model native startups above them, because the capture layer genuinely predates the intelligence layer and remains a real product underneath it. Ask which analysis capabilities are the vendor's own models and which are licensed, and what remains available if an upstream speech provider is unavailable.

Oversight of people is documented properly and oversight of the analysis is not addressed at all. The published implementation guide is a real administrative document rather than a marketing page: it names the role types, describes hierarchies, explains that administrators hold global settings and complete visibility into all recordings, notes that some settings cannot be changed, and covers how mail and calendar synchronisation is controlled per user.

It also gives an administrator a route to narrow the product's reach, with access restrictable to a named security group and custom role definitions carrying only the necessary consent permissions, while warning that a restriction may take up to an hour to take effect. That is more administrative candour than this category usually offers. The gap is the automated layer.

Scoring of calls, identification of winning behaviours, deal momentum signals and competitor detection all run over conversations without any published account of how a customer inspects, tunes, overrides or disables them, what a score means, or what happens when the system misreads a call. For a product whose output feeds coaching decisions about named employees and momentum judgements about live deals, that is the control a buyer most needs described. Ask how call scoring and deal momentum signals can be inspected, tuned or switched off, and what recourse exists when a call is misclassified.

A patent count standing where a model description should be. The product surface says the platform is backed by fourteen technology patents leveraging proprietary machine learning, and that is the whole of the disclosure: no model, family, version or provider is named for transcription, topic detection, objection identification, sentiment or deal scoring, and no accuracy, word error rate or evaluation figure appears for any of them.

Transcription accuracy in particular is the foundation everything else stands on, since a coaching signal derived from a misheard sentence is wrong in a way nobody can see, and no figure for it is published. Language coverage is not stated either.

Recorded as a retrieval limit rather than an absence: the parent operates a responsible artificial intelligence section within its trust centre which was not retrieved on this pass, so a governance or model statement may exist there, and none of it is reachable from the product page a buyer would actually read. The parent separately publishes a page describing its own approach to artificial intelligence for machine readers. Ask for transcription accuracy with the measurement basis, the languages supported, and which models perform the scoring.

One checkable claim, several uncheckable ones, and a body of evidence that has not been refreshed in years. The checkable one is specific and worth crediting: fourteen technology patents, a count a buyer can verify against a public register, which is a rarer form of evidence than the usual percentage.

Customer evidence is attributed rather than anonymous, with a named revenue enablement supervisor quoted by employer and three marketplace reviews reproduced in full with reviewer names, titles and links to the originals, which lets a reader check the source. Marketplace award badges cover three distinct segments.

Against that, the headline on the product page claims this is the fastest growing product of its kind in existence, with no measure, period or comparator, and the vendor has left that claim in place while retiring the standalone brand it was written for.

At platform level the supporting material is materially stale: the pricing page answers a question about value by citing marketplace rankings from the autumn of 2020 and three customer outcomes including a claimed nineteen hundred percent revenue increase, none with a stated method. The same page states the customer count twice and differently, as more than thirty thousand in one answer and thirty five thousand or more in the banner above it. Ask for the method behind the growth claim, and which of the customer outcome figures were measured rather than reported.

The axis applies in a narrow form because this product analyses conversations rather than initiating them, and the scope is stated here so a reader is not left assuming a gap where the obligation does not fall. There is no sequencer, dialer campaign or outbound delivery to prospects in this product, so consent capture and suppression for outbound messaging have little to attach to, and the obligations that do bite on the recorded call are recording and monitoring law, addressed on the disclosure row rather than here.

One connected capability does reach outward and is worth recording: configuring the product through tenant level mail settings grants it the ability to read and send mail for users across the tenant, so the platform holds a sending capability even though sending campaigns is not its purpose. Nothing published describes what it sends, under whose authority, or what controls apply.

The parent's wider platform includes outbound engagement products sold separately, and a buyer should not read this product's narrow scope as covering those. Ask what mail the product sends under the tenant grant, and what limits an administrator can place on that sending capability.

A privacy apparatus built at parent scale, with certification behind it and one visible hole where this product sits. The parent holds the international privacy information management certification alongside its security certifications, displays two independent privacy seals whose badges link to live third party validation pages rather than sitting as static images, and belongs to three privacy policy bodies including one at gold member level.

Individual rights are operationalised rather than described: a dedicated privacy request portal runs separate routes for verifying and correcting company data and profile data, a standing do not sell or share control is published, and a trust centre section is devoted to individual privacy. The parent also registers publicly as a data broker under Texas law and says so on its own trust page, which is a disclosure most companies in that position leave to a state register.

The hole is this product's own material. Everything above is built around the contact database, and none of it addresses the recording corpus, which is where the sensitive data in this particular product lives: audio and transcripts of customers and prospects who never contracted with anyone and whose words are analysed. No processing addendum, sub processor list or retention schedule specific to recordings was reached on any route. Ask for the retention period applied to recordings and transcripts, and for the sub processor list covering conversation content.

Two data sources with very different provenance questions, and only one of them is addressed. The conversations are the customer's own, captured under the customer's authority, so provenance there is straightforward and the interesting question is consent rather than licence. The second source is the connected intelligence layer, which brings the parent's contact and company database into the conversation view so that a representative sees relationship history alongside the call.

That database is the contested asset: it is assembled about individuals who did not supply it, and the parent's position on it is disclosed at least in outline, through a data transparency page, a published community code, verification and correction routes for both people and companies, and registration as a data broker under Texas law. None of those were retrieved on this pass and the grade does not rest on their contents.

What is absent from this product's own surface is the join between the two: nothing states what licence or basis permits contact records to be merged into a conversation record, what a customer may do with the combined artefact, or what happens to the enrichment when a subscription to the underlying data ends. Ask under what terms contact data is joined to conversation records, and whether that enrichment persists if the data subscription lapses.

Official routes throughout, documented at the level an administrator needs, with no evasion anywhere in the design. Capture happens through the meeting and communication platforms' own supported integrations, and the implementation guide describes the tenant level consent flows for both major productivity suites explicitly, including which permissions are granted, how to restrict them to a security group, and how to build a custom role carrying only the consent permissions required.

That is a vendor documenting the permission model of somebody else's platform accurately rather than working around it, and it is the opposite of the pattern this band usually records. Nothing scrapes, no unofficial client is used, and the parent operates its own infrastructure rather than reselling another application layer. Two things hold it below the top band.

The default tenant grant is broad, extending to reading calendar events for every user in the tenant and to reading and sending mail, so the product's permission footprint exceeds the recording function it is bought for unless an administrator narrows it. And no conformance position is stated toward the meeting platforms whose interfaces the product depends on, nor any account of what happens if those interfaces change. Ask what the product does if a meeting platform restricts recording access, and what the minimum viable permission set is.

The parent has built a governance surface and this product's page does not connect to it. A responsible artificial intelligence section exists as one of six areas within the trust centre, which places model governance alongside privacy and security as a standing topic rather than an afterthought, and the parent holds certifications spanning privacy and cloud controls. That section was not retrieved on this pass and this grade does not rest on its contents.

What can be established is what a buyer of this product reads, and none of it addresses stewardship of the material at stake. The corpus here is recorded speech of customers and prospects, retained and analysed at scale, and nothing on the product surface states whether recordings or transcripts train or tune any model, whether one customer's conversations inform analysis served to another, what retention applies to derived scores and summaries as distinct from the audio, or which providers process the content.

The market intelligence capability sharpens the question rather than softening it, since aggregating the voice of the customer across a book of business is by construction a use of conversation content beyond the single call it came from. Ask whether recordings or transcripts train any model, whether analysis crosses customer boundaries, and what retention applies to derived summaries separately from the audio.

This vendor answers the question the two nearest records in this index leave open, and it answers it in the wrong place. A published marketplace listing for the product's scheduling companion describes a built in compliance capture flow: meeting links route attendees to a landing page where explicit consent is captured before the meeting, offered for customers operating under European data protection law or whose own customers are sensitive to being recorded.

Consent captured before capture begins is precisely what a larger competitor in this category was held down for not publishing, and what a smaller one only partially answers by making its recorder visible in the participant list. Three things keep this in the middle band rather than above it.

The description sits on a third party marketplace listing last updated in March 2023, not on the vendor's own product pages, which say nothing about consent, recording notification or jurisdiction anywhere across five feature pages. It is a scheduling flow, so it covers meetings booked through that route and nothing states what happens on calls that are not.

And nothing describes what a participant hears or sees on a call that was not scheduled that way, whether the recorder announces itself, or how the product behaves where every party must agree. The European transparency obligations in force since August 2026 go unmentioned. Ask what a participant is told on a call not booked through the scheduler, and whether consent capture can be enforced rather than offered.

Deep, documented and unusually well supported for administrators. Capture integrates with the major meeting and communication platforms, mail and calendar connect through tenant level administrative consent on both leading productivity suites, and contacts and communications sync bidirectionally into the customer record system, which is the connection this category lives or dies on.

A published technical documentation library carries an implementation guide as an open file, a marketplace listing exists for the scheduling companion on a major productivity marketplace, and the parent runs its own partner marketplace, a cloud partner programme and an enterprise interface for delivering data into other systems.

The parent has also shipped a connector for assistant tooling and a route into a named external assistant, both as platform capabilities rather than as features of this product, and a buyer should read them that way. Held below the top band because the documentation is oriented to provisioning rather than to building: no interface reference specific to this product, no webhook description and no developer portal for it was located, so a customer wanting conversation data in a system that is not on the supported list has no visible route. Ask whether a documented interface exists for conversation data, and what the supported connector list is for this product specifically.

Cloud only, with a certification that speaks to the architecture and nothing that answers the location question. The parent holds the international standard for cloud security controls, which is a meaningful signal that hosting arrangements have been examined against a recognised framework, and operates a public status page reporting platform availability.

Beyond that the specifics a residency obligation turns on are unstated on every surface reached: no hosting provider is named, no region is given, no tenancy or isolation model is described for the recording corpus, and no recovery time or recovery point objective appears. The question matters more here than for the parent's other products.

Recordings are voice data about identifiable individuals, many of them customers and prospects rather than employees of the buyer, and jurisdictions differ on both where such data may be held and how long. A European buyer recording European customers needs a location answer before signing and cannot obtain one from the published material. Ask which regions hold recordings and transcripts, whether regional storage is available, and what the recovery objectives are.

A substantial certification set, published openly, one step short of the depth the leading record in this category reaches. The trust centre displays the international information security standard, its cloud security controls extension, the privacy information management standard at its 2019 revision, a service organisation control attestation, and a listing in the cloud security registry, alongside two independent privacy seals whose badges link out to live validation pages so a reader can confirm they are current rather than taking an image on trust.

Four industry body memberships sit beside them. The trust centre is structured rather than decorative, with separate sections for individual privacy, company privacy practice, security, responsible artificial intelligence, customer resources and terms, and a public status page operates. Three things hold it below the top band. No audit period, auditor name or downloadable report appears on the landing page, so the attestation is visible without being verifiable.

The cloud registry listing is at the self assessment level rather than the independently audited level above it, which is a distinction a reader could easily miss from the badge alone. And the badge captions are wrong on their face, describing the privacy management standard and the cloud controls standard both as information security management certifications, which are three different standards given one label. Ask for the current attestation with its period and auditor, and whether the report is available without a sales conversation.

The parent publishes a genuinely informative pricing page and this product is excluded from it. Six packages are enumerated across the sales and marketing lines with full feature lists and some real quantities, including credit allowances at seventy five and one hundred and fifty thousand, intent topic counts at twenty five, one hundred and unlimited, and stated campaign and account ceilings.

The consumption model is explained properly in the questions below: a credit is consumed on export of a profile, packages carry a predetermined monthly allowance, integrations carry a base cost plus a minimum bulk credit purchase, and one add on is priced on keyword volume and account universe. That is more mechanism than most vendors disclose and it makes the treatment of this product conspicuous. Chorus appears in none of the six packages.

It sits in a separate block below them headed as an embedded capability, with a one line description and a link, no feature list, no unit of pricing, no tier structure and no figure. A buyer therefore learns how the parent charges for everything except this. No figure appears on the product page either, and the only route is a demonstration request.

What third parties report is a per seat model with a three seat minimum in the low thousands of dollars annually, additional seats charged separately, multi year terms common, and consistent accounts of pressure to buy the wider platform alongside it, none of which converges tightly enough to record as a figure. Ask for the per seat rate, the seat minimum, the term, and whether the product can be bought without a wider platform subscription.

Recorded as gated and unaddressed rather than as an established absence, because the contractual documents were not retrieved on this pass and the product surface says nothing. What accumulates here is among the more consequential archives a revenue team builds: every recorded customer and prospect conversation, its transcript, the scores and coaching history attached to it, and the relationship timeline synced against the record system.

Nothing on the product pages, the implementation guide or the pricing material describes an export route, a format, a post termination access window or a deletion timeline for any of it. The synced half offers partial relief that a buyer should not overstate, since contacts and communications pushed into the customer's own record system remain there, but the audio, the transcripts and the derived analysis are the asset and they sit on the vendor's side.

Recordings are also material a business may be obliged to retain or to delete on request from the person recorded, so the question is regulatory as well as commercial. The parent publishes a terms and policies section within its trust centre which was not reached. Ask what exports at termination and in what format, whether audio and transcripts are included alongside metadata, and what is deleted on closure and when.

The axis applies weakly to a product that analyses conversations rather than sending outreach, and the scope is stated so a reader does not mistake narrowness for a failing. No sequencer, dialer campaign or bulk sending capability forms part of this product, so warmup, authentication, bounce handling and complaint thresholds have nothing to attach to. Two connected facts stop this being simply out of scope.

Tenant level configuration grants the platform the ability to read and send mail for users across the organisation, so a sending capability exists even though outbound campaigning is not the purpose, and nothing published describes what is sent, at what volume, or under whose sending identity.

And the parent sells outbound engagement products separately whose sending discipline is a different question entirely, so a buyer evaluating the combination should not read this row as covering them. Ask what mail this product sends under the tenant grant and from which addresses, and whether that sending can be disabled while retaining recording and analysis.

The roles are defined precisely and the market around them is not. The implementation guide names the intended user types and what each sees, covering an administrator holding global settings and full recording visibility, a sales organisation leader viewing across multiple teams, a role tailored to development representative teams and their connection rates, and individual contributors on primary sales and account teams.

That is a clearer statement of who sits inside the product than most vendors manage. Marketplace recognition spans small business, mid market and enterprise segments, which suggests real breadth. What is missing is everything a buyer uses to place themselves.

No company size, revenue band, industry or geographic statement appears for this product, no language coverage is stated for transcription, which is the constraint that decides whether an international team can use it at all, and no minimum seat count is published.

The unresolved commercial question compounds it: multiple independent accounts report that the product is increasingly sold as part of the wider platform rather than alone, and the vendor's own pricing page reinforces that reading by placing it outside the six packages as an embedded capability. A buyer who does not already use the parent platform cannot establish from published material whether they are a target customer. Ask whether the product is sold to buyers with no wider platform subscription, and which languages transcription supports.