AI · · 6 min read · Vinny Bonfim
AI reservations: turn booking emails, PDFs and screenshots into trips
The most useful AI in a limo office is the one that types the trip in for you, shows what it found and what's missing, and waits for a dispatcher to say yes.
AI for limo companies is most useful at the least glamorous step: typing the trip in. In LimoGrid, a dispatcher pastes a booking email or uploads a PDF itinerary or a screenshot of a text. The AI pulls out the trip, shows what it found and what is missing, and creates the reservation only after the dispatcher reviews it.
That last part is the whole design. The AI proposes. The dispatcher confirms. Nothing lands on the board because a model guessed.
This post covers what the feature does, the kinds of input it handles, why the review step matters more than the extraction, and where it sits in the rest of your limo reservation software.
What are AI reservations in limo software?
An AI reservation is a trip created from unstructured input instead of a form. Most bookings do not arrive as clean fields. They arrive as a forwarded email thread, a travel agency PDF, or a photo of a text message someone's boss sent at midnight. Somebody in your office reads that, opens the reservation screen and retypes it. Pickup time, address, flight, passenger name, phone, vehicle, number of passengers, return leg.
In LimoGrid this is called AI Create Reservation. You give it the raw material. It reads it, fills in the reservation fields it can support from the text, and flags the ones it cannot. You check the result, fix or add what is missing, and save. The reservation is then an ordinary reservation: it shows up on the dispatch board and goes through the same offer, billing and notification flow as one you typed by hand.
What kinds of booking input can it read?
Three kinds cover most of what a limo office receives outside the booking widget.
| Input | Typical source | What is often missing |
|---|---|---|
| Pasted email | Executive assistant, travel desk, repeat client | Passenger phone, vehicle type |
| PDF itinerary | Travel agency, event planner, corporate travel | Pickup address on the return leg |
| Screenshot of a text | Client texting the owner's cell | Date, if they wrote "Friday" |
The assistant email
The assistant who books by email at 11pm writes the way people write: "Can you get Mr. Chen from the airport Thursday, he's on the 4:40 from Chicago, then to the hotel, and back out Saturday morning." That is two trips, a flight, a relative date and no hotel name. The AI can pull out what is there and show what is missing.
The PDF itinerary
A travel agency PDF is usually complete but long. The trip details sit between a hotel confirmation and a dinner reservation. Uploading the file saves the dispatcher from hunting through three pages for the flight number.
The screenshot
Clients text the owner. The owner screenshots it and sends it to the office. Uploading the screenshot is faster than retyping it, and nobody has to squint at a phone to copy a flight number.
Why is the review step the point?
Because a wrong reservation is worse than no reservation.
If an AI books the wrong date, you find out when the passenger calls from the curb. If it invents a pickup address because the email didn't have one, a driver goes to the wrong building. Extraction that is "usually right" is not good enough for a business where one miss costs a client.
So the screen that matters is the review screen. It splits the result into two parts:
- What it found. The fields it could fill from the text: names, times, addresses, flight, vehicle, passengers.
- What is missing. The fields a reservation needs that the text did not answer.
The dispatcher reads both, corrects anything that looks off, fills the gaps (often with one call or one reply email), and then creates the reservation. The decision stays with a person who knows that "the usual car" for this client means the black Suburban, not the sedan.
This is also why we don't publish accuracy percentages. The honest answer depends on how messy your inbox is. What we can say is how the system is designed: it shows what it found and what is missing, and a person checks both before anything is saved.
The AI proposes, the dispatcher confirms. Nothing is saved until a person has reviewed what the AI found.
How does it fit into dispatch, billing and payments?
Once saved, an AI-created reservation is not special. That matters, because a feature that lives in its own corner of the app becomes one more place to check.
- Dispatch. The trip appears on the dispatch board and calendar, in the trip's local timezone, and goes out through the event-driven offer queue like any other job.
- Flights. If the input included a flight, flight tracking takes over from there. We cover how that works in flight tracking for limo dispatch.
- Accounts. Emails from an assistant or travel desk usually belong to a corporate account with related accounts: one booker, several passengers. Put the reservation on the right account and it ends up on the right invoice. See billing and corporate accounts.
- Payment. If the client pays by card, you can send a PayLink for the reservation. The trip is already on the page; the passenger adds a tip and pays, on your own merchant account. More on that in limo company credit card processing.
The feature also runs in the admin app, so the owner who gets a screenshot on a Saturday can turn it into a reservation from the admin app instead of forwarding it to the office.
What should you ask any vendor about AI reservations?
If you are comparing platforms, the demo will always show a clean email turning into a perfect trip. Ask for the messy case instead.
- Bring a real email from your inbox, with a relative date and a missing phone number. What does the screen show?
- Does it tell you what it could not find, or does it fill every field?
- Can you edit before saving, or do you fix it afterward?
- Does it handle PDFs and images, or only pasted text?
- Does the saved trip behave exactly like a manual one for dispatch, billing and notifications?
- Which plan is it on, and is there a per-use charge?
For a wider checklist across the whole platform, see our buyer's guide to limo dispatch software.
Which LimoGrid plan includes AI reservations?
AI reservations are part of the Pro plan, which also includes the full dispatch board with live driver tracking, corporate accounts, billing and driver pay, PayLink and 24/7 support. Pro is $179.99 a month plus a $299 one-time setup, up to 500 reservations a month, with unlimited users. There is no per-trip charge, and going over the reservation limit never blocks a job. Details are on the pricing page.
Frequently asked questions
Does the AI create reservations without a person checking them?
No. It shows what it found and what is missing, and the dispatcher reviews and confirms before the reservation is created. That review step is deliberate.
What files can I use with AI Create Reservation?
You can paste the text of an email, or upload a PDF or a screenshot. Typical examples are an assistant's booking email, a travel agency itinerary and a screenshot of a client's text message.
What happens when the email leaves something out?
The review screen shows what is missing. The dispatcher fills them in, usually after a quick reply to the client, and then saves.
Is an AI-created reservation different from a manual one?
Once saved, no. It goes on the dispatch board, into the offer queue, onto its account and through the same notifications and billing as any other trip.
If your office retypes bookings from email every night, book a demo and bring one of those emails with you. We will run it through AI Create Reservation while you watch.
About the author
Vinny Bonfim — Chief Technology Officer, LimoGrid
Fifteen years in software and five running black car operations — the rare combination where the person designing the dispatch screen has also worked a Friday night on it.
More about the team