Set up a Qbic kiosk at the reception desk

A reception screen is not a wall screen that happens to be lower down. People walk up to it and do something: register as a visitor, check in for an appointment, tap a card. That needs a screen big enough to read standing up, a touch surface, and a card reader in the same piece of glass — which is what a Luminen Pro 15 is.

Offision treats it as signage: a screen that plays a board. It is not a room panel and not the visitor self-service panel type; what it does is whatever the content you point it at does.

What to have ready

• A Luminen Pro 15, or the 10-inch Luminen Pro 10
• A PoE drop at the desk, or a socket and wireless coverage there
• Somewhere for it to stand or be mounted where people can reach the screen
• Visiting configured for the building
• About thirty minutes, including building the content

The Luminen Pro 10 is the same device at 10 inches, and the kiosk tile also covers a TD-1070 doing kiosk duty. A TD-1070 is a room panel by design, so it is the right choice only where the kiosk is small and mounted, rather than stood on a counter.

1. Build the reception content

The content exists before the hardware does. Go to Signage › Content, choose Add, and pick Reception & lobby.

Answer the screen questions to match the kiosk: a landscape shape, and Touch screen on. That last one is what turns the self-service buttons on instead of replacing them with a QR code — a touchscreen paired to content built without it is a kiosk nobody can use.

What to put on the content — who the welcome screen greets, how the walk-in code behaves, what the self-service buttons do — is in Set up a lobby screen for visitors. Build it there, then come back here for the hardware.

2. Set the kiosk up

Stand or mount it at the desk and take the network cable to a PoE port. It boots into Android.

Then get the player onto the screen. A kiosk that has never been set up boots into its own Configuration screen: put the player address in the Content field there and choose PLAY, or install the Offision Android app on it instead.

Install the app here. A reception kiosk is the case where browser mode costs the most — the built-in card reader is not reachable from a browser, and the badge printer is not either, so a kiosk in browser mode is a kiosk that can neither read a card nor print a badge. See Run the player as an app or in the browser.

The screen shows a six-character pairing code when it is ready.

3. Pair it as a kiosk

In the console, go to Devices › Signage › Devices and choose Add.

Choose the reception content from step 1, then Qbic kiosks under Certified devices.

That tile covers Luminen Pro 10, Luminen Pro 15, TD-1070 and TD-1070 Lite — its Support models button links each of them to Qbic’s own page. The neighbouring Qbic signages tile is the one for the BXP players that drive a wall screen.

Type the six characters from the kiosk. The field submits itself on the last one.

4. Give it a location

This step is not optional on a reception screen, and it is the one people skip.

The device’s location decides whose visitors it greets and, for anyone who registers on it, which building and floor they have arrived at. A kiosk with no location greets nobody. Place it on the floor plan — the wizard offers Set location as it finishes, and the same thing can be done later from the device’s own row.

How to place it, and what the location then controls, is in Set up a lobby screen for visitors.

5. Check it worked

A kiosk that only displays is half-installed, so check both directions:

• It greets. Invite a visitor for today, check them in, and watch the name appear on the kiosk.
• It accepts. Tap a self-service button on the kiosk itself and go through registration. The visitor should appear in the console as having arrived at this building.
• It reads a card, if staff will use it that way. Tap one on the screen’s face.

When it goes wrong

What this does not do

• It does not configure visiting. Visiting types, approval and who gets notified are set up once for the building, and the kiosk only offers what they produce.
• It does not make the kiosk a booking panel. It plays a board; it does not show a single room’s status with a light bar.
• It does not manage the device. Firmware, brightness and the kiosk launcher stay in Qbic’s own tooling.
• It does not replace a receptionist’s screen. The reception desk view in the console is a different thing, used by a person rather than by the visitor.