Check-in (Chrome desktop app)

This application will allow you to scan Tickera tickets without having to access the back end of your website. Application requires having Google Chrome browser installed and therefore can be used on all of the major operating systems (OSX, Windows and Linux).

Also, this application is compatible with our Check-in app Translation add-on so you can run it on your own language or just modify some parts of the text of the app interface.

 

Installation

To install application, first start your Chrome browser and then follow this link which will lead you directly to the application.

When application page loads, hit "Add to Chrome" button (1). A popup window will show, asking you to confirm. Just click "Add app" button (2) as described in the picture below

1

Once you have added Check-in application to Chrome you can simply launch it from this same window. However, to access it later, you can find it in your application drawer within Chrome browser as described in the picture below.

app

Optionally, you can create a shortcut for even easier access by right clicking on the application icon within the app drawer and selecting "Create Shortcut" option. Now, depending on the operating system you are using you may be offered different options for where you would like a shortcut to be placed ("Desktop" and "Pin to Taskbar" for Windows, "Applications folder" for Mac, etc.).

 

Using Check-in Chrome application

First off, if you have used our iOS or Android Checkin apps, the interface and usage should seem pretty familiar to you since this app shares the same DNA with our mobile apps. However, if you haven't used our mobile Checkin apps, we'll walk you through all of the bits and pieces so you should get a hang of it in no time.

Now, when you first start the application, you will be welcomed with the screen as shown in the picture below where you will be asked to enter the following credentials:

  1. WordPress installation URL - you should enter here the URL of your Tickera-powered website. Leading http:// or https:// is mandatory in order to be able to connect to your website.
  2. API Key - enter an API key of the event you want to check tickets for. This API key is automatically generated once you have finished creating your event or can be manually created in Tickera Settings -> API Access tab.
  3. Auto Login switch - if switched to active, you will be automatically logged in next time you start the app (unless you choose to logout from within the app)
  4. Sign in button - once you have entered your URL and API key, hit this button to log in.

Important note: in order to be able to log in, you must have your Tickera license key of either Standard or Bundle package entered in Tickera Settings. 

3

After you have successfully logged in, you will notice a little popup which will notify you that the database has been downloaded successfully. At this point you can start using this application offline and each time you connect the database will be synced again.

So, to conclude, this app allows you to scan tickets offline but first you will need to run it once while connected to the internet in order to download and sync the database from your Tickera-powered website. After that, you are ready to take Tickera to any remote location and be able to scan tickets regardless of the internet access availability.

offline

*please note that popup may appear on different places depending on which operating system you are running the app

Now, before we dive in any further, lets first walk through the available menu items:

menu2

 

1. Home - Stats - this will lead you to the starting screen mentioned on the beginning

2. List - selecting this will allow you to see the list of all the attendees and details about their orders

3. Check in - probably the most important menu item as it leads to the screen for tickets check-in

4. Sign out - if you sign out, you will be asked to enter your credentials again regardless of whether you checked Auto Login option

5. Network state icon - checks the network state. Icon is yellow when there is network connection and turns gray when disconnected

 

 

 

 

 

 

 

 

Home - Stats

After you have successfully logged in, you will be presented with the Home-Stats screen where you will be able to overview how many tickets have been sold (1) and how many tickets have been checked-in (2).

4

 

List

This screen will provide a scrollable list (1) of all the attendees of the event with the overview of their ticket IDs and the date of the ticket purchase visible at a glance. Also, from this screen you can use a Search field (2) in order to search for the particular attendee by name or ticket ID.

6-1

On the right of the each row in this list, you will notice an arrow button (3). When pressed, that button will load all the details about the particular attendee and also provide the option for manual check-in (useful when attendee have forgotten his/her ticket but proven the identity and found on the list of the attendees).

Attendee details screen contains following information:

5-2

  1. Name, ticket ID and date of ticket purchase
  2. Ticket type - type of the ticket
  3. Buyer Name - name of the buyer which may be different from the owner name presented on the top
  4. Buyer Email - email of the person who purchased ticket and to whose email the ticket was sent
  5. Custom Forms information (optional) - if Custom Forms add-on was used during checkout and if the elements in that Custom Form was set to Show in Check-in app, it will be displayed here. Otherwise, these fields won't be displayed.
  6. Check-ins - list of all of the check-in attempts. May show as Pass or Failed depending on number of available check-ins set for that ticket type.
  7. Check in button - used for manual ticket check-in
  8. Check in response message

Check in

Previously we've mentioned that this is probably the most important option. Essentially, this screen is used for the actual ticket check-in. It is consisted of only one big field (1) which will automatically fill up when barcode scanner button is pressed and the barcode on the ticket successfully read. However, ticket ID may also be manually entered to this field and yield the same result as when scanned with the barcode scanner.

When the ticket is scanned an validated, a corresponding message will appear below that field:

  • Ticket has been checked in - for valid tickets
  • Wrong ticket code - for expired tickets (when limit of available check-ins is reached)
  • Error - for non existent tickets

Also, from this screen you can search for an attendee by name using the search field (2) on the top right.

7

 

As you can see, installing and using Check-in application is fairly simple and self explanatory. However, to make sure that ticket check-in runs smoothly on your event, please take a moment to read our post about do's and don'ts in creating ticket templates and actual ticket scanning at the door. Of course, if you ever get stuck or need some further explanation or help, do not hesitate to contact our support team at support.tickera.com