---
title: How the second screen works
audience: users
summary: What the customer sees, how an advisor starts a session, and what the tablet will and will not do.
description: "What the World of Regions livestream tablet does in a travel agency — starting a session, pairing with a code, and what the customer can do with it."
order: 1
updated: "2026-09-14"
---

![The customer tablet before pairing: six empty character boxes under the heading "Let's find your journey", waiting for the code the advisor reads out. The tablet shows whichever language the operator has set — Polish here.](/docs/media/livestream-pairing.webp)

The livestream joins one advisor desktop to one customer tablet. Your application decides what the
tablet shows: it pushes a **view** and the data for it, and the tablet renders that, nothing of
its own. The customer can act only where your session config allows it, and the search view is
never customer-driven.

A session is always **one tablet**, fixed server-side. Its state lives in the backend, not in a
connection, so both sides see the same session whichever transport each uses.

## Starting a session

The advisor starts the session in their own desktop application, which shows a **six-character
code**. The customer types that code into the tablet on the other side of the desk and the two
are joined; from then on the tablet follows whatever the advisor is looking at.

One session holds **one tablet**. A second device typing the same code is refused rather than
quietly taking the first one's place, so a session cannot be hijacked by someone reading the
code over a shoulder.

## What the customer can do with it

The tablet is a mirror, not a second cockpit. It shows the offer, the photographs and the price
the advisor has open, and the customer can act only where the advisor's application has allowed
it — choosing between options put in front of them, for instance. Searching is never
customer-driven: nothing the customer touches changes a booking.

It is also the customer's own language and the agency's own brand: the operator sets both, and
the tablet applies them without anyone touching the device.

## When a session ends

Sessions end themselves. A tablet left untouched for **five minutes** closes, and so does a
session whose desktop has been idle for **fifteen**. That is deliberate — a tablet in a shop
window should not still be showing the last customer's holiday an hour later. Starting again is
a new code, which takes a few seconds.