WEBVTT

1
00:00:00.200 --> 00:00:04.568
On the evening, tickets are checked at the door with the scanner app, on a phone or

2
00:00:04.568 --> 00:00:08.200
a handheld scanner. In this episode we admit people to a performance.

3
00:00:09.151 --> 00:00:13.828
Staff who may take admissions see the Admit tool on their home screen, among the

4
00:00:13.828 --> 00:00:15.231
tools their role allows.

5
00:00:15.581 --> 00:00:16.381
Tap Admit.

6
00:00:18.488 --> 00:00:23.743
The performances at this door are listed, with how many people are inside of those

7
00:00:23.743 --> 00:00:28.807
expected. This one has three tickets sold, and its list of tickets has not been

8
00:00:28.807 --> 00:00:29.768
downloaded yet.

9
00:00:30.116 --> 00:00:31.316
Tap the performance.

10
00:00:32.026 --> 00:00:36.974
The list of tickets and the venue's keys are now on the device. From now on every

11
00:00:36.974 --> 00:00:42.106
scan is decided on the phone itself, so the door keeps working without a connection.

12
00:00:42.454 --> 00:00:47.366
The scan box is ready. With a handheld scanner you just pull the trigger, and on a

13
00:00:47.366 --> 00:00:52.397
phone the camera button scans the Q R code. You can also type the code printed under

14
00:00:52.397 --> 00:00:54.134
it. We type the first ticket.

15
00:00:54.484 --> 00:00:59.061
A big green ADMIT, with the seat and the ticket type. The count at the top goes up

16
00:00:59.061 --> 00:01:01.684
by one, and the scan is added to the log below.

17
00:01:02.036 --> 00:01:03.956
Now we scan the same ticket again.

18
00:01:05.448 --> 00:01:10.591
The banner is red: ALREADY IN, with the time it was scanned. Nobody can get in twice

19
00:01:10.591 --> 00:01:11.448
on one ticket.

20
00:01:11.796 --> 00:01:17.396
Anything that is not one of this venue's tickets, such as a product barcode, is said

21
00:01:17.396 --> 00:01:19.396
to be so, and is not recorded.

22
00:01:19.745 --> 00:01:25.435
A forged code is refused. Its signature does not match the venue's keys, so it can

23
00:01:25.435 --> 00:01:26.545
never be let in.

24
00:01:27.153 --> 00:01:28.993
Now the connection drops.

25
00:01:29.343 --> 00:01:34.063
We scan the second ticket. It is still admitted, because the list is on the device.

26
00:01:35.466 --> 00:01:40.408
A moment later, the scanner shows that it is offline, and that one scan is waiting

27
00:01:40.408 --> 00:01:45.471
to be sent. Nothing is lost: the scan stays on the device until the connection comes

28
00:01:45.471 --> 00:01:48.906
back, and the next person can be scanned in the same way.

29
00:01:49.257 --> 00:01:54.039
When the connection comes back, the waiting scans are sent. If two gates scan the

30
00:01:54.039 --> 00:01:58.998
same ticket while offline, the first scan to reach the server wins, and the other is

31
00:01:58.998 --> 00:02:00.297
flagged for a manager.

32
00:02:00.648 --> 00:02:03.848
In the next episode, we watch the door from the back office.