<!-- https://heyly.ai/blog/customer-notes -->
# Customer notes for service businesses: what to keep and where


Customer notes are the record of what each customer has told you over every job and every call, kept under their name so it is in front of you the next time they ring. For a service business they are not a CRM feature. They are the difference between "like we discussed" landing on someone who remembers and on someone who is stalling.

Most advice about customer notes is written for online stores and sales teams. This page is for a business where the person who answers the phone is the person doing the work.

## The moment customer notes are for

A regular calls and says "it's doing that thing again, like last winter". You have done a few hundred jobs since last winter. You know the voice, roughly the street, and nothing else.

What happens next decides whether you sound like their contractor or like the next result on Google. If the last visit's notes are in front of you, you say "the condenser fan, the one we said was on its way out" and the call is half done. If they are not, you ask questions they have already answered once, and they notice.

Notes taken per call help with today. Customer notes are what make the fourth call with the same person easier than the first.

## What belongs in them

Keep what the customer will expect you to remember, in their words where possible.

- **Access.** Address, gate or lockbox code, where to park, which door, whether someone is home during the day.
- **The equipment and its history.** Make and model, rough age, what you replaced and when, what you said was close to failing.
- **What you quoted.** The figure, what it covered, the date you gave it, and whether it was firm. When the next quote does not match the last one, this line is what saves the conversation.
- **What is still open.** A balance, a part you promised to bring back, a warranty question, a callback you said you would make.
- **The human details.** The dog's name, that they work nights, that they prefer a text before you arrive. Small, and remembered by the customer far longer than the invoice.

A useful shorthand for the middle three is said, quoted, owed: what they told you, what you told them it would cost, and what is still open between you. If those three are current, the notes are doing their job.

## What does not belong in them

Customer notes get read by whoever has the phone that day, and they get stored on devices that get lost. Some details should not be in them at all, and some need more care than the rest.

- **Payment card numbers.** Never in a note, in any form.
- **Opinions about the customer.** Write what was agreed, not what you think of them. Assume they could one day read it.
- **Alarm codes and door codes**, if you keep them, belong somewhere locked, not in a free-text field anyone with your unlocked phone can scroll. A gate code to a shared driveway is one thing; the code that disarms someone's house is another.

The FTC's [guide to protecting personal information](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business) is written for exactly this size of business, and its first principle is the useful one here: keep only what you need, and know where you keep it. The rest of the FTC's [privacy and security guidance](https://www.ftc.gov/business-guidance/privacy-security) covers what to do when a device with customer details on it goes missing.

## Where to keep them so they come back

The format matters less than one property: **the notes have to surface when that customer's number rings.** A beautiful spreadsheet on a laptop at home fails that test every time you are on a roof.

For a small operation, that usually means the notes field on the customer's contact card, because it sits on the phone that rings and it opens with the contact. One page per customer in a notes app works too, as long as you can find it by name in a few seconds with gloves off.

Your phone's call history is not a notes system. It records the number, the time and the duration of each call, and none of what was said. It can tell you a customer called four times in March. It cannot tell you what they wanted.

## The part that always breaks

Every customer-notes system fails in the same place: someone has to type the notes. On a busy day the calls you were on are exactly the calls you did not write up, and those are the busy-season customers you most needed to remember.

The fixes are boring and they work. Keep the template short enough to fill in at a red light. Write the numbers during the call and everything else straight after it. And once a week, look at who called and whose card did not change, because that list is where the gaps are.

## Where Heyly fits

We build a product for this, so read this section as a positioned claim.

[Heyly](/) is built for the calls you keep, not only the ones you miss. It writes down what each customer said, what you quoted and what is still owed, and keeps it under that customer, so the notes exist without anyone typing them after the call. Give customers a Heyly number and it is on every call, yours included: while you talk, the caller's words are on your screen, and when you cannot pick up, it answers, says it is an assistant, and adds that call to the same customer's notes. Keep your own number and Heyly's AI answers it for you, then writes down what was said.

Its limit is the same as any call-based system: it only knows what was said on a call. The extra you agreed at the door, the change you made on site, none of that reaches it unless it is said on the phone. And "owed" means the figures as they were spoken, not a ledger of balances.

To hear how it handles a call before anything else, ring our own line on +1 208 504 3639. It answers as a sample plumbing business and says it is an AI assistant.

If you are working out whether the calls you miss are worth solving first, start with [what a missed call actually costs](/blog/what-a-missed-call-costs). For notes on a single call, the template is in [phone call notes](/blog/phone-call-notes).

## FAQ

### What should customer notes include for a trades business?

Access details, the equipment and its history, what you quoted and when, anything still open, and the small human details the customer will expect you to remember. Said, quoted and owed covers the part that costs money when it is lost.

### What should never go in customer notes?

Card numbers, opinions about the customer, and anything that would do real harm if your phone were lost, such as an alarm code kept in a plain text field. Keep only what you need, and keep the sensitive part somewhere locked.

### Where should a small service business keep customer notes?

Somewhere that opens when the customer's number rings. For most one-truck businesses that is the notes field on the contact card or one page per customer in a notes app on the phone. A system you cannot reach from a job site fails when it matters.

### How do I make sure customer notes actually get written?

Keep the template short, write numbers during the call and the rest straight after it, and check once a week which customers called without their notes changing. That weekly check finds the gaps before a customer does.

### Can software keep customer notes for me?

Some tools write notes from your calls so you do not have to type them. Check whether they keep notes per customer across calls or only summarise one call at a time, and whether they work on the calls you answer yourself, not only on the ones they answer for you.

