Deliver exceptional customer support

Most service operations do not start out disorganised. They start small, with one person who remembers everything, and the memory stops scaling somewhere around the fourth technician.

The first symptom is usually a customer chasing an update nobody can give. The second is a technician arriving without the part he needs, because the previous visit was never written down anywhere he could read it.

A ticket is a small thing on its own. What makes it useful is that it belongs to a customer and, where it matters, to a serial number, so the history of one machine survives the technician who worked on it and the year it was bought.

Preventive maintenance is the part of after-sales that pays for itself and the first part to slip, because nothing bad happens on the day a visit is missed. It happens three months later, at the customer's busiest hour.

For anyone selling a maintenance contract the same schedule is a commercial record. Visits owed against visits made tells you whether the contract is being honoured, and whether it was priced sensibly in the first place.

Anyone who has run a workshop knows the pattern. A large share of incoming calls are customers asking where their unit is, and each one costs somebody the twenty minutes it takes to go and find out.

Automatic updates remove most of those calls. The rest get answered in seconds, because the ticket carries the item, the reported fault, the person handling it and the last thing that happened to it.

Parts come out of inventory as they are used, which keeps the spare parts position honest and puts a real cost on the job. Labour is recorded as time against the ticket. Neither is difficult on its own, and together they turn service from an impression into a number you can act on.

The first month of that data tends to be uncomfortable reading. Warranty work that everyone assumed was small turns out to consume a technician a week, or a product line that sells well is quietly the one generating half the callbacks. Both are worth knowing before the next purchase order goes to the supplier.

The honest caveat: this only works if jobs are closed on the day, not on Friday for the whole week. A technician writing up five jobs from memory produces a record that is roughly right and useless for costing anything.

That habit has to be set in the first weeks, and it is easier when closing a job is short. Ask for the parts, the time and one line on what was done. Anything longer gets skipped during the week and invented afterwards.

Warranty reminders are the simplest version of this. A contract or a warranty approaching its end date is a scheduled conversation instead of a lapse somebody notices six months late.

The more useful pattern is the one across customers. When the same fault shows up on the same model across several jobs, that is a supplier or purchasing conversation, and it only becomes visible when the service data sits in one place rather than in each technician's head.