Fill the runs that matter. Keep riders informed on storm nights.
Before we automate anything, we look at last season: which runs to keep, move or drop. Then we build the texts and the after-hours answers inside the booking system you already run. You approve every message template.
What we'd build
Typical scope, not a measured resultSeason review.
We line up your departures with the flights that actually land, competitor schedules and your own bookings. You see which runs to keep, move or drop, and where travelers arrive with nobody there to carry them.
Delay and storm texts.
Flights, weather and road closures are watched for you. Riders get a real pickup time before they need to call.
After-hours answers.
"Where is my driver?" and "Is the bus still leaving?" get answered at 11 pm. When the system isn't sure, it asks the guest to call you.
Group and charter quotes.
An emailed request becomes a priced draft quote for you to check and send.
How it works
- 01
A 20-minute call. Your season, your routes, your worst night last winter.
- 02
A review on last season's data. Read-only exports, guest details removed.
- 03
We build what pays first, inside the booking system you use today. You approve the wording, and you can switch any of it off.
Who builds it
Felix Steinhauser. 14 years at SIXT, most recently Director of AI Strategy & Delivery. Now Founder of Vectimo, building AI for operations teams in transport and property management.