By submitting, you consent to our use of your data. Privacy Policy.
Category
Business Management
Built by
Beam.ai
Register signed WaiverFile releases and their form fields, automating intake work like linking each waiver to a booking.
Signed release records
WaiverFile stores each completed release with the signer's name, date, and form answers. When a customer signs on your site, tablet, or kiosk, a Beam agent reads the finished waiver and links it to the matching booking or participant in your system. It can copy key fields into your CRM and mark the participant as cleared to take part. Waivers missing a signature, showing a mismatched name, or filled out for a minor without a guardian entry are set aside for staff, who confirm details before the participant is allowed through.
Form field routing
Each WaiverFile form carries fields like emergency contact, medical notes, and consent checkboxes. A Beam agent parses a submitted form, applies your rules, and writes the answers to the right place: contact into your roster, a flagged medical note into the staff view. It timestamps consent and files the record under the correct event. Answers that signal a health condition, an unchecked required box, or free text a rule cannot read are escalated to a coordinator, who reviews the note and decides whether extra sign-off or a phone call is needed.
Expiry and renewal
WaiverFile records carry a signed date, and many activities need a fresh waiver each season or visit. A Beam agent checks signed dates against your validity window, tags releases that have lapsed, and messages those customers your renewal link before their next booking. It notes the reminder on each record so nobody is asked twice. Cases where a customer has a booking within days but no valid waiver, or where the renewal bounces, go to front-desk staff to chase directly and confirm before the activity.







