Handle player PC requests
Review and respond to player requests for PCs so staff stay in control while customers get a smoother flow.
Player requests become a staff-managed queue instead of a crowd at the counter or unmanaged customer expectation.
Before you start
- Enable player-facing request features only after core session flow works.
- Train staff to check requests during busy hours.
- Keep PC availability accurate in the Controller.
Use requests to reduce counter pressure
Requests help players signal interest, but staff still decide whether a PC can be assigned or started.
- Treat requests as signals, not automatic session starts.
- Check station availability before approving or responding.
- Tell players how requests are handled at the branch.
Respond from the Controller
Staff should review the request, choose the correct action, and keep the floor controlled.
- Accept, reject, or resolve requests according to branch policy.
- Use registered player identity when available.
- Avoid starting sessions without confirming payment or balance rules.
Review busy-hour behavior
Requests can be useful during peak time, but only if staff check and resolve them quickly.
- Assign someone to watch requests during busy periods.
- Clear stale requests after the customer leaves or changes plans.
- Adjust customer instructions if requests create confusion.
Verify it worked
- Staff can see new requests in the Controller.
- Requests do not bypass payment or staff approval.
- Stale requests are cleared during shift handoff.
Troubleshooting
Players think a request guarantees a PC.
Explain request handling and keep staff approval visible in the branch process.
Requests pile up unseen.
Make request review part of the cashier or floor staff routine during busy hours.