Flybook Automated Riding Waiver Checks
Every morning, WebRun opens Flybook, lists riders arriving in the coming week, checks DocuSign for a completed liability waiver for each, posts a Slack list of anyone still unsigned, and drafts a signing reminder for your team to review before it goes out.
How do I automatically flag arriving riders who have not signed a waiver?
Every morning WebRun opens Flybook, lists riders arriving that week, and checks DocuSign for a completed liability waiver for each. It posts an internal Slack list of anyone still unsigned, grouped by arrival date, and drafts a signing reminder per rider for your team to send, so no guest saddles up without a waiver on file.
- No rider reaches the corral without a completed waiver on file
- Operations sees the unsigned list every morning grouped by arrival
- Signed riders drop off automatically from live DocuSign status
Built for guest ranch owners · dude ranch wranglers · ranch operations teams · trail riding outfits
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
theflybook.comin a real browser with your saved login - no setup, no API keys. -
1
Flybook - list arriving riders
theflybook.com
WebRun opens Flybook to list arriving riders. - Open Flybook and list bookings with riding activities arriving in the next 7 days
- Capture each rider's name, party, and arrival date
- Note which guests in each party are booked to ride
- Compile the list of riders who need a waiver on file
Done when Every arriving rider who needs a waiver is listed with their party and date.
-
2
DocuSign - check for a signed waiver
docusign.com
WebRun opens DocuSign to check for a signed waiver. - Open DocuSign and search completed envelopes for each rider's liability waiver
- Match a signed waiver to the correct guest and stay
- Flag any rider with no completed waiver on file
- Note waivers that are started but not yet finished
Done when Each arriving rider is marked as waiver signed or waiver missing.
-
3
Slack - post the unsigned waiver list
slack.com
WebRun posts the unsigned waiver list to Slack. - Post a summary to the operations Slack channel of riders still missing a waiver
- Group the list by arrival date, soonest first
- Draft a friendly signing reminder link for each unsigned rider and leave it for your team to send
- Never send the reminder to the guest directly without approval
Done when The operations team has a Slack list of unsigned riders with drafted reminders ready to send.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it email guests the waiver reminder on its own?
No. WebRun posts the internal gap list to Slack and drafts a signing reminder per rider, but leaves it for your team to send. Only the internal Slack digest is posted automatically; guest reminders wait for a human.
How does it know a waiver is actually signed?
It searches completed DocuSign envelopes and matches each signed liability waiver to the correct rider and stay, so a guest only clears the list once their waiver is genuinely finished, not merely sent.
What if a rider signs after being flagged?
It rechecks DocuSign every morning, so a rider who signs after being flagged drops off the unsigned list on the next run automatically, with no manual clean-up needed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.