The question that exposes it
A customer calls with a device. The agent needs two answers before anything else can happen: is this unit still under warranty, and what has already been done to it. If either answer takes more than a moment, the company does not have an after-sales system — it has a filing habit.
Warranty dates can be reconstructed from an invoice; repair history cannot, if it was never recorded against the unit. So the same fault gets diagnosed from scratch for the third time.
Want to know how this works out for your company? Send us the question as you would ask it.
The record has to belong to the unit
Most support tools organise around the ticket or the customer. Both are wrong for a physical product: a customer can own several units, a unit can outlive several owners, and a ticket is an episode rather than a history. The record has to be keyed to the unit, and it has to answer:
- Which unit is this, by serial number, and who has it now
- When did its warranty start, and on what terms — sale date or delivery date changes the answer
- Every ticket ever raised against it, including ones closed by someone who has since left
- What was replaced, from which stock, and whether that part carries its own warranty
Fault patterns across a model
A fault pattern across a model is quality information, and it almost never reaches anyone who could act on it. Support closes tickets one at a time; nobody looks down the column. When the unit record carries a model, that pattern is a query rather than an investigation.
Scale changes what the gap costs
A support team of three shares context by talking. That stops working once whoever answers has probably never seen this unit before.
On the build behind this article, the support team is over 50 people across more than 10 device models. At that size, "ask whoever handled it" is the operating model — and it is the thing that fails.
What connecting it actually means
In practice this is three systems most companies already own separately: the CRM holding the customer and the sale, the accounting or inventory system holding stock and invoicing, and the support desk holding tickets. The work is not buying a fourth thing — it is making the device a shared record across all three.
When a spreadsheet is enough
If units are low-value, warranty is short and replacement is cheaper than repair, a spreadsheet of sale dates is a rational system. The threshold is repair: the moment it is worth fixing a unit rather than swapping it, the unit acquires a history, and a history needs somewhere to live.