Bookings
A booking is the order. Each leg is a trip with its own clock.
A liverybook booking holds the client, the lead passenger and one or more legs; each leg has its own driver, vehicle, status, price and pickup timezone. Seven booking statuses and eleven leg statuses are linked by 25 allowed transitions, enforced in the service layer, and every move is written to an append-only event log with who did it and when. Late cancellations inside the window become late_cancelled rather than cancelled, and the fee line is created without anyone typing it.
7
booking statuses
11
leg statuses
25
allowed transitions
24 h
default late-cancel window
Booking detail · capture pending
What bookings covers today.
Legs, not rows
A round trip for two sedans is one booking with four legs. A DCA to LAX itinerary shows the pickup in ET and the LA-side times in PT, because each leg stores UTC and displays the pickup location's zone.
Status machines you cannot bypass
Unassigned to assigned to notified to en route to arrived to passenger on board to arrived to completed. Cancel, late-cancel and no-show from the states that allow them. Nothing else, from anyone, including the API.
Late cancel and no-show, priced per class
The window comes from the rate for the vehicle class, or the tenant default of 24 hours. The fee is a percent of base or a flat amount and lands on the invoice as its own line.
Recurring bookings
A template with an iCal rule (every weekday at 7:10, first Monday of the month) materialises bookings hourly, a configurable number of days ahead, and tracks where it got to.
Proposals that become bookings
A trip quote from the CRM converts in one atomic step: the lead becomes a customer, the rate list attaches to the billing account, and the draft booking and legs are created. Pay and convert charges the card in the same transaction.
Flight verification
Enter a flight number on a leg and liverybook verifies it through AeroDataBox and shows a flight badge on the trip. Live delay watch with automatic pickup adjustment is on the roadmap.
RoadmapLive flight delay watch, SMS confirmations to passengers and PDF manifests are on the roadmap.
Asked on most demos.
What is the difference between a booking and a trip?
The booking is the order the client placed; a trip, or leg, is one vehicle movement inside it. Status, driver, vehicle and price live on the leg.
Can I set different late-cancel windows for different vehicles?
Yes. Each rate on a rate list carries its own late-cancel hours and fee rule, with the tenant default as the fallback.
Does liverybook support round trips and multiple vehicles?
Yes. Both in the operator app and on the public portal: a round trip with two vehicles produces four legs that share the route and time.