What a customer record should contain

A customer record is the short sheet of facts your business keeps about one person or one company. Most records grow by accident. A field gets added because someone needed it once. A form picks up a new box because a tool offered one. Nobody ever removes anything. A year later the record has forty fields and your team reads six of them. The other thirty-four are scrolled past every day.

This article is about which fields earn their place and which ones nobody reads again. The working test is easy to state and harder to apply. A field earns its place when someone acts on it. If a value never changes a decision, a message, or a next step, it is decoration, and decoration has a cost: it hides the fields that matter.

Decide what the record is for before you decide what it holds

A record is not an archive of everything you could know about someone. It is the smallest set of facts that lets the next person pick up the relationship without starting again. That framing is worth settling first, because it decides everything downstream. If you are unclear on the job the record does, it is worth reading what one customer record actually means and what a CRM is actually for before you argue about fields.

Data protection law points in the same direction, and it is a useful discipline even where it does not strictly apply to you. The standard it sets is that personal data should be "adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed" [1]. Read that as a design rule, not just a legal one. Every field should trace back to a purpose. If you cannot name the purpose, you cannot justify the field.

The four jobs a good record does

Almost every field that earns its place is doing one of four jobs. If a field is not doing one of these, be suspicious of it.

Identity: who this is

You need enough to know you are looking at the right person or company and not a near-duplicate. A name, the organisation they belong to, and one stable identifier that does not change when they move house or switch jobs. Identity fields are the ones you can least afford to get wrong, because every other fact hangs off them. Two half-records for the same customer are worse than one, which is the quiet problem behind why your team asks the same question twice.

Reach: how to contact them

An email address, a phone number, and the channel they actually reply on. That last part matters more than the count of fields. A customer with five contact methods and no note about which one they answer is harder to reach than one with a single working channel. Capture the channel of record, not every channel that exists.

Context: what has already happened

What they bought, what they asked, the last few conversations, and any open quote or invoice. This is the part that saves a relationship from feeling anonymous. It is also the part most often scattered across tools, which is why it is worth keeping conversations, quotes and invoices against the same record rather than in separate systems.

State: where things stand now

The stage they are at, who owns the relationship, and the single next action with a date. State is the most valuable part of a record and the most perishable. A pipeline stage that is three months stale is not context; it is a wrong answer presented as a fact.

The fields nobody reads again

Against those four jobs, a familiar set of fields turns out to be doing none of them.

• Vanity fields. "How did you hear about us" collected on every form and never once analysed. If you are not going to read it in aggregate, stop asking.
• Duplicated facts. A field that copies a value living authoritatively in another system. The copy drifts, and now you have two answers and no way to tell which is current.
• Stale enrichment. Company size, job title, and social links pulled in once from a data provider and never refreshed. These age badly and are rarely acted on.
• Orphan free-text. A notes box with no owner and no convention, where five people write in five formats and nobody trusts any of it.
• Catch-all custom fields. The ones added for a campaign that ended, still sitting there because deleting felt risky.

None of these are read in the normal course of work. They are read, if ever, when someone is auditing the mess. The cost is not storage. The cost is that a crowded record trains your team to stop reading records at all.

Accuracy beats completeness

The instinct when tidying a record is to fill the gaps. The better instinct is to correct what is wrong and delete what is unused. A record that is half the size but true is more useful than a full one you cannot trust. The same legal standard that asks for relevance also asks that "every reasonable step must be taken to ensure that personal data that are inaccurate, having regard to the purposes for which they are processed, are erased or rectified without delay" [2]. In plain terms: wrong data should be fixed or removed, not left in place because removing it feels like losing information.

This is where habits matter more than schema. A well-designed record still rots if nobody maintains it, which is the theme of why your CRM is only as good as your habits. The field that earns its place today loses it the moment it goes stale and nobody corrects it.

Keep less, on purpose

There is a second reason to hold fewer fields: the ones you do not need become a liability the day something goes wrong. A record you no longer use is a record you now have to secure, back up, and account for. The principle to borrow here is that retention should be deliberate, "ensuring that the period for which the personal data are stored is limited to a strict minimum" [3], and that data is "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed" [4].

Practically, that means deciding up front how long a closed or dormant record stays, and letting it go on schedule rather than keeping everything forever by default. It is easier to be confident about this when you can get your data out and see it plainly, which is the point of the data you should be able to export on any Tuesday.

How 360REV approaches it

360REV keeps identity, reach, context and state against one record, so a conversation, a quote and an invoice sit beside the person rather than in separate tools. The aim is a record a colleague can read in ten seconds and act on, not a form with every box ticked.

A test you can run this week

Pick ten records at random and read them as if you were picking up each relationship cold. For every field, ask one question: when did someone last act on this value. If the honest answer is never, mark the field for removal. If the answer is often, the field has earned its place.

Do that once and you will usually find the same handful of fields carrying the weight, and a long tail of fields that exist only because nobody stopped to ask. A customer record should contain the facts that change what you do next, kept accurate, and nothing that merely feels thorough.