ConversationalIntelligenceSettings Metadata in SFDX

Architectural Overview#

Einstein Conversation Insights (ECI) processes voice calls (VoiceCall) and video meetings (VideoCall) to generate searchable transcripts, detect competitor or pricing objections, trigger automated coaching workflows, and power Agentforce / Einstein Generative AI call summaries.

The ConversationalIntelligenceSettings metadata type (ConversationalIntelligence.settings-meta.xml) controls the foundational org-wide switches for ECI. By managing ConversationalIntelligence.settings-meta.xml in SFDX, architects ensure that sandbox environments and production orgs have identical call processing pipelines enabled before deploying dependent ConvIntelligenceSignalRule definitions or call-triggered Flows.

SFDX Directory and File Suffix#

Key Metadata Fields#

ConversationalIntelligenceSettings provides boolean toggles for core ECI features, automatic CRM record linking, and generative insights.

Declarative XML Example#

Below is a production ConversationalIntelligence.settings-meta.xml configuration enabling Einstein Conversation Insights, automatic CRM record matching, speaker-attributed signals, and Opportunity page aggregation.

<?xml version="1.0" encoding="UTF-8"?>
<ConversationalIntelligenceSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <enableCallCoachingAutoMatching>true</enableCallCoachingAutoMatching>
    <enableCiAttributedSignals>true</enableCiAttributedSignals>
    <enableCiOpptyRecordPage>true</enableCiOpptyRecordPage>
    <enableConversationalIntelligence>true</enableConversationalIntelligence>
    <enableDynamicPlaybooks>true</enableDynamicPlaybooks>
    <enableUnifiedActivities>true</enableUnifiedActivities>
</ConversationalIntelligenceSettings>

package.xml Manifest#

Deploy ConversationalIntelligenceSettings before or alongside ConvIntelligenceSignalRule components:

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>ConversationalIntelligence</members>
        <name>Settings</name>
    </types>
    <types>
        <members>*</members>
        <name>ConvIntelligenceSignalRule</name>
    </types>
    <version>68.0</version>
</Package>

SFDX CLI Retrieval and Deployment#

Use Salesforce CLI to retrieve and deploy ConversationalIntelligenceSettings:

# Retrieve ConversationalIntelligenceSettings from the org
sf project retrieve start --metadata Settings:ConversationalIntelligence

# Deploy ConversationalIntelligenceSettings to a target org
sf project deploy start --metadata Settings:ConversationalIntelligence

Architect Best Practices and Gotchas#

• License & Permission Set Readiness: Enabling enableConversationalIntelligence at the org level requires active ECI or Sales/Service Cloud Einstein licenses (CallCoachingUser permission set license). Users will not see call players or insights until assigned the Conversation Insights for Sales or Conversation Insights for Service permission set.
• PII & Consent Governance: When enableCallCoachingAutoMatching is true, calls are automatically linked to matching Lead, Contact, and Opportunity records. Ensure your telephony/video provider respects regional two-party recording consent laws before pushing recordings into the ECI pipeline.

Frequently asked questions

What Salesforce feature is managed by ConversationalIntelligenceSettings?

ConversationalIntelligenceSettings controls Einstein Conversation Insights (ECI), which transcribes and analyzes Sales and Service voice and video calls to surface keyword mentions, coaching insights, and AI call summaries.

Where is ConversationalIntelligenceSettings stored in SFDX?

It is stored at force-app/main/default/settings/ConversationalIntelligence.settings-meta.xml and referenced in package.xml under Settings with member ConversationalIntelligence.

How does ConversationalIntelligenceSettings relate to ConvIntelligenceSignalRule?

ConversationalIntelligenceSettings turns on the org-wide Einstein Conversation Insights engine and record-matching options, while ConvIntelligenceSignalRule defines the specific keyword and competitor signal rules evaluated on transcripts.

Does enabling enableConversationalIntelligence automatically connect CTI vendors?

No. Enabling ECI turns on the processing pipeline, but you must still authenticate recording providers (such as Service Cloud Voice, Zoom, Gong, or RingCentral) and assign ECI permission sets to users.