The bulk of the work in a Conversation Insights rollout is upstream of the Salesforce setup: confirming licensing, choosing recording sources, and addressing consent. The Salesforce-side configuration is straightforward once those are settled.
- Confirm licensing and edition
Conversation Insights requires its own license and is included in some Sales Cloud editions. Confirm before scoping the rollout to avoid mid-project surprises.
- Decide the recording source
Pick the source the team will record from (Zoom, Microsoft Teams, Sales Dialer, partner). The choice constrains which calls flow into the product and what consent prompts already exist.
- Address consent and privacy obligations
Work with Legal to confirm jurisdiction-specific recording obligations. Configure the consent prompts in the recording source. Document the compliance posture before turning recording on.
- Connect the source to Salesforce
Setup, Einstein Conversation Insights, configure the integration. Test with a sample call. Confirm transcript, insights, and the link to the related Account or Opportunity all populate.
- Train managers on the coaching view
The product's value comes from the coaching loop. Run a workshop with sales managers on how to find calls worth reviewing, leave coaching comments, and track rep follow-through.
Zoom, Microsoft Teams, Sales Dialer, and several telephony partners. Each has its own connection setup.
Built-in: competitor, pricing, product. Custom categories supported via keyword and phrase lists.
Built-in. Promotes detected items to Tasks with one click; configurable on the Voice Call page layout.
Manager-facing surface for finding calls worth reviewing and tracking coaching follow-through.
Standard sharing rules on the Voice Call object. Often configured to give managers visibility into their team's calls.
- Consent rules vary by jurisdiction and recording medium. Failure to address consent up front is the most common rollout blocker.
- The integration setup is often the longest step. Telephony plumbing, OAuth approvals, and recording retention policies live outside Salesforce.
- Action item detection is good but not perfect. Some rep promises get missed; some non-commitments get flagged. Treat detected items as drafts, not certainties.
- Competitor mention coverage depends on the maintained competitor list. Keep the list current; new competitors are invisible until added.
- Storage costs grow with recording volume. Long-term retention policies should be set deliberately, not by accident.