How to use TrackPod for Mobile

Introduction:
Remember that an attendee's badge will have a code printed on it that TrackPod will utilize to submit their registration information. TrackPod can read a variety of codes, although barcodes and QR codes are the most prevalent.

In addition, there are numerous reasons (or scenarios) why an attendee badge must be scanned. These can range from as simple as recording attendance to as complicated as managing session access for a small group of attendees.

Scanning Codes
Before the event, each attendee's registration information is turned into a unique code that is printed and displayed on their badge. When the guest arrives onsite, the TrackPod app scans their code and exchanges information.

• . List the five unique scanning scenarios that TrackPod can be used for.

1. Code 39- A simple alphanumeric code that supports some special characters and is truncated with asterisks.
2. Code 128- A more dense barcode type with seven unique alphanumeric sections.
3. PDF417- A series of linear barcodes stacked atop one another to create a unique code.
4. QR Code- A square-shaped code with three distinct sections to store data.
5. Aztec Code - A square-shaped code with a distinct center section to store data.

let's review the potential scanning scenarios.

TrackPod can be employed in five distinct scenarios based on the event host's demands. A given event could involve any mix of these scenarios, therefore it's crucial to understand about them all so you're ready for any scanning jobs that may be assigned.

Session Attendance
This action tracks thebasic headcount at a given session.  An attendee's badge is scanned and the attendee is permitted into the session. All event attendees are allowed into the session until the session capacity is reached. The total number of attendees who entered the session is recorded and available in TrackPod's reports.

Time-Logged Session Attendance

This scanning scenario is frequently used for sessions related to accreditation - when time spent in attendance is monitored. When an attendee enters a session, their badge is scanned IN, when an attendee leaves a session, their badge is scanned OUT. 

The total time logged between being scanned-in and scanned-out is recorded for each attendee and is available in TrackPod's reports.

All event attendees are allowed into the session until the session capacity is reached.

Permission to Enter
In this access control scenario, when a badge is scanned, the app shows a green Authorized or red Not Authorized dialog box, depending on whether the guest has formally registered for the session.
If attendance is authorized, they may enter the session; otherwise, they may not.
Unauthorized attendees can use the override button. However, the choice to approve this activity is up to the event host.

One-Time Entry

Here's another access control scenario. When a badge is scanned, the app shows a green Authorized or red Not Authorized dialog box, depending on whether the guest has legally registered for the session.
If attendance is authorized, they may enter the session; otherwise, they may not.
With one-time admission, after the participant is scanned out, their profile changes from Authorized to Not Authorized, and they are unable to re-enter the session.

Unauthorized attendees can use the override button. However, the choice to approve this activity is up to the event host.

Product Redemtion

In this instance, scanning an attendee's badge indicates purchasing goods. This good could be food or drink tickets, event swag bags, or pre-paid products provided by a speaker.
An attendee's badge will always have a specified product amount connected with it, and when the badge is scanned, that quantity is lowered by one.

For example, an attendee's badge may include two pre-paid drink tickets. Scanning the badge for the first time yields an Authorized screen and serves the participant their first beverage. Scanning the attendee badge a second time results in another Authorized screen, allowing the guest to claim their second beverage.

TrackPod, on the third scan, will display a Not Authorized screen because the two products linked with the badge have already been redeemed.
A product quantity override button, similar to those used in access control scenarios, is accessible. However, the choice to approve this activity is up to the event host.

Key-in Barcode

TrackPod's scanner may occasionally fail to read an attendee's badge.
If the badge displays a visible alphanumeric code, there is a button that allows the user to manually enter the barcode information.