How to Track Client History and Information in Commercial Kitchen Equipment Service

Client history and equipment history are 2 different records and only 1 of them gets kept properly. The equipment has a file. The account has a scattering of emails, and the 5 things that decide how a relationship goes live in whichever technician has covered it longest.

The short version

Service companies that take records seriously usually mean equipment records: manufacturer, model, serial, what was done and what it cost. That is the right priority and it is half the picture.

The other half is the account. Who decides, what they are sensitive about, what was promised, how they pay, and which of their sites is difficult. None of that belongs on a piece of equipment and all of it decides how the relationship goes.

It also disappears when somebody leaves, which is why a service company can hold five years of perfect service history and still handle an account badly after a resignation.

What belongs where

Record	What it holds
The equipment	Manufacturer, model, serial, service history, parts, warranty, readings
The site	Access, hours, who holds a key, isolators, parking, quirks
The account	Who decides, spending limits, payment behavior, commercial context
The contract	Covered equipment, intervals, exclusions, rates, review dates

Most service companies keep the first properly, the second in people's heads, the third in email, and the fourth in a signed document nobody has opened since.

Roopairs holds clients with their service locations and equipment records beneath them, which is what gives the second and third rows somewhere to live rather than being kept alongside the system.

The 5 things that only exist in somebody's head

Ask any technician who has covered an account for three years and they will list these without pausing.

1. Who actually decides. Frequently not the person who calls, and the two are rarely the same on chain work
2. What they are sensitive about. A previous dispute, a piece of equipment they believe you should have fixed, a rate they queried
3. What was promised verbally. A discount, a response commitment, a favor done once that became an expectation
4. How they behave when something goes wrong. Some escalate immediately and some never complain until they leave
5. Which of their sites is difficult, and why, which is usually a person rather than a building

None of those is on a work order and all five change how a job should be handled. The third is the one that causes real damage, because a promise nobody recorded becomes a dispute nobody can settle.

Payment behavior belongs on the account, not in the aging report

The aging report tells you what is overdue. It does not tell you why, and the why is stable per customer.

Some customers pay on time and query nothing. Some pay slowly and always have. Some pay quickly once an invoice is accepted and the acceptance takes three weeks. Those are three different situations and only the first two look alike on a report.

What to record: their actual pattern, what typically delays an invoice, who processes it, and what has previously got one moving.

That turns collections from a chase into a process, and it means the person who picks up the account after a handover does not have to rediscover it over two quarters.

Record decisions and promises at the moment they happen

The habit that prevents most account disputes.

A customer declining a recommendation, agreeing to a rate, asking for a different invoice format, or accepting a longer response time on a particular site. Each is a decision, each has consequences later, and each is currently in an email or a memory.

Where it belongs is on the account with a date, in a sentence. "Declined seal replacement on the walk-in, 14 March, quoted at the time" takes ten seconds and settles a conversation eighteen months later.

The equipment version of this belongs on the equipment, and the commercial version belongs on the account. Both are worth the ten seconds and only the first tends to get it.

Site notes are the highest-value thing nobody writes down

And they save more time per year than any other record here.

Which entrance, where to park, what time you can get in, where the isolators are, who holds keys, which unit trips a shared breaker, and which manager to avoid interrupting during service.

A technician who has covered a site for years knows all of it and a covering technician knows none of it, which is why the first visit after a handover takes forty minutes longer than it should.

Capture it on the first visit to a new site as a matter of course, and add to it whenever somebody learns something the hard way.

What not to keep

Three things, and the first two are common.

Personal opinions about individuals. A note calling somebody difficult is a note you would not want read aloud, and it will eventually be read by somebody it was not written for.

Anything you would not put in writing to the customer. The test is whether you would be comfortable if they saw it, because occasionally they do.

And duplicates of what is already on the equipment. An account note describing a repair is a second version of the truth that will diverge from the first.

Structure it so a group is one customer

The structural decision that makes all of this usable on chain work.

A restaurant group is one customer with many service locations, not many customers. Get that wrong and the account-level knowledge fragments across forty records while the equipment sits under whichever one somebody typed first.

The exception is franchising, where separate legal entities operate under one brand. Those genuinely are different customers and the test is who signs the check.

Roopairs syncs clients and service locations to QuickBooks as distinct objects, which is what keeps a group as one account in the books as well as in the field system.

What this is worth

Three moments, and all three are expensive without it.

A handover, where a covering technician or a new account manager starts from a record rather than from nothing. A dispute, where a dated note settles what was agreed. And a renewal, where knowing what the customer cares about is most of the preparation.

None of it is exotic. It is a handful of fields on the account and the site, filled in by the people who already know the answers, at the moment they learn them.

The test of whether you have it: pick an account and ask somebody who has never worked on it to prepare for tomorrow's visit. Whatever they cannot find is what currently lives in a head.

Roopairs runs a product tour where you can see clients, their service locations and the equipment records beneath them.

What service companies in the trade say

“We came over from another platform, we spent over 2-years on the other platform, trying to make it work for us but it never clicked. So far in the first six months of use on Roopairs, things are clicking and working like we haven't seen before. Jobs are easier to keep track of, invoicing is simpler, our techs found this platform is more fluid to use.” — Greg Austin

Also worth reading

• Chart of Accounts for an Equipment Service Firm
• Client Portals: What Customers Should See
• The future of IoT for commercial kitchen repair companies

Frequently asked questions

What is client history as distinct from equipment history?

Equipment history is what happened to a piece of equipment. Client history is who decides, what they are sensitive about, what was promised, how they pay, and which of their sites is difficult. The first gets kept properly and the second usually does not.

Where should each type of information sit?

The equipment holds manufacturer, model, serial, service history, parts and warranty. The site holds access and quirks. The account holds decision-makers, limits, payment behavior and commercial context. The contract holds covered equipment, intervals and rates.

What lives only in somebody's head?

Who actually decides, what the customer is sensitive about, what was promised verbally, how they behave when something goes wrong, and which of their sites is difficult and why. The verbal promise is the one that causes real damage.

What should be recorded about payment?

Their actual pattern, what typically delays an invoice, who processes it, and what has previously got one moving. An aging report shows what is overdue and not why, and the why is stable per customer.

What should not be recorded?

Personal opinions about individuals, anything you would not put in writing to the customer, and duplicates of what is already on the equipment. The test for the second is whether you would be comfortable if they read it.

How should a restaurant group be structured?

One customer with many service locations. Getting that wrong fragments the account knowledge across forty records. The exception is franchising, where separate legal entities operate under one brand and the test is who signs the check.