An illustrative CRM example explains stable source references. See why matching rules, shared email addresses and human review matter when linking customer records.
The spoken explanation, organised by chapter.
This accompanies our article on CRM integration. Establish which records represent the same person or organisation and which information each system owns.
Two fictional contacts share a general email address. Matching only that address could merge their records. Later, one contact changes address.
Each source system keeps its own stable identifier. An explicit mapping table connects those references to the correct destination record. Identity does not change merely because a name or address changes.
Define when a relationship exists, which combinations need review and who may confirm a new mapping. No match or several candidates must not automatically create another customer record.
The CRM may own the account manager, while accounting owns billing information. Transfers update only agreed fields. A returned record must not start an endless loop of changes.
For our shared email address, a person compares source references and relationship details. Only then is a mapping recorded. Similarity alone must not merge the contact histories.
Test changed addresses, merged contacts, concurrent messages and archiving. Reconcile created, updated and rejected records against the source, so incomplete synchronisation does not remain unnoticed in daily use.
Show which record was rejected and why. An administrator should be able to correct and reprocess that record without restarting the entire synchronisation or creating another customer relationship.
CRM integration starts with identity and responsibility, rather than a name lookup. Our source article explains recognition, field agreements, error handling and controlled synchronisation in more detail.
1:52An illustrative CRM request shows how an API integration handles repeated messages, invalid fields and a timeout whose outcome has not yet been established.
Source articleAPI integration for connected business systems
2:00Follow customer details, work status and invoice data through three fictional systems. See why each integration field needs an agreed source and direction.
Source articleSoftware integrations for connected business applications
1:51Use a fictional sales enquiry to see how an AI agent separates facts, unknown information and suggested next steps while a salesperson retains the decision.
Source articleAI sales agent