Prompt
I'm building one shared customer record for sales, support, and marketing teams
Latest observation
That’s a solid goal. A single shared customer record can reduce duplicate work, improve handoffs, and give every team the same context.
A good way to think about it is to define one customer “source of truth” that includes:
- Identity data: name, email, phone, company, account owner
- Firmographic data: industry, size, location, revenue
- Interaction history: calls, emails, meetings, web activity, tickets, campaigns
- Lifecycle status: lead, MQL, SQL, active customer, churned, renewal due
- Support context: open cases, SLAs, product usage issues, severity
- Sales context: pipeline stage, opportunities, next steps, close date
- Marketing context: segment, campaign engagement, consent/preferences
- Data governance: who can edit what, audit history, deduping rules
To make it work across teams, you’ll want to define:
-
Unique customer identity rules
How you match and merge records across systems. -
Field ownership
Which team/system is the authority for each field. -
Access control
What sales, support, and marketing can see or edit. -
Event tracking
Every customer interaction should feed into the same timeline. -
Lifecycle alignment
Agree on shared definitions for stages and statuses. -
Automation and routing
Triggers like assigning cases, alerts, or campaign suppression.
If you want, I can help you design:
- a data model/schema for the shared customer record,
- a field ownership matrix by team,
- or a CRM architecture for how to implement it.
Brands