Handle mobile PC requests
Use mobile PC requests as a staff-controlled queue for players who want a station, package, or branch response.
Mobile requests help staff organize demand without automatically starting sessions or bypassing payment rules.
Before you start
- Mobile request surfaces are enabled for the branch.
- Staff have a routine for checking request queues.
- PC availability is accurate in the Controller.
Explain what a request means
A mobile request is a signal to staff, not a guaranteed booking or automatic session.
- Tell players that staff confirm availability.
- Keep payment or balance rules separate from the request itself.
- Use request status to reduce counter confusion.
Review the queue
Requests are useful only when staff check them during active operation.
- Assign cashier or floor staff to watch requests during busy time.
- Check the requested station or station type before responding.
- Clear stale requests when players leave or change plans.
Respond and start the next action
After reviewing a request, staff should respond through the branch process that matches the player and payment state.
- Approve, reject, or resolve according to branch policy.
- Start a paid session only after payment or balance rules are satisfied.
- Use player account context when the request comes from a linked player.
Verify it worked
- Staff can see mobile PC requests in the Controller.
- Requests do not create sessions without staff approval.
- Resolved requests no longer clutter the active queue.
Troubleshooting
Requests are missed during rush hours.
Assign request review to a role and include it in shift handoff.
Players think requests reserve a PC automatically.
Clarify branch wording and train staff to confirm availability before promising a station.