The easiest way to manage customer records

A customer database nobody updates is not a database. It is a list of people who used to live there.

Last updated: September 2026

Why customer lists rot

Every trades business has tried this. A spreadsheet, or the contacts app on a phone, or a shoebox of job sheets with names on them. It works for a month and then it rots, because updating it is a separate job from doing the work.

The rot is specific: numbers change, tenants move, the address you have is the billing address and not the site, and the note that explains why this customer always wants a call before you arrive is on a job sheet in a van.

The fix is not a better spreadsheet or more discipline. It is making the customer record a by-product of doing the work, so it updates itself because you used it.

What a trades business actually needs to store

Less than you think. Four fields carry almost all the value:

  • Name and phone, because that is how the job starts.
  • Email, because that is how the confirmation, the quote and the invoice get sent.
  • The site address, separately from the billing address. For letting agents and landlords these are always different, and conflating them is the most expensive small mistake in this list.
  • What you have done for them before, which is the field everybody wants and nobody maintains.

Anything beyond that, a marketing preference, a lead source, a follow-up date, is a field you will not fill in reliably, and a half-filled field is worse than no field because you will trust it.

Search beats structure

The test of a customer list is not how it is organised. It is whether you can find a person in four seconds while they are on the phone.

That means searching by anything you might remember: part of a name, a phone number, a postcode, a street. Trades customers are remembered by street far more often than by surname, which is exactly what a contacts app is worst at.

It also means the history has to hang off the customer. “We were there in March, the write-up says the isolator was already faulty” is the sentence that ends an argument, and it is only available if the record and the work are the same record.

Where Dispatch fits

Customers in Dispatch are searchable by name, email, phone, postcode or street, and can be archived rather than deleted when they go quiet. The site address is held on the job, so one customer can have any number of properties without the billing details drifting.

The part that does the real work is the completion history: every completed job for that customer, grouped by site address, with the write-up and the photographs from each visit. You did not maintain it, and it is the most useful page in the app when a customer rings about work from two years ago.

Because the record is built from jobs, it stays current by itself. Booking a visit, sending a quote, raising an invoice and writing a job up all land on the same customer, so there is no separate housekeeping task to forget.

Deleting a customer properly is handled too: the account owner types the customer name back to confirm, and the jobs, notes, reports, answers and photographs go with them, while invoices and CIS statements are kept because the law requires it.

What your customers never have to do

This matters more than it sounds. Your customers never create an account, never set a password and never install anything. They fill in your fault report form from a link, read and accept a quote from a link, message you about the job from a link, and pay the invoice from a link.

Every one of those links produces a record attached to the customer without anyone typing it in. That is what keeps a customer list current: it is a residue of work rather than a chore.

The honest limits

This is not a sales CRM. There are no pipelines, no lead stages, no marketing campaigns and no reminder to ring a prospect in six months. If you want to run outbound sales properly, you want a different category of tool and you will be disappointed here.

There is also no import wizard for a shoebox. Moving an existing list across means entering customers as their next job comes in, which sounds slow and is usually faster than it sounds: most trades businesses discover that the customers who matter are the ones who ring, and within a couple of months they are all in there.

If your question is really about handling repeat customers on a cycle rather than storing them, managing recurring customer jobs is the more useful page.

Questions

Customer records: FAQ

What should a trades customer record contain?

Name, phone, email and the site address kept separately from the billing address, plus the history of what you have done for them. Extra fields tend not to get filled in, and a half-filled field is worse than none.

How do I find a customer quickly on the phone?

Search by whatever you remember. In Dispatch that is name, email, phone, postcode or street, because trades customers are remembered by street at least as often as by surname.

Can one customer have several properties?

Yes. The site address lives on the job, so a landlord or agent can have any number of addresses without the billing details drifting between them.

Is this a CRM?

Not in the sales sense. There are no pipelines, lead stages or marketing campaigns. It is a customer record attached to the work you have done for them.

What happens if a customer asks to be deleted?

The account owner types the customer name back to confirm, and their jobs, notes, reports and photographs are deleted. Invoices and CIS statements are kept, because the law requires it.

A customer list that maintains itself

Searchable customers, site addresses on the job, and every completed visit filed under the address it happened at.