What actually belongs in a shared customer record

The promise of a unified platform is that everyone reads the same record. The risk is that everyone also writes to it, and within a quarter the contact has forty fields that three different teams interpret differently.

The test for a shared field

A field belongs on the shared record if more than one team reads it and all of them mean the same thing by it. Billing address passes. Lead score usually does not, because sales and marketing rarely define it identically.

• Identity: name, company, role, contact channels
• Commercial state: open deals, contract terms, payment status
• Relationship history: conversations, notes, meetings, files
• Ownership: who is accountable, and since when

What to keep team-local

Working state belongs to the team that produces it. A support triage flag, a marketing segment, a delivery checklist — these change on their own cadence and confuse everyone else when promoted to the shared record. Link them to the contact instead of flattening them onto it.

One owner per field

Every shared field should have a team that owns its definition and a rule for how it changes. Without that, the field slowly becomes advisory, and people go back to asking each other in chat — which is exactly the cost consolidation was supposed to remove.