Automated Orbitz Booking Change Alerts
Every morning, WebRun opens your company's Orbitz bookings, checks every upcoming trip for a schedule change, cancellation, or gate and time update, logs each itinerary change to Google Drive, and texts your travel coordinator through Twilio the moment something shifts.
How do I get alerted when an Orbitz booking changes?
WebRun checks your company's Orbitz bookings every morning for schedule changes and cancellations, logs each itinerary update to Google Drive, and texts your travel coordinator through Twilio the moment a trip changes, so a schedule shift reaches the right person before a traveler is caught off guard at the gate.
- Schedule changes reach the coordinator the same morning they happen
- Every itinerary change is logged with a dated record
- Unchanged bookings never generate a false alert
Built for Corporate travel coordinators · Travel management companies · Executive assistants · Operations teams with traveling staff
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.orbitz.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Orbitz - check bookings for schedule changes
- Open the trips dashboard on Orbitz
- Check every upcoming booking against its original itinerary
- Note any schedule change, cancellation, or update since the last check
Done when Every upcoming booking has been checked for a change.
-
2
Google Drive - log each itinerary update
drive.google.com
WebRun opens Google Drive to log each itinerary update. - Open the itinerary changes log
- Add an entry for each change with the traveler, trip, and what changed
- Keep the log dated for reference
Done when Every change since the last check is logged and dated.
-
3
Twilio - text the travel coordinator
twilio.com
WebRun opens Twilio to text the travel coordinator. - Text the travel coordinator only when a booking actually changed
- Include the traveler, the trip, and the specific change
- Stay quiet when nothing changed
Done when The coordinator has been texted about every change, and nothing else.
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 WebRun rebook or cancel a trip?
No. WebRun only reads the current booking status on Orbitz. Rebooking, canceling, or changing a trip is always done by a person.
Will the coordinator get texted for routine confirmations?
No. Twilio only fires when a booking actually changes, a cancellation, schedule shift, or similar update. Unchanged bookings stay quiet.
Where is the full change history kept?
In your own Google Drive log, dated by day, so the coordinator can review what changed even before the text arrives.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.