Understand local-first branch operations

Before you start

• Know which machine hosts the Controller and Local Node.
• Confirm the branch network can reach the player PCs.
• Keep staff aware of who can restart the Controller machine if needed.

Keep live branch work local

Gaming venues cannot pause every time the internet becomes unstable. Session, device, and staff actions should happen close to the floor through the branch-local path.

• Start, extend, transfer, and stop sessions from the Controller.
• Keep Agent PCs connected to the Local Node on the branch network.
• Use local reports and history for immediate cashier questions.

Use cloud services for oversight

The cloud still matters for owner accounts, subscription state, updates, backups, platform promotions, and longer-term visibility. It should support the branch rather than block live floor work.

• Use cloud-backed owner tools for account and subscription management.
• Use synchronized records for owner visibility after branch work is recorded locally.
• Review release and backup status when internet connectivity returns.

Set staff expectations

Staff should know which warnings matter, what to do during a connection issue, and how to continue service calmly.

• Watch Controller service and device availability warnings.
• Avoid repeatedly restarting multiple PCs before checking the Controller host.
• Record any customer-impacting issue so the owner can review it later.

Verify it worked

• The Controller can load branch pages while the branch network is healthy.
• Agent PCs stay visible from the Controller when they are powered and connected.
• Staff know which actions may wait for internet and which actions should keep running locally.

Troubleshooting

Related product pages

• Product overview
• Controller
• About InkPlay

See also

• InkPlay system overview
• Understand offline and reconnect behavior
• Handle Controller service unavailable