​

Salesforce implementations usually need stronger field governance and ownership mapping than simpler CRM stacks.

​

Prerequisites

• Salesforce admin access with API permissions.
• Approved object strategy (Lead vs Contact vs Opportunity activity).
• Field-level mapping spec signed off by CRM owner.

​

Setup workflow

1. Connect Salesforce using an integration user.
2. Select target objects and required field mappings.
3. Map call outcomes to controlled picklist values.
4. Configure activity/task creation for actionable outcomes.
5. Run supervised test set and validate record updates.

​

Mapping recommendations

• Always store Callaro call_id and voice_session_id in Salesforce activity payload.
• Keep one canonical outcome field for reporting.
• Use separate fields for AI summary and next-best action.

​

Validation checklist

• Updates land on expected object types.
• No duplicate activities are created during retry scenarios.
• Ownership and assignment rules continue to work after integration.

​

Known limits

• Field-level security can silently block writes.
• Record-level automation may modify mapped values post-write.
• Multi-object mapping increases QA and support complexity.