Flag passengers who still have an unsigned flight waiver
Every morning, WebRun opens TripWorks, reads the digital waiver status for every passenger on the next two days of flights, finds who has not signed yet, and posts your crew a clear Slack checklist grouped by flight so unsigned waivers are chased well before the launch window.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I automatically flag balloon passengers with unsigned waivers?
Every morning, WebRun reads the digital waiver status for every passenger on the next two days of balloon flights in TripWorks, finds who has not signed, and posts your crew a Slack checklist grouped by flight and ordered by launch time. The crew chases outstanding waivers early, so no passenger reaches the launch field with paperwork undone.
- Crew starts the day knowing exactly which waivers are still outstanding
- Unsigned waivers are chased before launch, not discovered at the field
- Passengers who already signed drop off the list from live TripWorks status
Built for hot air balloon operators · balloon ride companies · ground crew leads · tour operators
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
www.tripworks.comin a real browser with your saved login - no setup, no API keys. -
1
TripWorks - check digital waiver status
tripworks.com How to Automate TripWorks
WebRun opens TripWorks to check digital waiver status. - Open TripWorks and list every flight in the next two days
- For each passenger, read the digital waiver status attached to the booking
- Collect the name, flight date, and party for anyone whose waiver is still unsigned
- Note the waiver signing link on file so the crew can resend it if needed
Done when Every passenger with an unsigned waiver on upcoming flights is identified with their flight and party.
-
2
Slack - post the unsigned-waiver checklist
slack.com How to Automate Slack
WebRun opens Slack to post the unsigned-waiver checklist. - Post a checklist to the crew Slack channel grouped by flight and launch time
- List each unsigned passenger with their party size and the waiver link to resend
- Put the flights nearest to launch at the top so the crew chases the most urgent first
- Keep the message internal to the crew. Do not message passengers from this run.
Done when The crew has a Slack checklist of every unsigned waiver, ordered by how soon each flight launches.
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
Does it message passengers to sign?
No. This run only posts an internal Slack checklist for your crew. It surfaces the waiver link so a person can resend it, but it never contacts a passenger on its own.
How far ahead does it look?
It checks the next two days of flights in TripWorks by default, so unsigned waivers surface with time to chase. You can widen or narrow the window to match how far out you book.
What if a waiver gets signed after the checklist posts?
It reads live waiver status in TripWorks on each run, so anyone who signs before the next morning drops off the list automatically and the crew only sees who is still outstanding.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.