Overview: Arrival
This feature is supported for: Resorts that use RTP|One and Aspenware Identity and have a license agreement for Aspenware Arrival.
This feature is NOT supported for: Resorts that use Siriusware.
Key Terms
Resort/Organization
This is the highest level of the Arrival application. This level will have impacts across the entire application. Theming and technical tasks are completed at this level. Resorts can have many Locations.
Location
This is the second level in the Arrival architecture. Locations are composed of Activities. There can be several Locations and each Location can have multiple Activities.
Activity
This is the third level in the Arrival architecture. Activities are composed of Tasks. There can be many Activities under one Location and each Activity can have multiple Tasks.
Task
This is the fourth level in the Arrival architecture. Each task indicates a discreet action that is needed to be taken by the guest. Activities can have multiple tasks.
Description
Airline passengers have been programmed to check-in 24 hours prior to their flights for years now. This allows the airline to capture information on the guest, saves time at the airport, and gives travelers peace of mind that their experience at the airport will be smooth. Aspenware Arrival provides this experience for guests coming to ski and ride at the resort. Guests can check in prior to arriving at the resort.
Guests interacting with Arrival will use the application to complete missing information or tasks required for their upcoming activities. For example:
If they have already purchased their resort products, but are missing required information, they may receive an email with a link to Arrival. These are most often automatically triggered to send 1-2 days prior to the guest’s activity via a CRM, based on the guest having an upcoming activity purchase that requires an Arrival task to be completed.
If they are purchasing on-premise and need to fill out information prior to checking out at a cashier, they may navigate to a Location URL (“Non-transaction driven” URL) from a QR code posted in the rental shop or pass office.
If they want to get easy access to the QR codes to print their non-printed media at a Pick Up Box at the resort, they may be prompted to download their unique QR codes to their Apple wallet from Arrival before their trip via a triggered email, or they might scan a QR code posted near the PUBs to be directed to get their unique QR code for printing in Arrival.
If they want to check to confirm whether their pass is ready to take direct to lift, they may go to pass checker via a link from the a “make sure you’re prepared for your upcoming trip” email sent to them by the resort to validate that they have the right media on hand and access products purchased before they arrive.
Pass Media Redemption
QR codes will be displayed in Arrival for guests to use to pick up media at either an Axess PUB or Skidata Skiosk. For easy access, guests can also add these QR codes to various apps such as Apple Wallet and GPay.
Pass Checker
On Arrival’s Pass Checker page, guests can look up their pass eligibility by either Pass# or RFID#. They can also filter between specific lifts and date combinations to check their pass eligibility. This is useful for resorts that limit lift access for specific gates and also for passes that have blackout dates.
Arrival “Check-in” Tasks
Arrival allows guests to complete tasks necessary for guests to participate in activities at the resort.
Waivers
Rental Profile
Child Registration Profile
Photo Upload
How it works
Arrival uses Locations, Activities, and Tasks to determine what functions guests will be completing.
Locations - A Resort can have several Locations. Each Location will have its own unique URL to which guests can navigate. Each Location requires a default activity. Examples of locations include:
“POS Transactions” - A “POS Transactions” Location might prompt users to complete tasks personalized to them based off of orders placed in your POS system. Whether through an eCommerce store such as Aspenware Commerce or placed directly into the POS through a phone call or resort visit.
“Rental Shop” A “Rental Shop” Location is most likely a configuration used for purchases made by guests who are physically at a rental location on-premise.
Activities - An Activity is comprised of one or more tasks. These task may be related to a specific purchase. Examples include:
“Purchases” - This might be an Activity underneath the “POS Transactions” Location. This particular Activity will link to specific tasks that are required to be completed by the guest for the particular product purchases they have where they are missing required information. The guest would only be prompted to fill out specific tasks that they are personally missing based on their orders.
“Ski/Snowboard Rentals” - This might be an Activity underneath the “Rental Shop” Location. Again, this particular Activity will link to specific tasks that are required to be completed by the guest for this particular product purchase.
Task - A Task is the specific function that guests will be completing. Tasks supported in Arrival include:
Waiver Signing
Child Registration Capture
Rental Profile Capture
Photo Capture