A shop safe that was last serviced "a while ago"
A retailer rings because their safe will not open in the morning. Your engineer attends and gets it working. While there, they realise your firm installed that safe and used to service it every year. The last service was three years ago. Nobody sent a reminder, because the reminder system was a diary the old office manager kept, and it went when she did.
Across the area there are dozens of safes like that: in shops, pubs, surgeries, offices and homes, installed or serviced by your business at some point. Each one is a small annual visit you could be booking in a quiet week. Most of them are now invisible.
Service records scattered across years of paperwork
Safe work is a sideline for many locksmith firms, which is exactly why its records are the weakest. Installations are in the accounts as invoices. Services are in job sheets. The details that matter for the next visit, such as the make, model, lock type and where the safe actually is in the building, are in engineers' heads.
- There is no list of safes, only a list of invoices.
- Service intervals are agreed verbally and never written down.
- Reminders depend on one person's diary.
- Access details for the safe's location (which room, who holds keys, opening hours) are not recorded.
- Previous service notes are not available to the engineer on the next visit.
Lapsed services and lost repeat work
Each lapsed service is repeat revenue that did not happen, and repeat revenue in quiet weeks is what keeps engineers busy. When a customer eventually has a problem, they may not remember who serviced it, and another firm gets the call. The records also matter for customers who are asked about their safe by their own insurer, and who expect you to be able to say when it was last looked at.
A safe register that books its own services
We build a register of safes linked to your customers and your job system.
- Each safe has a record: customer, site, location in the building, make, model, lock type, installation date, and the service interval agreed with the customer.
- We populate the register from your past invoices and job sheets, extracting safe jobs so you start with what you already have rather than a blank list. Your engineer checks the list before it goes live.
- Services come due on the register and the system sends the customer a reminder with a booking link, or adds them to the office's call list, depending on how you prefer to work.
- Services can be grouped by area, so an engineer can do several in one day.
- On the visit, the engineer opens the safe's record on their phone, sees the previous notes and records what was done, with photos if needed.
- The customer receives a service record by email after the visit, generated from the job.
| Information | Where it lives now | Where it lives after |
|---|---|---|
| Safe make and model | Engineer's memory | Safe record |
| Location in the building | Engineer's memory | Safe record with access notes |
| Last service date | Old job sheet | Safe record, with history |
| Next service due | Someone's diary | Automatic reminder list |
| Service notes | Paper, if anywhere | Attached to each visit |
What a service involves and how often it should happen is for your engineers and the manufacturer's guidance to decide. The register records and schedules whatever you set.
Quiet weeks with booked work in them
Services come round on time, so the customer never has to remember. The office can see which services fall in the next month and group them sensibly. Engineers arrive knowing what they are looking at. And customers who get a reminder, a tidy visit and a service record are the ones who ring you first when something goes wrong.
Is your safe work like this?
- You could not list the safes you have installed or serviced.
- Service reminders depend on one person remembering.
- Engineers arrive without knowing the make or model.
- Customers call with faults on safes that were never serviced again.
- Safe work is mixed into general invoices with no separate record.