An IT or fleet team should evaluate support and lifecycle by testing how the service behaves on the worst day of a device’s life, not the first. That means knowing who answers users for each fleet group, how operating system and model changes are handled over years, and whether recovery and offboarding have been rehearsed on real hardware. Otukan agrees support lines with you and any partner before rollout, reviews OS releases on your own models and tests lost-device, leaver and retirement paths during the pilot. This applies to Android and Apple devices in each ownership mode. Service hours and escalation terms are agreed per contract.
This page is part of the evaluation and lifecycle collection.
Support by fleet group
Support needs differ by who owns the device and what it is for. Settle them group by group.
| Device group | Typical support need | Lifecycle pressure |
|---|---|---|
| Corporate-owned, general use | Password resets, lost phones, app problems | Refresh cycles and OS updates on mixed models |
| Dedicated or kiosk devices | Fast replacement so the task continues | Long service lives on a fixed OS image |
| Personally owned, work profile or User Enrollment | Work app access without touching personal data | User-driven OS updates and device changes |
Operating systems
Android and Apple devices age differently. Android support depends on each maker’s update policy per model; Apple publishes its own device support for each OS release. Otukan records both per model in your inventory rather than applying one rule to the whole fleet.
Privacy on personal devices
Support on a personally owned device has limits the user can see. Help desk staff can find the device, reset work access and remove work data. They cannot read personal apps, photos or messages, and the enrolment mode keeps those out of the management service in the first place. Otukan writes those limits into the support script, so staff and users hear the same answer.
Operating model
A support arrangement is only as clear as its lines and its access rules.
Support lines
| Line | Usually held by | What it handles |
|---|---|---|
| First line | Your help desk | User contact, device look-up, lock and passcode reset |
| Second line | Your fleet administrators, or a partner where agreed | Group moves, policy questions, on-site handling |
| Third line | Otukan engineers | Enrolment faults, policy delivery, platform changes, the service itself |
Who holds each line is agreed per contract and written into the responsibility matrix. For how that matrix is built, see ownership and partner scope.
Access and change control
Otukan support reaches your tenant only when a case needs it, with your approval and a time limit, and every action is logged. Who hosts and operates the tenant is set out on MDM deployment options. Policy changes travel the same way whoever makes them: pilot group first, then the wider fleet once devices confirm the result.
Integrations over time
Directory, certificate and ticketing connections age too. Otukan includes each connection in lifecycle reviews, so an expiring certificate or a changed directory attribute is caught in the review, not in a user’s failed enrolment.
Ending the service
Lifecycle includes the end of the contract. Export formats, deletion confirmation, the handover period and the release of devices from bulk enrolment are agreed before rollout and rehearsed once on a pilot tenant, so leaving is a procedure rather than a negotiation.
Lifecycle, rehearsed
Evaluate every stage with a named workflow on pilot devices, and record the result.
- Provisioning. A new device reaches its user, enrols into the right group and receives policy and apps without help desk involvement.
- Change. A policy change reaches the pilot group, one device is made to fail it, and the pause and rollback work as written.
- Recovery. A device is reported lost, locked, wiped and replaced, and the replacement enrols into the same group.
- Offboarding. A leaver’s corporate device is reset and returned to stock; a leaver’s personal device loses its work data and nothing else.
- Retirement. A model at end of support is replaced, and the old units are released from bulk enrolment.
Each rehearsal produces a dated record with devices, OS versions and the person who confirmed it. Those records become the baseline for the reviews Otukan holds with you after go-live. Moving an existing fleet in is covered on MDM migration.