Login Requests

Login requests let a walk-in guest ask the operator to open a client PC for a postpaid session. The guest picks a duration on the idle screen. The cashier approves or rejects the request from the server. This removes the need for the cashier to walk to each PC to start a session by hand.

How a Guest Sends a Request

When login requests are enabled, the client login screen shows an Ask to open this PC button next to the customer login form. The guest taps it and sees a dialog with:

• Duration options. Each option shows a preset number of minutes and the estimated price. The server quotes every price live from the active pricing schedule, so the guest sees the same figure the operator sees.
• Postpaid notice. A reminder that the session is paid afterwards. The guest pays at the cashier when the session ends.

The guest selects a duration and taps Send request. The idle screen then shows a waiting state until the operator responds. The guest can cancel the request while waiting.

The Operator Queue

Each pending request appears on the server main page in two places:

• Toast cards. A stack of cards in the corner of the main page shows the newest requests. Each card lists the PC name, the requested duration, the estimated amount, and how long ago the request arrived. Up to three cards show at once. Extra requests collapse into a "more" button that opens the full queue.
• Queue dialog. A dialog lists every pending request with the same details and the same actions.

Approving a Request

Select Approve on the card or in the queue. A confirmation asks you to open the PC. Confirming starts a normal postpaid session on that PC for the requested duration. The final charge is calculated from live pricing when the session ends, exactly like a session a cashier starts by hand. The quoted amount is an estimate for reference only.

Rejecting a Request

Select Reject to open the reject dialog. You can type a reason the guest will see. If you leave the field blank, the guest sees your configured default rejection reason. If no default is set, the guest sees the standard message asking them to contact the cashier.

Automatic Cleanup

A pending request is removed on its own when it is no longer valid. This keeps the queue accurate:

• The guest cancels the waiting dialog.
• The guest walks away and the client disconnects.
• A session starts on that PC by any other means, such as a manual start or a member login.
• The PC is already busy when the request arrives. The server refuses the request instead of queueing a row for an open PC.

Enabling Login Requests

Login requests are controlled in Settings > Clients. Turn on Enable login requests from clients to show the request button on client idle screens. When the feature is on, a Default rejection reason field lets you set the message guests see when you reject without typing a reason. See Clients Settings.

Real-Time Updates

The operator queue updates over the TCP event stream. New requests appear at once without a page refresh. When one terminal approves or rejects a request, the queue clears on every terminal.