Overview
This template responds when a device leaves Kiosk mode unexpectedly. It checks current device status, sends a report to the administrator, and routes the next action to restart, remote support, or on-site handling. The workflow then verifies recovery when a restart is chosen and records the outcome for follow-up.
The Problem This Workflow Solves
Teams responsible for monitored devices need a clear way to respond when a Kiosk exit event appears on a device that should remain controlled. They must check the current device state, review the latest screenshot and health details, and decide whether to restart, hand off remote support, or send an on-site technician.
- Faster review. The report gathers device status and screenshot details in one place for the administrator.
- Clear handoff. The workflow sends the incident to restart, remote support, or on-site handling.
- Post-restart check. The workflow checks the device again after five minutes when restart is chosen.
- Recorded follow-up. The final email captures on-site feedback or the need for manual handling.
Who This Is For
- Device administrators. They review the incident report and choose the next handling method.
- On-site support teams. They receive the handoff when local inspection or recovery is needed.
- Teams managing Kiosk devices. They use this template for devices that should stay in Kiosk mode.
What Sets This Workflow Apart
- Event filtering. It continues only for Kiosk exit events and skips unrelated statuses.
- Context before action. It collects device health, configuration, and screenshot data before asking for a decision.
- Verification after restart. It checks both the restart task and the later device state before closing the incident.
- Branch-specific follow-up. It sends separate reports for remote support, restart recovery, and on-site results.
How It Works
- Receive the Kiosk exit event
- The workflow starts only when AirDroid Business reports a Kiosk status change showing the device is not in Kiosk.
- Collect device context
- It refreshes the screenshot, queries connection and health details, and prepares a report in the selected time zone.
- Ask the administrator to choose a path
- The workflow emails the investigation and waits for a choice to restart, start remote support, or notify on-site staff.
- Run the selected handling method
- Restart sends a device reboot request and checks the result later, while the other options send the corresponding notification or link.
- Confirm recovery or pass back the result
- If a restart is used, the workflow checks again after five minutes; on-site feedback is then compiled and emailed to the administrator.
What You'll Need
- Event source and device scope
- The workflow needs a Kiosk status change event for the target device and the device identifier from that event.
- Notification recipients
- Enter a valid administrator email address and, if used, an on-site technician email address.
- Authorized service connections
- Provide the AirDroid Business and email service credentials needed to query devices and send messages.
- Report time zone
- Select the time zone used for event time, last contact time, and screenshot time in reports.
How to Use
- Step 1. Add the required connections and recipients
- Step 2. Set the report time zone
- Step 3. Attach the Kiosk exit event
- Step 4. Test each handling branch
After import, enter the email addresses and authorize the AirDroid Business and email service connections.
Choose the time zone that should appear in investigation reports and follow-up messages.
Connect the workflow to the Kiosk Running Status event that indicates the device has exited Kiosk.
Use a test device to confirm restart, remote support, and on-site handling before wider use.
