One Back Office for Every Terminal You Run

A single hall can be managed by walking around it. Five halls under three agents cannot. The moment terminals are spread across locations — and especially across other people’s locations — the operator’s real problem stops being games and becomes visibility: which machines are live, what went in, what came out, and whether the count at the desk matches the count in the system.

The back office behind our VLT platform is one interface over the whole structure, from the top of the chain down to an individual spin on an individual machine.

The hierarchy

The system is built as an agent tree rather than a flat list of venues. Five levels, each one able to see and manage everything beneath it and nothing above it.

This structure is the reason the platform suits networks rather than only single owners. If you distribute terminals through other people — dealers holding territories, agents running rooms they own themselves — each of them gets a working back office scoped to their own branch, and you keep a consolidated view over all of it without asking anyone to send you a spreadsheet.

If you run every hall yourself, the same tree still works. You simply occupy more of the levels.

There is no cap on halls or terminals in an account.

Delegating work without delegating money

Three further levels sit alongside the main ones, and they exist so you can hand someone a job without handing them a balance. A sub-dealer does what a dealer does, an engineer does what an agent does, and a sub-cashier does what a hall does — but none of the three holds an independent balance. Each draws on its parent’s.

In practice a technician can service terminals and a floor cashier can run a shift without either of them becoming a separate pot of money you have to reconcile at the end of the week. It is a small distinction that saves a recurring argument.

Live monitoring

The dashboard answers the most-asked questions first, without anyone building a report: which terminals are online right now, what has gone in and come out today, gross gaming revenue, and what currently needs attention.

That set is deliberately short. A back office that opens on forty widgets gets read by nobody after the first week; the useful test is whether the four numbers you check every morning are on the screen when it loads.

Alerts

Conditions worth interrupting someone for are raised in the panel and sent to Telegram. Unusually large payouts are the case operators care about most, and the one worth having reach a phone rather than waiting to be noticed in a report.

Telegram matters more than it sounds for this market. The person who needs to know a machine just paid out an unusual amount at eleven at night is not sitting at a desk with the panel open.

Remote configuration

Changes are pushed from the back office to a terminal, a hall, or a whole branch of the tree without a site visit. Configurable remotely:

• Game mix — which titles appear, per terminal or per hall
• Denominations and bet limits
• Language
• Branding
• RTP

The practical consequence is that a floor is not fixed at the moment it opens. Most opening game mixes turn out to be wrong in at least one direction, and fixing that in week three should cost a decision rather than a drive.

Installation is the one point where remote configuration is not the whole answer. Support can connect to a terminal over AnyDesk to help with setup where a venue needs a hand, which in practice matters most for the first machine in a new room and rarely after that.

A note on RTP

RTP is configurable rather than fixed per title. What you are permitted to set is a market question before it is a platform one — some regulators mandate a band, some mandate a number, and some leave it to the operator. The platform will not decide that for you, and neither will we; bring your market and we will tell you what is workable in it.

Cash desk and collection

Payout happens at the desk, recorded against the session it belongs to. Collections are recorded in the panel, so what came out of a machine and when is a lookup rather than a conversation.

When a counted figure does not match a recorded one, support is available around the clock to go through the transaction history with whoever is holding the discrepancy. That is a deliberately plain description of how it works: there is no automated adjudication step, and a person on a night shift with a shortfall gets a human rather than a ticket queue.

Paying cashiers on performance

A cashier can be put on a percentage of the hall’s profit. The rate is configurable and off by default, and the bonus becomes available at a set interval — six hours out of the box. Withdrawing it deducts the amount from the hall’s balance and the cashier takes that sum from the register, with the movement recorded in balance history alongside everything else.

Paying floor staff a share of what they bring in is normal practice in retail gaming and almost never supported by the software, which means it usually lives in a spreadsheet and gets argued about on Fridays. Having it in the same system as the takings removes the argument.

Reporting

Standard reports, what each answers, and export format

Report	What it answers	Export
Transactions	Every credit in and payout out, traceable to a terminal and a session	CSV, XLSX
Panel actions	Who changed what in the system, and when	CSV, XLSX
RTP	Actual return by game over a chosen period, against what was configured	CSV, XLSX
Game statistics	Which titles are being played, and which are earning	CSV, XLSX
Game list	What is enabled where, across the tree	CSV, XLSX
IP intersections	Which accounts share an IP address	CSV, XLSX

That last one is the standard first check for multi-accounting and bonus farming. When the same address sits behind several accounts claiming the same promotion, this is where it shows up — and it is the report almost nobody in this market bothers to mention they have.

Session-level history is retained for three months. If your regulator requires a longer record than that, export on a schedule and keep the archive on your side — worth building into your operating routine at launch rather than discovering at an audit.

The game statistics report is the one that pays for itself. A floor almost always has two or three titles quietly occupying machines that earn nothing, and they are invisible until someone ranks them.

Roles, permissions and audit

Permissions follow the hierarchy. An account at any level sees its own branch downward and nothing above or beside it, so an agent can be given a real working back office for their halls without seeing the rest of the network, their commercial terms, or each other.

Every action in the panel is logged with the account that performed it and the time it happened, and that log is one of the standard reports rather than something support has to retrieve for you.

For a network operator this is usually the deciding feature rather than a footnote. When money is moving through other people’s hands, the question is not whether you trust them — it is whether a disagreement six weeks from now can be settled by looking something up.

Where you can use it

The back office runs in a browser and works on a phone. An agent checking a hall’s take from the car, or an owner looking at an alert at midnight, does not need to be at a desk.

Questions operators ask

Can I change a terminal’s settings without visiting the venue?

Yes. Game mix, denominations, bet limits, language, branding and RTP are all set from the back office and pushed to a terminal, a hall or a whole branch of the tree. Support can also connect over AnyDesk if a machine needs hands-on help during installation.

How many halls and terminals can one account manage?

There is no cap. The structure runs superagent, dealer, agent, hall, terminal, and it is designed for networks that grow by adding branches rather than by adding accounts.

Can I give an agent access to only their own halls?

Yes — that is how the hierarchy works rather than a setting you switch on. Each account sees its own branch downward and nothing above or beside it, so agents get a working panel for their own rooms without visibility of the wider network.

How far back does session history go?

Three months in the panel. Everything exports to CSV or XLSX, so if your market requires a longer retention period, schedule regular exports and hold the archive yourself.

Does the back office work on a phone?

Yes. It runs in a browser and is mobile friendly, and alerts go to Telegram, so the things that need attention out of hours reach you without a laptop.

Is there an audit trail of who changed what?

Yes. Panel actions are logged with the account and the timestamp, and available as a standard report you can export. For a network moving money through several parties, this is usually the feature that settles arguments.

Related