...
| Info |
|---|
NOTE: There is an additional charge and time to implement required by 1Risk to utilize this integration. |
Feature Description
| Info |
|---|
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 ‘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.
...
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.
...
Insert excerpt