Mobile Device Support

The regional manager at Acme called the desk from a car park. His phone had stopped showing work email on Friday and he had only noticed on Monday. That told the technician two things: the password had been changed on Friday, and the weekend had been quiet. Then he mentioned, as an aside, that it was his own phone and that his daughter also used it. He had just found a game on it he did not recognise. The technician fixed the mail in four minutes and spent the next twenty, gently, on the other two things. They were not tickets but were the reason there would be one.

This series is about the device that is in everyone's pocket and only partly in the desk's remit. It covers what the desk supports on a phone and what it does not. That is drawn as three rings so the boundary can be said kindly. It covers enrolment and setup without a visit, in plain words and without a product name. It covers email and calendar on mobile, the recurring tickets and the password change that causes most of them. Then come lost and stolen devices and the first hour, where the decisions are about data, not hardware. It covers BYOD boundaries in practice, including what the organisation genuinely cannot see on a personal phone. And it covers reducing mobile tickets with a standard device, a guide and a reminder.

Articles in This Series

• What the Desk Supports on a Phone, and What It Does Not
  Company phone against personal phone, the apps the desk owns against everything else, the three rings of support, how to say it kindly, and the mobile support scope.
• Enrolment and Setup Without a Visit to the Desk
  The enrolment steps in plain words, the self-service guide, and the work account on the device. Covers the second factor set up at the same time, the starter's first-day kit, and the guide outline.
• Email and Calendar on Mobile: The Recurring Tickets
  Sync stopped because the password changed, the certificate prompt, the full mailbox, and the calendar in the wrong time zone. Also covers the notifications that stopped, the checks in order, and the checklist.
• Lost and Stolen Devices: The First Hour Is About the Data
  The report, the lock-or-wipe decision and who makes it, the password reset and session revocation, the carrier, the police report where required, discretion, and the lost-device runbook.
• BYOD Boundaries in Practice: What the Desk Can and Cannot See
  What the organisation can and cannot see or do on a personal phone, and the work-profile idea. Covers the honest explanation to a worried user, the leaver's personal phone, and the BYOD explainer.
• Reducing Mobile Tickets: Standard Device, Guide and Reminder
  The standard device, the setup guide, the password-changed reminder, the authenticator-on-a-new-phone runbook, measuring the category, and the mobile self-help index.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.