Callback register

Job register

The return visits on a job, in one place — so a pattern is visible instead of remembered by nobody.

Rows you can count, and nothing more

You can see how many rows there are. That is the entire arithmetic in this tool, and it is deliberate.

There is no callback rate here, no percentage, no per-technician figure, no ranking, no league table, no quality grade and no benchmark. A number like that looks objective and is not: it depends on what anybody chose to log, on which jobs were hard, and on who was sent to the difficult ones. Attached to a person’s name it becomes a performance measure built from a list somebody kept unevenly — and that is a bad thing to hand anybody.

It finds no fault

Nothing here characterises a callback as somebody’s error, as poor workmanship, as negligence or as a warranty matter. Why a job needed a second visit is a judgment — sometimes it is a part, sometimes the customer described something else, sometimes it is genuinely a miss. The record holds what happened; the reading of it stays with you.

Kept against the job

A callback belongs to the job it came back on, by that job’s stable id. The original ticket number is a field on the row, so the two ends of the story stay connected.

Kept alongside: Service call report · Service plan renewal register · Work order

A register of return visits, kept per job on your device. Rows can be counted and that is the whole of the arithmetic: there is no callback rate, percentage, per-technician metric, ranking, quality grade or benchmark anywhere in this product. It makes no finding about fault, liability, negligence or workmanship. Everything runs on your device.

Questions people ask

Will it work out my callback rate?
No. There is no rate, percentage or benchmark anywhere in this tool. You can see how many rows a job has, and that is all the arithmetic there is. A callback rate produced from an unevenly kept list looks objective and is not.
Can I see callbacks per technician?
No, and that is deliberate. There is no per-person metric, ranking or league table in this product. The record holds who attended the return visit because that is a fact about the visit — it is not turned into a measure of anybody.
Does it say whose fault a callback was?
No. It characterises nothing as error, poor workmanship, negligence or a warranty matter. It records why you went back, what was found and what was done. The judgment stays with you.
How is a callback linked to the original job?
By the job's stable id, with the original ticket number recorded on the row. Renaming a customer or a job moves nothing.
Where is the data kept?
Without an account: in this browser, on this device, with nothing uploaded and nothing to sign up for. Signed into a CompliMaint workspace, the same records are also stored for that workspace — which is what puts them on your other devices and in front of your colleagues — and the screen says which of the two you are looking at.