Conversational Intelligence Migration FAQs

What is Vendor Transcription Processing?

Vendor Transcript Processing (also known as Fast Vendor Transcript or FVT), is the updated method for quickly making video transcriptions from Google Meet, Microsoft Teams, and Zoom available in Salesforce immediately following the conclusion of a meeting.

How do I set up Vendor Transcript Processing?

Vendor Transcript Processing is turned on by default for orgs when ECI data is migrated to Core. The feature can’t be turned off after it’s enabled. 

What is the storage policy for video and voice calls?

What are the storage/data retention policy and post ECI to Core migration?

By default, customers get 10 GB of storage on Core. This is the storage across all entities – not just for ECI-related entities. For new ECI customers, ECI data is stored on Core.

Any existing ECI data will be migrated over to Core at no additional storage cost to customers. Post migration, any new ECI data is counted against the Core storage.

What is being introduced?

For storage, turn on Storage Quota for all ECI entities. On the Setup, go to the Storage Usage page. Expose all the ECI entities we’re storing in Core. This is a read-only view where we show how much storage each table is consuming. Customers can see how much storage ECI-related data is consuming directly from Setup → Storage Usage.

Where can customers see ECI storage usage?

In Setup → Storage Usage. All ECI entities stored in Core appear in the list of objects with the amount of storage each entity is consuming.

What is the data retention and purge policy?

The general purge policy of Core storage is two years. Admins can define “Purge Policies” per entity level, if necessary. 

Do we expect customers to run out of Core storage because of ECI transcripts?

No, this is unlikely. ECI transcript storage is highly optimized. While a typical 30-minute call produces about 170 KB of data, it only counts as 2 KB toward your storage limit. This is because the system charges based on the number of records (rows) rather than the actual file size.