Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Pass Checker enables guests to enter their card number (passmedia# or RFID#) to check if their media will work at a specific lift. Among many use cases, guests can check if their pass is hotlisted due to incomplete tasks or if their pass is blacked out for the selected date.

Setup Checklist

This section is a comprehensive and high level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.

Infrastructure Tasks

1. Send request to Aspenware to enable Pass Checker

PREREQUISITES

Aspenware Arrival Tasks

1. Edit General Tab in Aspenware Arrival Admin Toolbar REQUIRED

2. Create “AccessLocations” Collection REQUIRED

3. Create “Pass Checker - Hotlist Reason” Collection OPTIONAL

4. Create “AccessLocations” mapping(s) REQUIRED

5. Create “Pass Checker - Hotlist Reason” display mapping(s) OPTIONAL

6. Update Pass Checker Languages Strings OPTIONAL

7. Edit Task Types OPTIONAL

8. Create Task List REQUIRED

9. Create Activities List REQUIRED

10. Create Locations List REQUIRED

11. Customize Theme OPTIONAL

12. Create Users OPTIONAL

DETAILED SETUP

Infrastructure Tasks

  1. Submit a request to your Aspenware Service Partner to enable Pass Checker.

Aspenware Arrival Tasks - Detailed Setup Guide

1) Edit General Tab by adding Resort’s Default Pass Checker POS Location ID.

  • The Pass Checker POS Location ID is a setting from RTP|One, and can be sourced from your RTP|One administrator. (RTP|One/ Access Control Admin / Access Control Management / Access Location)(Select an access point that most tickets would be valid for? Why is POS in the label?)

While logged in as admin, click on the GENERAL tab in the admin toolbar. Enter the numeric value in the “Pass Checker POS Location ID” field, and click the UPDATE GENERAL SETTINGS BUTTON.

If using Google Analytics, enter the Tag ID in this window.

Resort Codes, Resort Group Codes and Sales Location IDs?

2) Create “AccessLocations” Collection (required).

While logged in as admin, click on the COLLECTIONS tab in the far right corner of the menu bar.

  • Create a Collection by entering “AccessLocations” in the Name field, then clicking the ADD COLLECTION button.

3) Create PassChecker Hotlist Reason” Collection (optional)

If you would like to hide RTP Hotlist reasons with more appropriate customer-facing language, follow the procedure above to create a new collection, naming it “Pass Checker - Hotlist Reason”.

4) Create “AccessLocations” Mappings (Required).

Assign Items to the Collection by selecting the Collection (click in check box). This will launch the ADD NEW COLLECTION ITEM window.

  • When the Add New Collection Item window appears, populate the fields as shown. The Name field is customer facing and should be easily recognizable to a resort guest. Avoid jargon or internal names like LIFT 4 or POMA. Instead, use a name that a guest will recognize, like TRAM, or BEGINNER LIFT. The Value is the RTP Access Location Code. Ask your RTP System Administrator for these codes. Save entry by clicking ADD COLLECTION ITEM.

If necessary, you can edit your collection item by selecting it (check box), then clicking UPDATE COLLECTION ITEM. You can also delete using this same steps.

5) Create Pass Checker HotList Reason display mappings (optional)

Follow the same process to add Collection Items to “Pass Checker-Hot List Reasons” if necessary.

6) Update Pass Checker Language Strings (optional)

  • Logged in as admin, click on the LANGUAGE Tab on the admin toolbar. Scroll down to Pass Checker, and click on it to expand entries.

  • All entries have default copy supplied, so you do not have to edit if you choose not to. Note that the entry entitled “Invalid Media Error Text” includes a spaceholder for a phone number, which must be customized by the resort.

Steps 7-10 ( Edit Task Types, Create Tasks, Create Activities and Create Locations) are used to define the actions (complete waiver, provide rental info) required for the guest to successfully fulfill their ecommerce purchase.

Task Types are predefined (Waiver, Rental Profile, Child Registration Profile or Photo), but can be customized to capture specific info, expiration, or set as optional or required.

Tasks are the specific documents (Season Pass Waiver, Ski School Waiver, Rental Form) or actions (Photo Upload) that need to be executed. In the instance of a document, it has been built inRTP|One, and mapped by entering the Authorization Type Code in the POS Waiver ID field.

Activities are the customer-facing icons that inform your guest as to what actions they need to execute. You can assign multiple tasks to an activity. For example, a guest purchasing a rental would need to provide a completed rental info form as well as execute a liability waiver. In that case, those two TASKS can be assigned to a single RENTAL SHOP CHECK IN ACTIVITY.

Locations represent the physical (or virtual) setting where fulfillment of your guest’s purchase will take place. Typical Location definitions might include Rental Shop (if there are multiple shops at the resort, you would be more specific: Main Lodge Rental Shop, Back Country Rental Shop, etc.). Virtual locations might be ONLINE, WEBSHOP or some other designation that allows the customer to compete their tasks and go straight to lift.

How do these four items work together? At your resort, the RENTAL SHOP location could have an activity assigned called RENTAL SHOP FORMS, that is made up of two tasks: RENTAL WAIVER (TASK) and a RENTAL INFO FORM (TASK). The Rental Waiver would be defined as a Waiver (Task Type) while the Rental Info Form would be defined as a Rental Profile (Task Type).

7) EDIT TASK TYPES

There are 4 task types in Arrival. Click on the box to edit each task.

  • Effective days allows for the aging of a profile, photo, waiver, etc., on a schedule determined by the resort. Setting effective days to 365 means the document will expire one year from the time it was uploaded. Leaving the field blank means it never expires. You cannot add additional task types.

8) CREATE TASK LIST

  • Tasks are the steps a guest needs to complete to be allowed to fulfill their order. For example, a season pass holder must complete a waiver (required) and upload a photo (optional) to be allowed to pick up or activate their pass.

  • Logged in as admin, click on TASKS tab in Arrival admin toolbar. Scroll to the bottom of the screen, and populate the fields in the Add New Task window. Click on ADD TASK. To edit an existing task, click on the box to select it, and edit in the window below. Click UPDATE TASKS to save your changes.

  • WAIVER TASKS have several unique configurable components, allowing resorts to use them in many situations.

  • Ask your RTP|One Administrator for a list of “Authorization Types” that exist in RTP|One. (Administration Navigator/System Administration/Customer System Management/Authorization Types). You will use the Authorization Type Code to populate the POS Waiver ID field when creating tasks.

  • Enable “Consolidate Waiver” if xxx xxx xxx. Enable One Day Waiver if xx xxx xxx.

  • Follow this same procedure to complete ski school waivers, rental profiles, and child rental profiles.

9) CREATE ACTIVITIES

Activities are the actions a guest must execute to fulfill their ecommerce order. Activities can be a single task, or a collection of required tasks. Activities can be age-specific, or can encompass all ages. Adding an image, like an icon or photo, assists the guest in navigating the Arrival experience. Is not required, but is recommended.

10) CREATE LOCATIONS

Locations are the physical (or virtual) setting where fulfillment of your guest’s purchase will take place.

Define locations by selecting a name that resonates with your guests, avoiding jargon, abbreviations, and technical language. Ticket Office, Main Lodge Rental Shop, SkiWee Cabin are all examples of easily identifiable physical locations. Virtual locations, where the guest will compete all activities, and go straight to lift should also have a name that reflects that functionality- Online, Ecommerce, and Webshop are a few examples.

SETTINGS? use POS? IS edit profile location? set default activity required?

ASSIGN ACTIVITIES - required if default is set?

11) Customize Theme.

12) Create an admin user.

What is process for creating an admin user if the don’t have aspenware domain in email address? Move this to the top.


Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.

  • No labels