What should a customer record contain?
What should a customer record contain? Some businesses keep only a name and phone; others open a thirty-field form and fill none of it. Both are useless. 🪪
A customer record should show, at a glance, what a decision needs: who, where they came from, what they bought, and when last.
Short answer: a record has four layers — identity, source, history, consent. Every field must feed a decision; a field that doesn’t isn’t opened. 📋
Four layers of a record
BU BÖLÜMÜN ÖZETİ
- Identity
- Source
- History
- Consent
Each answers a question. 🧩
Identity
Name, phone, email, company; who is the customer? 🪪
Source
How did they find us? Ads, referral, search, shop; feeds channel decisions. 🧭
History
First purchase, last purchase, total spend, products bought; the relationship in brief. 📜
Consent
Which channels they agreed to and when; required for marketing messages. ✅
When to open a field
Four questions. ❓
Business customer records
BU BÖLÜMÜN ÖZETİ
- Company and tax details
- Several contacts
- Contracts and quotes
- Payment terms
Four fields that differ. 🏢
Company and tax details
What invoicing needs; one correct source. 🧾
Several contacts
Purchasing, accounts, users; each a separate contact. 👥
Contracts and quotes
The current contract and last quote; see the documents guide. 📄
Payment terms
Terms and payment habits; feed cash planning. 💳
Keeping records alive
BU BÖLÜMÜN ÖZETİ
- Automatic updates
- Note discipline
- Yearly review
- One record per customer
Four habits. 🔄
Automatic updates
Last purchase and total spend update by themselves on each sale. ⚙️
Note discipline
Meeting notes short and dated; a record, not a novel. 📝
Yearly review
Stale contact details get checked. 🗓️
One record per customer
No duplicates; see the duplicate records guide. 👯
Four common mistakes
BU BÖLÜMÜN ÖZETİ
- A thirty-field form
- Not recording source
- Keeping consent elsewhere
- Scattered notes
All four make records unusable. 🚧
A thirty-field form
Empty fields crowd the record and bury information. 📋
Not recording source
Which channel brings customers is never known. 🧭
Keeping consent elsewhere
If consent isn’t on the record, messages reach the wrong people. ⚠️
Scattered notes
Notes in email, messages, notebooks; the record stays incomplete. 🗂️
What should I do today?
BU BÖLÜMÜN ÖZETİ
- Step 1: list current fields
- Step 2: check the four layers
- Step 3: close one field, open one
- If you want help
Three steps, one hour. 🪜
Step 1: list current fields
How many fields, and how many are filled? 📊
Step 2: check the four layers
Identity, source, history, consent; which is missing? 🧩
Step 3: close one field, open one
Remove a field nobody fills; add source if it’s missing. ✂️
If you want help
Let us design your customer record together: use the consult your expert form. For your current setup see the digital audit; the bigger picture sits in the data housekeeping roadmap. 🎯
Related reading from the archive: answering customer questions · WhatsApp and SMS.
📝 Notes From the Field
A business’s customer record had over thirty fields, mostly empty; where customers came from was never recorded. The record was reduced to four layers, a source dropdown was added and history fields updated automatically from sales. A few months later it could finally see which channel brought the most valuable customers.
📖 Short Glossary
Customer record: the single record holding a customer’s information. Source: the channel through which the customer found you. Consent: permission for contact. Total spend: the sum of a customer’s purchases.
⚡ Quick Summary
A customer record shows decision information at a glance. 🪪 It has four layers: identity, source, history, consent. Each field must feed a decision, with a clear owner and update moment. Business records add company details, several contacts, contracts and payment terms.
🎯 Next Step
Let us design your customer record: use the consult your expert form. The product side sits in the product data guide; for your setup see the digital audit.
Frequently Asked Questions
Sık Sorulan Sorular
What will be done by looking at it? No answer, no field. 🎯
A field nobody fills is a field that stays empty. 👤
Stale information misleads; the update moment must be clear. 🗓️
Useless personal data isn’t collected; see the data limits guide. 🚫
Only if you have a real purpose and the customer gives it knowingly. Purposeless personal data is both a burden and a compliance risk.
Automatically through a hidden web form field, and by asking “how did you hear about us?” on the phone. A dropdown keeps it tidy.
Short, dated and action-oriented. What the next person contacting the customer needs to know is enough.
Source: Turkish Personal Data Protection Authority — guidance