Start with the work
For each piece of information, distinguish the source, the authoritative copy and the person allowed to change it. Company data, conversation context and subscription preferences can have different authorities.
Build the working checklist
- List source, purpose, verification date and access for each required field.
- Choose an identifier and a duplicate resolution rule.
- Assign ownership for corrections and deletions.
- Document what should happen when systems disagree.
Check it against a real task
Rehearse a changed email address, reassigned account and duplicate record. Verify that connected systems do not restore an obsolete value after the team corrects it.
What to take away
The result should be a field map and a responsibility map. Automatic synchronization is useful only when its conflict rules match those maps.
Build a field responsibility map
Scroll horizontally to read all columns.
| Field | Authoritative source | Review question |
|---|---|---|
| Account identifier | The agreed shared record | How are duplicates recognized before updating? |
| Enquiry context | The original request and reviewed summary | Can the operator distinguish a quotation from an inference? |
| Company information | The verified source with a review date | What happens when the customer corrects an external field? |
| Preference or exclusion | The reviewed preference record | Can a later import reactivate an obsolete status? |
| Owner and next action | The operating team’s shared record | Who acknowledges an ownership change? |
Work through a correction
Suppose an external record lists a person in the wrong role. The operator verifies the correction and updates the shared record. A later synchronization should not automatically restore the old value. The field map must identify which source wins, who resolves conflicts and which connected systems need the correction. Without that rule, adding synchronization increases uncertainty.
Review access and retention with the same map
For each field, identify who needs it to complete the task and who can correct or remove it. Define a review or retention rule with the responsible operator and appropriate reviewer. Copying a full conversation into every tool is rarely necessary when a source link and a reviewed handoff summary will do. Do not put actual customer records into the downloadable template.
Working files
Blank templates for your own planning. These contain no customer records and are not submitted to Sales Fit Lab.
Columns for source, authoritative copy, access, conflict handling and retention owner.