THE SHORT ANSWER
Store only data that supports a defined customer or operational decision: identity and contact details, source, lifecycle stage, interactions, relevant purchase or service history, preferences, consent and account context. Limit access, maintain quality and delete or correct data under the rules that apply.
Build the minimum useful customer record
| Area | Purpose | Quality question |
|---|---|---|
| Identity/contact | Recognize and reach the right person or account | Is it current and verified where needed? |
| Source | Understand how the relationship began | Is the definition consistent? |
| Lifecycle stage | Coordinate the next action | Is it evidence-based and maintained? |
| Interactions | Preserve useful context | Is the note relevant and respectful? |
| Purchase/service history | Deliver and support the relationship | Are returns, cancellations and issues included? |
| Preferences/consent | Respect communication choices | Can origin, scope and change be shown? |
| Account context | Serve multi-person relationships | Are roles and permissions distinct? |
Treat data quality as operating work
Duplicates split a relationship across records. Stale stages misroute work. Missing source and outcome fields weaken analysis. Uncontrolled free text can collect speculation or sensitive information that should not be there.
- Choose a stable identifier and duplicate-resolution rule.
- Define who owns each important field.
- Use controlled values where comparison matters.
- Record uncertainty instead of inventing precision.
- Review stale records and failed automation.
- Restrict access according to job need.
Collect for a purpose, not for possibility
Before adding a field, name the decision, service or obligation it supports. Consider whether the same outcome can be reached with less precise or less sensitive information. Explain collection in language the customer can understand.
Evidence & context: UK Information Commissioner's Office
Make the record usable and accountable
Document field meanings, permitted uses, access, retention and correction paths. Requirements vary by jurisdiction, industry and data type; obtain specialist advice for the applicable context.
Use the record for segmentation and measurement, while keeping analytics definitions separate from operational truth.
Sources & further reading
- Customer Relationship Management
OpenStax, Rice University. Open educational material on managing customer relationships and value over time. CRM software and lifecycle messaging do not themselves create retention.
- Direct marketing guidance
UK Information Commissioner's Office. UK regulatory guidance on planning, collecting information, transparency and respecting communication preferences, checked 28 September 2026. Requirements vary by jurisdiction and context; this is not individual legal advice.
- How should we assess security and data minimisation in AI?
UK Information Commissioner's Office. UK regulatory guidance, checked 11 September 2026. Jurisdiction-specific context, not individual legal advice or permission for a particular use.
Examples and exercises are illustrative unless attributed to a source. No independent expert review is claimed.
A correction, a counterexample or an experience worth sharing?
Join the conversation ↗