Customer Support· 3 min read· By The SpideyChat Team

Taking Over an Existing System Questions

A customer wants somebody else to service a system they did not install. A checklist for the takeover.


A business asks a new company to take over its alarm maintenance. The relationship with the previous installer has broken down.

The system is an older model, nobody has documentation, several devices are unlabelled and the previous company will not provide the engineer code.

Taking on the contract without an inspection would mean agreeing to maintain something nobody can fully access, which is a commitment with no defined limit.

1. Inspect before agreeing anything

What is installed, its age, its condition, how it is configured and whether programming access is available. Quoting a takeover without this is quoting for an unknown.

2. Establish whether the engineer code is available

The most common obstacle. Where the previous company retains it, options narrow to a default reset where possible or a panel replacement.

3. Explain the code position to the customer honestly

Why it matters, what it prevents and what the options are. Customers assume a system they paid for is theirs to have serviced by anybody.

4. Check whether a default reset is possible

On some systems and not others, and frequently requiring physical access to the panel. This is the route that avoids a replacement where it exists.

5. Document the system as it is

Devices, locations, zones, wiring and anything unusual. This documentation is a genuine deliverable and it is what makes future maintenance possible.

6. Check the age and support position

Whether parts remain available and whether the manufacturer still supports it. A system with no available parts is a maintenance contract with a hidden end date.

7. Check the communication path

Where monitoring is involved, how the panel communicates and whether that path still works. Failed communication is a silent failure that only appears at a takeover.

8. Check the battery and device condition

Backup batteries, sensor condition and anything failing. A system nobody has serviced for years will need work before a maintenance contract makes sense.

9. Quote the remedial work separately

What is needed to bring it to a maintainable condition, distinct from the ongoing contract. Bundling them makes the contract look expensive and the work invisible.

10. Be honest where replacement is the better option

An old system with no access, no parts and failing devices is frequently better replaced than maintained. Saying so clearly is better service than an unsustainable contract.

11. Explain what the customer will hold afterwards

Codes, documentation and access, so that the same situation does not recur with the next change of supplier.

12. Handle the previous company professionally

Regardless of the circumstances. Cooperation saves time and the relationship between installers is smaller than anybody expects.

13. Set the contract terms clearly from the start

What is covered, response times and what is charged separately, which is the ground in maintenance contract and service questions.

14. Answer the takeover questions at the enquiry

An assistant that asks what system is installed, how old it is, who installed it, whether documentation or codes exist and what the customer actually wants lets a company decide whether to survey before committing to anything. The same handover problem appears in onboarding and documentation questions from new clients, the monitoring position in monitoring and response questions security firms hear, and the conversation handover in using the live inbox taking over a chat. See features, start at try, and the sector view sits under security companies.

Frequently asked questions

Can a different company service an existing alarm system?
Frequently yes, depending on the system type, whether programming access is available and whether the installing company holds codes that have not been provided.
What is an engineer code?
A programming level access code, which some installers keep rather than providing, and without which a system cannot be fully reprogrammed or in some cases properly serviced.
What should happen before a takeover is agreed?
An inspection establishing what is installed, its condition, whether access is available and what would be needed, because agreeing to maintain an unknown system is a commitment with no boundary.

Want a 24/7 AI Employee for Your Website?

See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.

No obligation. We will review your website and show you how SpideyChat could work for your business.

Keep reading