← Back to the field guide
Connect business data and workflows

Salesforce: decide where the customer record lives.

The useful CRM question is often about ownership, not another field.

November 7, 2026 · Source-backed explainer · Synthetic example

Dash-Squared editorial · Last reviewed November 7, 2026

Look inside the idea

Connected does not mean synchronized.

Business integration / decide who owns the record and how failures recover.

Connected does not mean synchronized.Business integration / decide who owns the record and how failures recover. Name the source of truth, the record ID and the exception owner.DASH-SQUARED / THE VISUAL FIELD GUIDEConnected does not mean synchronized.Business integration / decide who owns the record and how failures recover.Source recordStable source IDIntegrationValidate + map fieldsCheck repeated eventsTarget recordAPI / eventException ownerReview + reconcileA retry is not automatically safe.Repeated events should not create duplicate actions.Use stable IDs, suitable retries and reconciliation.Name the source of truth, the record ID and the exception owner.Illustrative model · Read the explanation, limits and sources alongside it.
A source record identified by a stable ID feeds an integration that validates fields, maps data and handles repeated events before updating a target record. Failed work goes to an exception owner for reconciliation. Open full graphic ↗

Follow the idea

  1. Identify the source record and the fields it owns.
  2. Validate, map and handle repeats before changing the target.
  3. Send failed or conflicting work to an owner for reconciliation.

Keep the limit visible

Conceptual design, not a universal exactly-once guarantee. Interfaces, transaction semantics, ordering and retry behavior differ. Each target operation needs an explicit recovery design.

What if the same event arrives twice?

Use stable event/record identity and an operation-specific strategy so a repeat does not create an unintended duplicate. Some interfaces require reconciliation rather than a blind retry.

A common assumption

“Connecting two systems means their records will stay consistent.”

Ownership, mappings, duplicate handling and recovery need a deliberate design.

Source for this graphic: learn.microsoft.com ↗ www.twilio.com ↗ · Checked November 7, 2026 · Illustrative example.

In this explanation01The job it does02A concrete example03What it does not solve

The job it does

Salesforce provides customer relationship management and related business applications. This guide focuses on a CRM as a system of record: who maintains customer information and how other systems should refer to it.

A concrete example

Synthetic example: sales creates an account while service updates the contact details. Decide which record is authoritative, which fields synchronize and what happens when two systems disagree.

What it does not solve

A CRM does not resolve conflicting definitions or produce clean data merely by storing it. Access, adoption and integration ownership need explicit decisions.

The next useful question

Which system owns each important customer field?

Before choosing the tool

  1. Which system owns each important customer field?
  2. How will matching, duplicate records and conflicting updates be handled?
  3. Which team owns an integration exception after handover?

What we would verify

Move a small synthetic dataset through create, update and failure cases. Check reconciliation and permissions before migrating real customer records.

When a simpler answer may fit

Improving a current CRM or using a simpler customer-management process may be more useful than replacing the platform.

Understand the idea beneath the productRead the concept explanation ↗
Primary sources · checked November 7, 2026www.salesforce.com · source ↗

Independent, unsponsored education. This is an explanation of a tool and a possible approach, not a claim of delivery experience, certification, endorsement or partnership. Verify the actual product, plan and configuration.

Published .