Overview: 1Risk Waivers

1Risk’s electronic waivers can be integrated into Aspenware Commerce to be signed either as a required part of the checkout process for orders that require waivers, or as a follow up waiver signing pre-arrival task, where personalized 1Risk waivers can be linked to in an order confirmation email.

This feature is supported for:

Resorts that use 1Risk as their waiver management tool.
Resorts that use Aspenware Commerce and either RTP|One or Siriusware.
Resorts that use Aspenware Arrival or Resort Tools AND use RTP|One for POS.

This feature is NOT supported for:

Resorts that do not use 1Risk as their waiver management tool.
Resorts using Aspenware Arrival and Resort Tools AND use Siriusware for POS.

Key Terms

1Risk Waivers

1Risk is a ski industry vendor that offers advanced waiver signing functionality including intial, name and date signing throughout the waiver body and storage of guest waivers within the database. Aspenware Commerce offers several ways to integrate with . Resorts can utilize by directing guests to the platform through the CTA link in the confirmation email or by presenting guests with waiver signing within the Aspenware Commerce checkout flow. When presented within the Aspenware Commerce checkout flow, the the waiver is presented as an iframe through which the user interacts directly with the waiver. Signed waivers are stored in great detail within the platform; Aspenware also offers integrations to reference the waiver ID in the resort POS. For RTP|One, an authorization profile is created for the signing guest that references the waiver ID and, optionally, offers a full html record of the waier. In Siriusware, the waiver is mapped to a corresponding waiver ID and is shown in the liability section of the guest’s profile as well as within their activity profile.

NOTE: There is an additional charge and time to implement required by 1Risk to utilize this integration.

Feature Description

NOTE: For information about 1Risk Waiver compatability with Aspenware products and POS platforms, please see Waivers (Standard and 1Risk) for a comparison chart.

When presented within the Aspenware Commerce checkout flow, the 1Risk waiver is presented as an iframe through which the user interacts directly with the 1Risk waiver. Signed 1Risk waivers are stored in great detail within the 1Risk platform; Aspenware also offers integrations to reference the 1Risk waiver ID in the resort POS.

HINT: (For more information about integrating 1Risk Waivers with Aspenware Arrival, please see Configuration: 1Risk Waivers for Arrival.)

When signed as a step in checkout for RTP|One, an authorization profile is created for the signing guest that references the 1Risk waiver ID and, optionally, offers a full HTML record of the 1Risk waiver.

In Siriusware, the 1Risk waiver is mapped to a corresponding waiver ID and is shown in the liability section of the guest’s profile as well as within their activity profile.

It can also be presented as a pre-arrival follow-up task, when configured as a follow-up task, resorts can include a CTA within the order confirmation email directing guests to the 1Risk platform.

Selecting ‘Sign Waiver’ brings the guest to the 1Risk platform with their information already pre-populated. From here, they can complete their waiver to be stored in 1Risk.

While waivers can be configured to be collected either in the checkout flow or as a follow-up task after the order has been completed, there is no option to “skip waiver and sign it later” option in the checkout., Waiver signing for a product is configured to be completed either as a required task during checkout or an optional task after an order is completed.

When the waiver is signed, whether it is signed through the link in the order confirmation or required in the checkout flow, it will be stored in 1Risk for easy access and reference with all the necessary guest information and wet signatures.