Skip to main content

​
Overview

When Cura syncs CRM data, it can expose account context to agents and AI workflows. Managing that data correctly helps avoid stale details, duplicate context, and conflicting responses.

​
How CRM-synced context works

After CRM connection, Cura periodically syncs eligible records and mapped fields. Synced values can include:
  • Contact and company profile data
  • Owner and lifecycle state
  • CRM-specific custom fields you map
Synced CRM fields are integration-managed. Direct edits to integration-managed values may be overwritten on the next sync.

​
Best practice: separate synced vs custom context

Use two layers of information:
  1. CRM-synced context for canonical system-of-record fields
  2. Custom Cura knowledge for operational guidance, exceptions, and policy notes
This split keeps CRM updates clean while preserving important team-specific instructions.

​
Avoiding duplicates and conflicts

Conflicts usually appear when the same fact exists in multiple places with different values. To reduce conflicts:
  1. Define a source of truth for each field.
  2. Keep naming consistent across CRM and Cura custom fields.
  3. Remove duplicate custom notes when that data is now CRM-synced.
  4. Review sync logs periodically for repeated overwrite patterns.

​
Change management

When updating CRM mappings:
  • Test in a limited segment first.
  • Confirm AI responses still reference the intended fields.
  • Document which team owns each critical mapping.

​
Operational checklist

  • Review mapping health weekly.
  • Audit unresolved sync errors.
  • Reconfirm credentials and scopes after CRM admin changes.
  • Keep high-risk fields (billing, SLA tier, escalation flags) tightly controlled.