# Single customer record: one customer, every team

> A single customer record is one entry per customer that head office, dealers, field staff and service all work on. What it holds, and what breaks without it.

The business OS · The Intellsys team · 18 November 2026 · 7 min read

A single customer record is one entry per customer that head office, dealers, the field force and service all read and update, instead of each keeping its own copy. It holds who the customer is, where they came from, who owns them now, what they were quoted and what happened at each step. Without it, every hand-off between teams loses something.

## The short answer

- A single customer record is one entry per customer, shared by every team that touches them.
- It carries the owner and the history, not only the name and number.
- Without it, a hand-off between head office, dealer, field and service loses the customer.
- One record does not mean everyone sees everything: access still follows role and territory.
- You can reach it without a big migration, starting with new leads.

## What a single customer record holds

A contact list is not a customer record. A list tells you who someone is. A record tells you what is happening with them and whose move it is.

- **Who they are** Name, mobile number, city, and the business or household they belong to.
- **Where they came from** The advertisement, store page, dealer or call that produced the enquiry.
- **Who owns them now** One named person, and since when, not a team or a dealership.
- **Where they are** The stage of their journey, from enquiry to sale to service.
- **What was done** Every call, visit and disposition, with who did it and when.
- **What was offered** Each quotation and its versions, and what was shared with the customer.
- **What they own** The products or parts bought, which shape service and the next sale.

*Seven things a single customer record holds. The owner and the history are what make it a record rather than a contact.*

The owner line matters most. A record that says "dealer network" against a customer has no owner at all.

## What breaks without a single customer record

When each team keeps its own copy, the copies drift. Nobody notices on the day. They notice when a customer calls back.

| What happens | With a copy in each team | With one record |
| --- | --- | --- |
| A customer calls the dealer after head office called them | The dealer starts again, and the customer repeats themselves | The dealer sees the earlier call and its outcome |
| A dealer's salesperson leaves | Their leads stay in their phone or their sheet | Their leads are reassigned, with the history kept |
| The same person enquires twice from two advertisements | Two leads, two callers, two quotations | One customer, with both enquiries on it |
| A customer disputes the price they were offered | Someone searches email and laptops for the quote | The quotation and its versions are on the record |
| The customer returns for service | Service has no idea what was promised at sale | Service sees what was bought and what was said |

Each row is an ordinary week in a dealer network. None of them is solved by working harder, because the information exists. It is just in the wrong copy.

## One customer, four teams, one week

Here is the same customer with one record. Each team adds to it; nobody copies it.

- **Head office** An enquiry from a search advertisement creates the record and names the source.
- **Dealer** The record is routed to the dealer for the customer's area, and a salesperson owns it.
- **Field** The salesperson calls, visits and records each outcome as a disposition.
- **Quotation** A quotation is built on the record, revised once, and shared by WhatsApp.
- **Service** Months later, service opens the same record and sees the sale and the promise.

*One customer moving through four teams. Each adds to the same record, so nothing is lost at the hand-off.*

Our own shorthand for this is "One record. Every app a view of it." The dealer sees a queue, head office a dashboard, the field a day plan, service a history. Underneath, it is the same entry. How a disposition list should be built so that the history is useful is in [lead disposition](https://intellsys.cloud/blog/lead-disposition), and how records reach the right dealer is in [lead routing to dealers](https://intellsys.cloud/blog/lead-routing-to-dealers).

## Who owns the record, and who may see it

One record does not mean one open door. A dealer in one city should not see another dealer's customers, and a field officer should see their own leads and not their manager's whole region.

Two ideas are worth keeping apart. **Ownership** says whose move it is: one person, with a date. **Access** says who may see or change the record: decided by role, by reporting line and by geography. A regional manager may see every record in the region without owning any of them. The three questions that decide access are set out in [role-based access control for dealer networks](https://intellsys.cloud/blog/role-based-access-for-dealer-networks).

Before you put teams onto one record, agree these rules in writing.

- [ ] **One identifier** Decide what makes two entries the same customer, usually the mobile number.
- [ ] **One owner at a time** Every record names one person, never a team or a dealership.
- [ ] **A duplicate rule** Say what happens when a known customer enquires again.
- [ ] **A source for each field** Decide which system is right when the ERP and the record disagree.
- [ ] **Access by role and territory** Write down who sees which records, and who may change them.
- [ ] **A reassignment rule** Say who moves records when someone leaves, and keep a log.

*Six rules to agree before teams share one customer record. Each prevents a dispute that would otherwise come up in week one.*

## How to reach one record without a big migration

The usual fear is a year-long data clean-up. You can avoid most of it by starting from today rather than from the archive.

1. **Start with new enquiries** Route every new lead onto the shared record from a fixed date.
2. **Match on the identifier** When a new lead matches an old customer, join them instead of creating another.
3. **Bring open work across** Move leads and quotations still in progress, not closed history.
4. **Switch off the copies** Retire each sheet or list once its open work has moved.
5. **Backfill if it pays** Import older history only where service or repeat sales need it.

*Five steps to a single customer record that start with new leads and leave the archive for last.*

Within a few weeks, the shared record holds most of the work that matters, because most of the work that matters is recent. The wider case for one system is in [what a business operating system is](https://intellsys.cloud/blog/what-is-a-business-operating-system).

> **How Intellsys OS handles it.** In Intellsys OS every team works the same records in the view that suits it: a table, a list, a board or a calendar, a day plan and a queue for each person. Reassigning work, singly or in bulk, keeps an audit log.

## How Intellsys OS keeps one customer record

In Intellsys OS a business defines its own journeys, activities, forms and dispositions, and head office, dealers and the field work the same records. Calls are logged and scheduled on the record, each person has a day plan and a queue, and work can be reassigned one at a time or in bulk, round-robin, with an audit log. Quotations, with their versions and PDF, sit on the record and can be shared by WhatsApp or email. Permissions reach down to a single record, by role, reporting hierarchy and geography, so one record does not mean everyone sees it.

Service Desk works the same record, so a ticket starts from what sales already knows, with response and resolution clocks on every case. More is on [the customers page](https://intellsys.cloud/platform/customers).

## Questions people ask

### What is a single customer record?

It is one entry for each customer that every team works on: head office, dealers, field staff and service. It holds who the customer is, where they came from, who owns them now, and every call, visit, quotation and outcome, instead of each team keeping its own copy.

### Is a single customer record the same as a single customer view?

They are close. A single customer view usually means a screen that gathers data from several systems. A single customer record means the work itself happens on one entry, so there is nothing to gather and no copy to drift out of date.

### Does a single customer record mean every dealer sees every customer?

No. Access is set separately from the record. A dealer sees the customers in their own territory, a field officer sees their own leads, and a regional manager sees the region, decided by role, reporting line and geography.

### How do you handle duplicates in a single customer record?

Agree one identifier, usually the mobile number, and a rule for what happens when a known customer enquires again. The new enquiry is joined to the existing record, with its source kept, rather than creating a second customer with a second owner.

---

[Request a demo](https://intellsys.cloud/demo) · [Blog](https://intellsys.cloud/blog)

This is the Markdown version of https://intellsys.cloud/blog/single-customer-record. Intellsys is built by GrowthJockey, a full stack venture architect.
