Self-service Devices
Part of Retail equipment maintenance software
Recording faults in customer-facing devices
Record the device, observed symptom, customer effect and service state so retail equipment faults reach the right responder.
Record a fault while the symptom and its effect on shoppers are still clear. Identify the device, describe what happened without diagnosing it prematurely and say whether staff can provide the service another way. The next person should be able to act without asking a shopper to repeat the problem.
Identify the device and interrupted task
Use a stable asset ID as well as the store and current position. “Screen at front counter” can become ambiguous after a move or replacement.
Record when the problem was first noticed, the task attempted, the visible result and whether it happened again after a permitted retry. Avoid entering customer names, card details or images of personal information merely to describe a technical symptom.
For example, “product-search kiosk at the entrance restarted after a shopper selected a size; staff lookup still worked” records an observation and its service effect. “Bad network card” is a diagnosis that needs investigation.
If a device appears unsafe or may have been altered, follow the store’s stop-use and escalation procedure instead of asking staff to reproduce the fault.
Field / What to record
- Asset and place
- Asset ID, store and current position
- Observed symptom
- Attempted action and visible result
- Customer effect
- Task interrupted and any available assisted route
- Current state
- In use, restricted or out of service under store procedure
- Evidence
- Error text, time and permitted supporting image, if useful
- Next owner
- Team or supplier expected to respond
These are suggested fields, not a universal software form. A powered-on device may still be unable to complete its customer task. Do not close a report merely because its display has returned.
Reporting vs. diagnosing: what to record
- Do record
- Observed symptom: 'product-search kiosk at entrance restarted after shopper selected a size'
- Do not record
- Diagnosis: 'bad network card' – this requires investigation
Benefits and risks of including images in fault reports
- ProsVisual evidence helps technicians identify issues quickly, especially for display or interface problems
- ConsRisk of capturing personal data; avoid images of customer details, faces or payment cards
Distinguish duplicate reports from new failures
If several colleagues report one continuing outage, link their observations to the active case while preserving times and symptoms. If the device was restored and the symptom later returns, record a new failure event and link the earlier work.
A return visit where the task never worked again belongs to the continuing case. Multiple messages about one outage are not multiple breakdowns.
MaintainX documents an asset field on work orders and an asset page with associated work orders. On a parent work order with sub-work orders, its asset field disappears and assets are specified on the sub-work orders.
Dynamics 365 Field Service documents associating work-order incidents with customer assets. In either workflow, staff must link the record to the correct physical device.
Close the loop with the store
A technician’s note should separate the reported symptom, established cause if any, action taken, parts changed and check performed. Say when no cause was found.
Have the responsible store role confirm the customer task works before returning the device to normal use, and tell colleagues whether a workaround or watch period remains.
Review a sample of reports after the process starts. Check whether responders can find the device, understand the service effect and see the outcome.
Change the form or training where information is lost; extra fields are useful only when they improve the response.
Key metrics for evaluating fault reporting effectiveness
- Response clarity ratePercentage of reports where responders could identify the device and task without asking shoppers
- Workaround documentation rateProportion of reports where alternative service methods were recorded
- Store confirmation rateHow often the responsible store role confirmed task functionality before reactivation
