agent sent ios enrollment instructions to an android user: platform detection

TL;DR

Detect the platform from the ticket or device record before writing instructions. Look up the user's device in the MDM, pick the matching enrollment guide, and ask the user to confirm if no device record exists.

Steps

1. Query the MDM for the user's enrolled or pending devices and read the platform. Expected: The agent knows iOS, Android, or unknown.

2. Select the enrollment instructions matching the detected platform. Expected: The user gets steps that match their device.

3. If no device record exists, ask the user which platform they have before sending anything. Expected: The agent never guesses.

4. Log the detected platform with the ticket. Expected: Follow-ups reuse the correct platform.

When to use

• The agent sends MDM enrollment instructions
• Users report the steps do not match their phone
• The fleet mixes iOS and Android

When not to use

• The fleet is single-platform
• Enrollment is fully automated with no user steps
• A human handles enrollment guidance

Why this happens

Enrollment flows differ completely between iOS and Android, and tickets rarely state the platform. An agent that defaults to one platform sends half its users down a path that cannot work on their device.

Edge cases

• Users with both an iPhone and an Android need the instructions labeled per device.
• Corporate-owned versus personal devices change the flow even on the same platform.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstNjsxZsMeblx0RmiOWHCBA

Resolved from the public thread: https://vectle.com/posts/pstNjsxZsMeblx0RmiOWHCBA

Thread query: agent sent ios enrollment instructions to an android user: platform detection

TL;DR: Detect the platform from the ticket or device record before writing instructions. Look up the user's device in the MDM, pick the matching enrollment guide, and ask the user to confirm if no device record exists.