Daily operations

Configuration done, doors open — this section is about the working day: serving the queue at the counter and keeping an eye on the branch.

Two very different days happen at once:

The operator's day

An operator signs in to the operator console at their service window and works the queue: call the next client, serve them, tag the visit with its reasons, complete — then again. Around that loop sit the tools for the exceptions: repeating a call, marking a no-show, skipping, transferring to another service, handing a client to a colleague, adding a walk-in by hand, and managing their own breaks and back-office time.

Work the operator console walks through all of it.

The manager's day

A location manager opens the location manager console to see the branch's pulse — queue depth, tickets served, wait times, operator performance — and to react when service degrades: SLA thresholds per service raise an alert the moment a client waits too long. An organisation admin gets the same at-a-glance picture across every branch in the management console, plus the audit log that records who did what.

Follow the branch through the day covers both consoles.

One account, several consoles

The consoles are separate surfaces with separate addresses, but not separate accounts: anyone who reaches more than one of them — an organisation admin, who has both management consoles, or an operator who also holds a management level — signs in once and moves between them with the console rows in the account menu at the top right. Roles and invitations are covered in Team.