Scanning QR codes for default check-in status

QR scanning enables you to check in customers by using the FareHarbor app either with or without an external scanning device. If you have multiple check-in statuses configured in your Dashboard and you want a specific device to use a specific status, you can configure it under the QR code settings using the default check-in status.

For example, if you want to check people in for the tour (default check-in point: device 1) and then again when they go through the entrance (second check-in point: device 2) their statuses should update accordingly. As they proceed through various check-in points on the facility, the same rules will apply.

Companies that might benefit from this feature:

• Ferry operators who want to tag customers who have boarded and disembarked the boat.
• Bus tour operators such as hop-on, hop-off buses that want to tag customers who are hopping on at different points of the journey.
• Rental companies that want to tag customers with statuses of their rentals, for example, “checked out equipment” and “returned equipment”.
• Activities or providers with multi check-in points, for example, “checked in”, “boarded”, and “disembarked”.

Prerequisites

The following are required before being able to use a device-specific check in status with QR code scanning for checking in customers:

• On your FareHarbor Dashboard
  • QR scanning must be enabled on each item for which you want to be able to use this feature on the Dashboard.
  • Your check in statuses are configured on the Dashboard under Settings > Check-in.

• Install the FareHarbor mobile app
  • The FareHarbor iOS (version 2.15.1 or higher) or Android (version 1.16.0 or higher) app must be installed on your mobile device. You can check which version you’re using here or by going to the app description on the Apple App Store or the Google Play Store
  • Offline mode must be disabled under QR scanning settings on your mobile app.

Configuring a device-specific check-in on your mobile app

To configure a device-specific check-in status for a specific mobile device, you need to update the setting under QR Scanning > Settings.

Note: In this workflow, the device configuration used at the primary point should be left as Default in the app QR scanning settings. ONLY subsequent statuses should be configured under the QR code settings. Leaving the status for the devices used at the primary check-in point as default will check users in and will ensure that a ticket cannot be reused, whereas changing the default check-in status for the subsequent statuses will allow you to update the customer’s check-in status to the new status.

Example scenario:

Note: The following scenario assumes the check-in statuses in your Dashboard are set as shown here:

1. Customer A arrives at the first check-in point (Tour) and Staff A scans their QR code.
   
   
2. The check-in status is updated to the default status (the first check-in status) in the Dashboard.
   • The default initial status is Tour Check-in. The Booking overview and manifest are automatically updated in your FareHarbor Dashboard to reflect the new status. The Booking overview is shown here:
   • If the QR code was already scanned at this check-in location, the scan details will display Already checked-in in the FareHarbor app when attempting the scan, which is in place in order to prevent the use of the same QR code (ticket) by another individual.
3. Customer A enters the ship to go to another check-in point, and the QR code is now scanned by Staff B. Staff B’s device is set to Entrance Check-in.
4. The customer’s check-in status is updated in the FareHarbor app, as well as in the Booking overview and manifest in the Dashboard.
5. If Customer A had already checked in at that location, they cannot check in again and status shows Already checked-in.
6. Default statuses are device-specific and can be customized in the Dashboard check-in status settings.
7. Customer A can now check in to other entrance points onboard the ship using their QR code. However, they cannot go back to the first point of entry, as this will show Already checked-in and the code cannot be re-used.

Notes:

• When a staff member moves to a different check-in point, they need to ensure that their device is configured to the correct check-in point status. For example, the status should be Tour Check-in if their location is set to scan for the Tour, or Entrance Check-in if they are positioned at the entrance.
• Ensure that the check in mode (customer or whole booking) is configured the same way across all mobile devices.
• This is not a hierarchical check-in process, meaning a customer can update to any status configured for the check-in device. However, if the customer already has any of the check-in statuses assigned, they will not be able to check-in again at the primary (Dashboard default) check-in point. This is to avoid customers being able to check in more than once (reuse the same QR code).

Frequently Asked Questions

Internal-only content. Don't copy and paste to anyone.

Note: The feature is currently enabled with a remote config for Queen Mary and some other beta customers. If you see this feature enabled in the QR scanning settings while logged in as an Admin, this means the setting is enabled for that beta client. If you close the FH application and log in again, you will not see the setting for any other company.

To learn more, feel free to run through this slide deck.