Conversation intelligence vendors: can you train on or license customer calls?

Why customer calls are not yours to license#

Customer calls are not a conversation intelligence vendor's to license because the vendor captures them as a processor for its customer. The customer decided to record its sales calls, chose which meetings to capture and controls the recordings, transcripts and emails under the contract.

Vendor terms usually say this plainly. Gong's customer terms, for example, define customer data to include data collected and processed by or for the customer using the services, and state that the agreement gives Gong no right, title or interest in that customer data. A vendor in that position cannot grant an outside developer rights it does not hold.

Recording consent is narrower than it looks#

Recording consent on a sales call covers the recording, for the purposes the customer disclosed, and little else. The prospect on the other end heard a notice from your customer, not from you, and depending on where each participant was, an all-party consent rule may apply to the recording itself.

Licensing those calls to an AI developer is a new use by a new party. Even where a notice mentioned quality or training purposes, the phrase is usually read as training the customer's staff, not training outside models. Voice raises its own issues, since some state laws may treat voiceprints as biometric identifiers. Treat this as general information rather than legal advice; consent rules and contracts are assessed case by case with counsel.

Can you train your own product models on calls?#

Training your own product models on customer calls is possible only where the customer contract grants that right, and many enterprise buyers now ask for no-training clauses during security review. The same question then passes to your sub-processors, including any model provider that sees transcripts.

Public reaction shows why the wording matters. On August 7, 2023, after backlash over earlier changes to its terms, Zoom amended its terms to say that customers' audio, video and chat content would not be used to train its AI models unless customers consented, and its current terms say it does not use communications-like customer content to train its own or third-party AI models. Sales tech buyers read vendor terms with that episode in mind.

If you do train on customer content, limit it to customers who opted in, keep training sets traceable to each customer, and make them follow your retention schedule. Gong's published standard, for instance, keeps emails, calls and transcripts for three years or for as long as the company remains a customer, whichever is shorter, and a training copy that outlives that rule becomes the weak point.

Contract terms to check in your customer agreements#

Customer agreements decide how far a conversation intelligence vendor can go with call data, and the relevant terms are spread across the master agreement, the DPA and the order form. Read them together, because an order form for a large customer often narrows the standard terms.

What a conversation intelligence vendor can license#

A conversation intelligence vendor can license the records it created itself, not the records it captured for customers. The table sorts the usual record types.

Your own sales calls are a different case#

Your own recorded sales calls are a different case because your company recorded them as a party to the conversation. Discovery calls, demos and renewal conversations linked to CRM outcomes are the kind of record that teams building AI sales agents look for.

They still need work. The prospects consented to recording under your notice, which may not reach licensing, so sort the archive into calls to include, calls to transform through transcript de-identification, and calls to exclude.

• 1Confirm what each recording notice and meeting invitation said.
• 2Map where participants were located, to identify consent rules that may apply.
• 3Prefer transcripts over audio, with names, companies and figures removed.
• 4Exclude calls where a prospect screen-shared its own customer data, health or financial details.
• 5Link the remaining transcripts to deal stage and outcome from the CRM.

Illustrative: a sales engagement vendor separates two archives#

Illustrative: a fictional sales engagement platform records and transcribes calls for its customers and also runs its own sales team on the product. The CEO asks whether either archive could be licensed.

Counsel's review places every customer workspace out of scope: the contracts limit use to providing the service, and the calls were recorded under customers' notices. The vendor's own workspace is reviewed separately. Calls with a clear notice and participants in locations where one-party consent applied are transcribed, de-identified and linked to deal outcomes; the rest are excluded.

The vendor also reviews engineering history and support tickets. The final scope covers the vendor's own records only, documented so the company can answer any customer who asks whether its calls were involved.

How SourceX approaches call data#

SourceX treats call recordings as a record type with a high privacy burden, which lowers net value in the SourceX Enterprise Data Value Framework. In the SourceX five-step transaction, the Rights step separates customer workspaces from the vendor's own records before anything moves, and Preparation removes personal and confidential details from transcripts. The SourceX Evidence Packet records the consent basis, permitted use and release authorization for each package the vendor approves.