Remote disable does not survive a factory reset
We built remote disable for rented hardware. It is genuinely useful, and against an actual theft it is worth nothing.
What software control gives you
Being able to disable a device remotely covers the common case well: someone keeps the equipment past its return date, ignores reminders, and is not attempting anything clever. Disabling it usually produces a phone call, which is the outcome you wanted.
What it does not survive
Anything running on the device is defeated by a factory reset. Configuration goes, your agent goes, your keys go. Thirty seconds with a paperclip returns the hardware to a working state under their control.
If your recovery plan is a software flag, your recovery plan is an honesty system.
Control the part they cannot reset
For a connected device, the service is the leverage, not the hardware. Barring the SIM or disabling the connection is done at the provider, cannot be undone from the device, and turns an expensive item into a paperweight regardless of what firmware it is running.
Consider what the device is actually worth without your service. If it is worth a lot, expect to lose some. If it is worth very little, the deterrent does most of the work for you.
Make the financial route the real one
Hold a payment method with the customer's agreement, state the non return charge clearly up front, and apply it consistently. This is the mechanism that actually recovers value. Everything technical is there to prompt the return, not to enforce it.
Layer them in the right order
- Reminders before the due date, which resolve the vast majority
- Escalating contact after it
- Software disable, as a prompt to make contact
- Service level bar, for genuine non return
- Charge, applied predictably rather than at discretion
Building step three first is tempting because it is the interesting engineering. Steps one and five recover far more.
Need help with any of this?
These notes are free and always will be. If you would rather someone just set it up, or you are stuck on something similar, get in touch at hello@opsira.io.