How it works
From the reservation you already have to a mobile experience your customer actually opens.
TripPass is not a dispatch system, a booking engine or a ticketing platform, and it does not ask you to move off the tools you run today. It takes information you already produce and turns it into the part your customer sees.
- 01
Your information reaches TripPass
Nothing about your existing setup has to change. Pick whichever route is least work for your team — most operators start with email forwarding because it needs no development at all.
- CSV upload, with a saved column mapping you reuse each time
- Email forwarding to a private address, parsed automatically
- REST API with your own key, for dispatch systems that can post out
- Webhooks, with signature verification on every delivery
- Manual entry, for the one-off trip or the late addition
- 02
TripPass normalises and de-duplicates it
Reservations arrive in different shapes and often arrive twice — an original and an amendment. TripPass reconciles them into one record per trip and keeps a history of what changed.
- Duplicate confirmations are matched, not stacked
- Amendments update the live experience rather than creating a second one
- Anything ambiguous goes to a review queue instead of being guessed at
- Every change is recorded so you can see what the customer saw and when
- 03
The experience is built in your branding
Your name, your logo, your colours, your phone number, your booking link. TripPass appears as a single quiet line at the bottom of the page.
- Company name, logo and colour applied across every screen
- Your dispatch number and booking link on every trip
- Custom domain available on the top plan
- Content sections shown or hidden per mode and per account
- 04
Your customer opens one link
Sent by text or email, or scanned from a QR code at a show entrance. It opens in the phone's browser and can be saved to the home screen.
- No download, no account, no password
- Each link is private to one trip or one attendee session
- Links expire on a schedule you control
- Works on any modern phone, including older devices
- 05
It keeps itself current
The experience is not a snapshot. As the trip or the show progresses, the page the customer already has open changes with it.
- Trip stages move from confirmed through to completed
- Flight status and terminal information refresh for airport work
- Event announcements reach attendees who already opened the link
- Ask Margo answers questions using only what you have published
What TripPass deliberately does not do
Being clear about the edges saves everyone time. TripPass is the customer-facing layer, and it stops there.
Not a dispatch system
Not a booking engine
Not ticketing or registration
Questions
Before you ask.
How does TripPass get my reservations?
Four ways, and you can use more than one. Send a CSV export, forward your confirmation emails to a private address we give you, post them to the API, or send them from your dispatch system's webhook. TripPass reads them all into the same normalised record.
Do I have to replace my dispatch or booking system?
No. TripPass sits alongside whatever you already run. It reads your reservations and produces the customer-facing experience; your dispatch, pricing and billing stay exactly where they are.
What does the customer actually receive?
A link, usually by text message, or a QR code they scan at an event. It opens straight in their phone browser — no download, no login, no account.
How long does setup take?
A transportation operator can usually send a first live trip within the same week. An event built from an exhibitor spreadsheet takes a few days including a review pass.
See what your passengers or attendees would get.
A short walkthrough of the real thing, using your kind of trip or your kind of show.
Ask for 774-436-MARGO if it is easier to remember.