Changelog
October 2026: the rebrand and the run board
What shipped in liverybook in October 2026: the new name and brand, the dispatch run board, the booking wizard, loyalty, email, affiliates and flight badges.
Updated
October 2026 was the month TripDex became liverybook, and the month the dispatch run board shipped. Here is what changed, in the order a dispatcher would notice it.
TripDex is now liverybook
The product has a new name, always lowercase, and a new brand system called Midnight and Marigold. The operator app ships with light and dark themes under the new palette, and the customer portal picks up each tenant's own colours on top of it. The old TripDex name will linger in a few internal places for a while; the rebrand doc on the site covers what is still in transition. The descriptor has not changed: liverybook is the operating system for ground transportation.
The dispatch run board
The run board is the main dispatch screen and is now live. It has a 16-column trip table with a per-user column visibility toggle, four stat cards (active trips, pending dispatch, available drivers, completed today), and Today, Tomorrow and 24-hour filters. An upcoming rail on the right lists unassigned trips soonest first.
Driver, vehicle, status and subcontractor are inline selects on each row. Farmed-out trips show Sub Driver and Sub Vehicle columns. Two dispatchers cannot assign the same trip at once; optimistic locking refuses the second save.
Updates arrive over a WebSocket for trip status changes, new bookings, cancellations, flight delays and GPS updates, and the board also auto-refreshes every 30 seconds.
Public booking wizard with guest checkout
The customer portal at each tenant's slug address now has a public four-step booking wizard: trip, vehicle, details, checkout. Guests can book and pay without an account, and guest bookings are attached to the account if the same email registers later.
The wizard supports a round trip toggle and multiple vehicles with quantities on one booking. Prices come from the tenant's default rate group, including its seasonal schedule, and bookings auto-confirm with a confirmation email.
Loyalty points
A points program per tenant, with earning rules for base spend, service type, vehicle class, signup and referral. Points expire first in, first out. Redemption is capped per booking. Every movement is recorded in an append-only ledger. Portal customers see their balance after logging in. Six operator endpoints and three portal endpoints cover setup and use.
Multi-tenant email
Each tenant can now send transactional email from its own Postmark or SendGrid account. Credentials are encrypted at rest with Fernet. Nine templates ship: booking confirmation, invoice reminder, CRM sequence, proposal sent, portal welcome, password reset, compliance expiry, booking cancelled, and payment receipt. Bounces are handled and a per-tenant suppression list is kept.
Affiliate contacts, driver roster and compliance gate
Affiliate records carry a tier (standard, preferred, strategic), an approval status (pending, under review, approved, suspended, blocked) and an insurance expiry date. From those, liverybook computes a compliance status (compliant, expiring soon, expired, pending, blocked) and sends expiry alerts at 60, 30 and 7 days.
Affiliates now have contacts with roles and a driver roster with licence details. A trip cannot be farmed to an affiliate that is not approved and compliant. Affiliate drivers get a tokenised link per trip and can set statuses from en route to completed; they cannot cancel or mark a no-show.
Flight verification badges
Trips with a flight number are verified through AeroDataBox and show a flight badge on the trip, so a delayed arrival is visible on the board without opening the booking.
Also in this release
Bookings are split into a Booking (the order) and one or more BookingTrips (legs), with 7 booking statuses, 11 leg statuses and 25 allowed transitions written to an append-only event log. Late-cancel and no-show fees are created as invoice lines automatically. Every time is stored in UTC and displayed in the leg's pickup timezone. The REST API under /api/v1/ has OpenAPI docs, API-key auth with scopes, and webhooks with retries.
On the roadmap
Three things operators ask about most are not built yet. A driver mobile app, which is what brings live GPS and in-app status updates for an operator's own drivers. SMS through Twilio. And Stripe Connect onboarding, so operators can connect their own Stripe account without liverybook configuring the key during setup. Card collection itself is live in both the operator app and the portal checkout.
Tenants are still created by liverybook rather than by self-serve signup. If you want a login, book a demo.