Device Repairs Administration

Overview

Using Device RepairsAssisting with Device RepairsDevice Repairs Administration

The Device Repairs workflow is designed so that users can drop off broken devices securely, and admins can later collect these devices, troubleshoot them, and return them efficiently. This workflow simplifies device repair logistics, reduces downtime, and enhances user convenience without relying on manual intervention.

This article covers setting the workflow up in the FUYL Portal.

Some of these settings depend on the role assigned in the FUYL Portal. If an option doesn't appear, an administrator may need to grant access to it.

Set up a Device Repairs workflow

1. Admin Access

   Browse to the FUYL™ Portal (FUYL.io) and log in with an administrator profile.

2. Create a Device Repairs workflow

   1. Navigate to the Workflows tab and select “Create New.”
   2. Name the new workflow appropriately (e.g., “Staff Laptop Repairs”).
   3. Select “Device Repairs” as the Workflow type and click “Next.”

3. Configure workflow options

   Options for this workflow include (and are all enabled by default):

   Setting	What it does
   Require device ID	The user is required to enter a device ID.
   Require repair reports	The user is required to enter information regarding the repair request.

   Repair reports

   Setting	What it does
   Include "other" repair options	The user is allowed to select “Something else” as a repair option when prompted.
   Include issue description	The user is prompted to describe the issue the device is facing.

   Custom field

   Setting	What it does
   Include custom drop off field	The user is shown a custom step on drop off.
   Large text	Required heading text.
   Small text	Optional supporting text.
   Include user input field	The user must input text before continuing. Their entry appears in any email notifications, webhooks and on the repair dashboard.

   Link workflows

   Setting	What it does
   Link workflows	Select a separate Device Loan or Deployment workflow to link, allowing the user to borrow or collect a new device. If a Loan workflow is linked, the user will be required to return their loaned device when picking up their repaired device. See Dynamic bays for more on optimising utilisation with linked workflows.

   Notifications

   Note: Notification content accuracy relies on the timezone configured in Settings - Account

   Setting	What it does
   Repair dropped off	The email addresses included here will be notified when a device is dropped off. Multiple emails can be added by pressing return.
   Notify user when ready for pickup	The user will be notified by email when a device administrator has dropped off their repaired device.

4. Link user groups (optional)

   Select a subset of user groups authorised to use this workflow. Provisioning must be configured for this feature.

5. Confirm workflow

   Check and confirm the workflow settings.

6. Allocate the workflow to bays

   Before users can opt to deposit devices, the workflow must be allocated via the FUYL Kiosk. See Allocating workflows to bays.

Kiosk button labels are set once per account and apply to every Kiosk. Learn how to apply a custom label.

The workflow will appear on the FUYL Workflows dashboard, displaying weekly usage stats, the number of stations in use, and how many devices are waiting for collection.

Monitor and review in the Repairs dashboard

Device administrators can check on the current and historical status' of repairs in the Repairs dashboard, accessible by selecting the Repairs icon on the left of the FUYL Portal.

The Repairs dashboard is presented in two views;

Broken devices

The Broken devices view displays devices that have either been dropped off by an end user and awaiting collection, or have been collected and awaiting repair. The table includes the following details:

Repaired devices

The Repaired devices view displays devices that have been repaired and deposited in the Smart Locker for collection or devices that have been collected by the end user. The table includes the following details: