x-hoppers dynamic variables use cases
This document describes use cases for passing dynamic variables in broadcast messages using Smart Notifications API.
Developer documentation: Running x-hoppers Parameterized Actions via API | Wildix Developer Docs.
Created: February 2025
Updated: March 2025
Use case 1: Request assistance at a self-checkout kiosk
Actors:
Customer
Store associate
Precondition:
The customer is at a self-checkout kiosk.
The customer requires assistance.
Postconditions:
A notification is sent to the store associate's headset indicating that assistance is required.
The store associate arrives at the specific self-checkout kiosk to assist the customer.
Main Flow:
The customer approaches the self-checkout kiosk.
The customer faces an issue and decides to request assistance.
The customer presses the "Request Assistance" button on the self-checkout interface.
The kiosk system generates a URL associated with that specific device.
The system sends a notification to the store associate’s headsets, indicating the location (self-checkout kiosk identifier) and the request for assistance.
The store associate hears the notification and acknowledges it.
The store associate proceeds to the specified self-checkout kiosk to assist the customer.
Use case 2: Click-and-collect
Actors:
Customer
Store associate
Preconditions:
The customer needs to pick up their order.
The customer inputs their order number or name.
Postconditions:
An announcement is made through the store associate’s headset indicating that the order is ready for pickup.
The store associate prepares the order for the customer.
Main Flow:
The customer arrives at the store and accesses the tablet, the retailer’s proprietary app or web page via QR code.
The customer inputs their order number or name.
The system retrieves the order details and generates a notification.
The system plays an announcement through the store associate’s headsets, stating, “Order number [order number] is ready to be collected by [customer name].”
Store associate hears the announcement and prepares the specified order for the customer.
Use case 3: Pharmacy prescription pickup
Actors:
Customer
Pharmacist
Preconditions:
The customer needs to pick up their prescription.
The customer enters personal details.
Postconditions:
Important patient information is played through the pharmacist's headset to prepare the prescription.
The pharmacist prepares the prescription without the customer having to speak to the pharmacist first.
Main Flow:
The customer arrives at the pharmacy and accesses the tablet, the pharmacy’s proprietary app or web page via QR code.
The customer enters their personal details (name, date of birth, etc.).
The system retrieves the prescription details associated with the entered information.
The system plays an announcement through the pharmacist’s headset, stating the patient's name and other relevant details (e.g., “Prescription ready for [customer name], address [customer address].”).
The pharmacist hears the announcement and retrieves the prescription without needing to ask the customer for information.