Remote lock is the wrong first question
In phone rental, installment and enterprise asset management, a supervision lock is often treated as the last line of device security. Yet the capability behind that label varies widely. Some solutions use the system-level management provided by Apple, Google or the handset maker; others are ordinary apps that restrict users through overlay windows, accessibility permissions, device admin or a custom lock screen. They can look alike while a device is running normally, then diverge sharply after a factory reset, a firmware flash, safe mode, an OS upgrade, a network outage or a backend fault. The useful question is not "can it lock the device remotely?" but "after the device is reset, flashed, disconnected or attacked, can the organisation still identify, control and recover it?"
Check how the device is enrolled
For iPhone and iPad, the stronger path is Apple Business Manager or Apple School Manager with Automated Device Enrollment (ADE). ADE configures a device from first power-on, can prevent the user from removing the management profile, and normally places the device in supervised mode. A profile downloaded from a web page, or a lock app alone, is not equivalent. Check that Settings shows the device as supervised, the profile cannot simply be deleted, the serial is in the organisation's Apple Business device library and assigned to the intended MDM server, and that reactivation after a wipe brings back the remote-management screen.
For Android, look for Fully Managed, Device Owner, Android Management API, Google zero-touch or vendor enterprise capabilities such as Samsung Knox. Google defines Fully Managed as management of the whole device, not one work profile or one app. An APK using accessibility or device-admin permissions is not the same as system-level Device Owner.
Verify recovery and communication limits
- Factory reset. A device added to Apple Business manually through Apple Configurator may have a 30-day temporary release window; confirm it has passed. On Android, demand a supported brand list, model list, minimum OS version, domestic versus international differences and the outcome after flashing official firmware or unlocking the bootloader. "All Android devices" without boundaries is not an answer.
- Offline reality. Remote commands normally travel through APNs and require connectivity. A device with no SIM and no Wi-Fi may not receive a new instruction immediately — a communication boundary, not proof of insecurity. Insist on both online control and local policies that survive a short outage or reboot.
- Closed loop. "Command sent" is not "command executed". The console should distinguish created, awaiting push, received, retrieved, succeeded, failed, temporarily unable and timed out.
Test that a locked device stays locked after reboot, that queued commands run after reconnection, and that status updates after a SIM swap. Be cautious of any claim of real-time new commands on a fully offline device. The final scope is subject to the confirmed product specification and service agreement.
