Problem guide
Repeat customers have to explain their site or account every time
Repeat customers re-explain themselves because what your people learned last time was saved on a job, a visit or an order, not on the customer or the place. That record closes, and the next request starts from the customer's memory. Jobber's help says properties have no notes field, so a site fact lands on the client, where every site's work shows it, or on one job, where it stays. Choose the record that belongs to the place or account, keep standing facts there, and read it first on every new request.

How it actually happens
Customer knowledge is learned one visit, call or order at a time, and it is learned by whoever happened to be there. In field service, the first tech finds out the loading dock gate sticks and the security desk wants a call twenty minutes ahead. The second learns that the rooftop unit on the north side is the one with the bad disconnect. The third learns the facility manager changed and the new one only answers texts. A clinic, a law firm or an accounting firm collects the same kind of facts: the patient who needs the ground-floor room, the client who only signs on paper, the bookkeeper who sends statements late every quarter.
Each of those facts gets written, if it gets written at all, in the place the person is already typing: the notes on today's job, visit or matter. That record closes. The next request creates a new one with an empty notes field, and the person taking the call asks the customer the same questions the last three people already answered.
The software usually has a better place, and it usually goes unused. ServiceTitan keeps a location record for each service address with its jobs and equipment. Housecall Pro has Address Notes that follow the address to every future job. Jobber has no notes on properties at all, so site facts go on the client, where they show on every site's work, or on a job, where they stay. In each case, the place a fact ends up depends on which box someone tapped at the end of a long day.
Then the office adds its own split. A customer who is "Smith Property Management" in the operating system may be "Smith Property Mgmt LLC" in the accounting system because QuickBooks Online would not accept a duplicate name. Search for one and you will not find the other.
Here is a typical example from field work. A plumbing company has serviced a strip mall for four years. The shutoff for unit C is behind a locked panel in unit D, and the key is with the landlord's maintenance man. The tech who knew retired in the spring. The next call is a burst pipe on a Saturday. The new tech spends forty minutes finding the shutoff while the tenant's floor floods, and the landlord explains the key arrangement on the phone, again.
What it costs the relationship
A repeat customer stays because working with you is easier than starting over with someone else. Every repeated question erodes that. By the third time a facility manager walks a new tech to the roof, or a patient fills in the same history form, you are no different to them from the business down the road, except that you already know how much they have been paying.
Signs you have this problem
- Customers sigh and say they have been through this with you before
- Whoever takes the request asks for access details, contacts and preferences on every call
- Only one person knows how a particular customer, building or account works
- Your people arrive or respond without the key, badge, document or detail that customer always needs
- Useful notes exist, but inside closed jobs, old emails or a former employee's phone
What usually causes it
- Standing facts are written on the job, visit or order where they were learned, and that record closes with them insideThe handoff gap
- What people learn on site or in the conversation rarely travels back to whoever takes the next requestThe field-to-office split
- Each customer's quirks are handled as one-off surprises instead of standing conditionsThe exception swamp
Find your cause
Ask these in order. The first yes is usually where yours starts.
- Does your system have a record for the place or account separate from the single job, visit or order?If yes: the structure exists; the problem is where people type. If no, as with Jobber properties, decide how standing facts will be labeled on the client so they are not mistaken for another site's.
- When someone learns something about a customer, does it end up anywhere but the job?If yes: check that the person taking the next request reads it. If no, close-out is where customer knowledge dies.
- Is there a customer only one person knows how to serve?If yes: that customer is your test case. Write their record from that person's head this week.
- Do your accounting system and operating system spell the same customer differently?If yes: duplicates are likely splitting history. Fix the names before importing anything else.
How it breaks in each industry
- Commercial HVAC and mechanical service
- The site knowledge is physical: which roof hatch, which ladder, which unit serves which zone, which panel kills which compressor. It sits with the tech who has been there five times. When he is off, the crew spends the first hour finding the equipment and the customer spends it on the phone.
- Facilities maintenance for multi-site clients
- One client, sixty stores, each with its own hours, door, contact and landlord rules. Notes saved at the client level appear on every store's jobs, so the crew at store twelve reads instructions meant for store forty.
- Healthcare practices and clinics
- Patients fill in the same intake form at each visit and repeat their history to the front desk, the assistant and the provider. What one staff member learned about a patient's preferences or access needs sits in a visit note that the next scheduler never opens.
- Accounting and professional services firms
- Each year's engagement starts a new file. The client re-sends the same entity details, contacts and quirks of their books because last year's notes live in last year's folder or in the head of the staff member who has since moved on.
Where it breaks between systems
- Jobber clients and properties
- Jobber's help center says properties have no notes field. A note left on a client links by default to that client's requests, quotes, jobs and invoices, and notes left on visits become job notes. For a client with several sites, a site fact either goes on the client, where every site's work shows it, or on a past job, where the next job does not.[1]
- Housecall Pro address and job notes
- Address Notes apply to a single service address and appear on every future job or estimate created there. Private notes on jobs and estimates hold information specific to that one job. The right place exists, but a fact a tech types into the job note stays on that job until someone moves it.[2]
- ServiceTitan location record
- ServiceTitan's glossary defines a location as a physical service address tied to a customer, holding the jobs, equipment and history for that property, so a business with multi-location customers can track work site by site. The structure is there; whether a tech's discovery reaches it depends on where the tech typed.[4]
- ServiceTitan follow-up notes
- A note logged while following up on an estimate reaches the location record only if the user ticks Copy to Location Notes. Site notes are opt-in, one entry at a time.[3]
- ServiceTitan and QuickBooks Online
- The connection moves invoices, payments, expenses and sales tax into QuickBooks Online. Nothing about sites, access or equipment history is part of it, so the accounting record of a repeat customer says what they paid, not what the crew needs to know.[5]
- QuickBooks Online customer names
- QuickBooks Online rejects a name already used by another customer, vendor or employee, and Intuit's fix is to change one of them, for instance by adding a middle initial or a number. Two sites or two owners with the same name end up spelled differently in the books than in the field system.[6]
- Housecall Pro and QuickBooks Desktop
- Housecall Pro tells users to make the Customer Name in QuickBooks Desktop match the Display Name in Housecall Pro exactly before completing the job. If they differ, completing the job creates a duplicate customer in QuickBooks Desktop, splitting one customer's history across two records.[7]
By the numbers
No industry association or government survey publishes a figure for this. The measurement below gives you your own.
Rules that apply
- 40 CFR 82.157(l), refrigerant service records[8]
- For equipment with a full charge of 50 pounds or more of an ozone-depleting refrigerant, each service visit produces a record for the owner that includes the amount and type of refrigerant added, and the records are kept at least three years. When that history sits on the right site and the right unit, the next tech and the owner can both find it; when it sits on a closed job, nobody can.
- 40 CFR 84.106, HFC leak repair[9]
- Since January 1, 2026, appliances holding 15 pounds or more of an HFC or a high-GWP substitute carry their own leak-repair records, also kept three years. The rule leaves out the residential and light commercial air conditioning and heat pump subsector. On covered equipment, equipment history is a regulated record, not a courtesy note.
Measure it in your own shop
From: Your last 20 jobs, visits or orders for repeat customers, their notes, the standing record for each customer, and the call or intake notes.
- For each one, list the standing facts your people needed: access, contacts, preferences, rules, equipment or account details, past problems.
- Sort each fact into one of four bins. Connected: on the standing record and seen by the person doing the work. Split: recorded, but on a past job or the wrong record. Hidden: recorded somewhere nobody looked, such as an email or a personal phone. Missing: not written anywhere.
- Count the times a missing or hidden fact cost a phone call, a wait, a repeated question or a return trip.
Reading it: Your own history test, not an industry figure. A high Split count says the system has a place for standing facts that nobody uses. A high Missing count says the knowledge only exists in people's heads, which is a staffing risk before it is a software one.
What does not fix it
- One long customer note
- In systems where client notes flow to every job, a long note becomes noise that everyone scrolls past, and site twelve's instructions show up at site forty.
- A CRM bolted onto accounting
- Accounting connections carry invoices and payments. A CRM fed from them knows what the customer paid, not where the shutoff is or how the customer wants to be contacted.
- Telling people to write better notes
- Better notes on the job still close with the job. The question is where the note goes, not how good it is.
What to try this week
- Find the record that belongs to the place or accountCheck what your system offers above the single job: a location record, an address note, a property, an account or client profile. Write down where a standing fact should go so it shows up on the next request, and where it should not go.
- Start with your twenty busiest customersFor each, ask the person who knows them best for access, contacts, preferences, rules, key equipment or history, and anything that went wrong before. Put it on the standing record, not on a job.
- Keep it short enough to read on a callTen lines that someone can scan while the customer is on the phone beat a page nobody opens. Put the one thing that causes a wasted trip or a repeated question at the top.
- Add a check to close-outBefore anyone closes a job, visit or order, one question: did anything about this customer change or surprise you? If yes, it goes to the standing record that day, by that person or by a named office person.
- Read the record when the request comes inWhoever takes the request opens the standing record before asking the customer anything. Ask only what the record cannot answer.
Where do-it-yourself stops
These steps spare your best customers from repeating themselves for the accounts you have covered, and they expose how much knowledge lives with one or two people. They still depend on people flagging changes and someone moving notes by hand, and they do not connect the customer record to quoting, scheduling and accounting. The lasting fix is a tool built around your own systems, so what your people learn about a customer is waiting the next time anyone touches that account. That is what a Workflow Spec designs.
Questions people ask
Why do our repeat customers have to explain themselves every time?
Because what your people learned on earlier visits or calls was written on those visits, not on the customer or the site. When the job closed, the knowledge closed with it, and the next request starts from the customer's memory instead of yours.
Where should site notes live in Jobber?
Jobber's help center says properties have no notes field, and client notes link to everything for that client by default. For a single-site client, the client note works. For multi-site clients, label each fact with the site it belongs to, or keep a site record outside Jobber that the office reads.
Does Housecall Pro keep notes by address?
Yes. Housecall Pro's Address Notes stay with one service address and show on every future job or estimate there. The catch is that techs often type into the job's private note instead, which stays with that job.
Do we have to keep equipment service records?
For some equipment, yes. Large commercial refrigeration and air conditioning systems covered by 40 CFR 82.157 and 84.106 need refrigerant service records kept at least three years. Keeping them with the site and unit makes them findable when the next tech or an inspector asks.
Who should keep the customer record current?
The person who notices a change reports it, and one named person in the office makes sure it lands. Without a named person, everyone assumes someone else updated it.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.
Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.
