Why Filly exists.

10:00 PM Pacific. End of a brutal day shift. Skeleton crew on nights.

A single affiliate partner in Las Vegas had just sent 60 reservation emails to our inbox, each with its own PDF attachment. All at once. Underneath that, the regular operation kept moving: clients calling, texting, emailing. Every request needed to land in Limo Anywhere before the night was out.

No automated intake for that batch. No integration to carry it across. Just an inbox on fire and a clock ticking toward midnight.

We opened the first PDF and started copying.

I remember sitting there thinking: I have almost two decades in this industry. I’ve trained hundreds of people on this system. I know every corner of this operation. And tonight, I’m a data entry clerk.

It was more than frustration. It was the exhaustion of watching capable people spend their sharpest hours on work that should not need so much of their attention.

I didn’t rage-quit or have a dramatic epiphany. I just made a decision, somewhere around the 30th PDF, that I was done accepting this as normal.

I started in luxury transportation back-office operations in 2006. I trained the teams, managed the dispatch grids, and learned exactly where the work got stuck.

The same drain kept showing up: dispatchers spending hours just getting reservations into Limo Anywhere. Requests don’t arrive through one neat channel. They come from every direction at once: emails with PDF attachments, booking spreadsheets, and documents someone has to decode and enter field by field.

Copy the name. Paste the pickup. Find the rate code. Fix the phone format when the field rejects it. Repeat.

On paper, it sounds manageable. At a busy desk, each dropdown, account suggestion, and validation rule is another detail someone has to get right while the phone keeps ringing.

We knew this work well. We also knew how much of the day it was taking.

A generic form-filler was never going to be enough. The difficult part was understanding the reservation workflow: which fields matter, which choices depend on an account, and what a validation message means in practice.

Years of training dispatchers had taught us those details. An airport belongs in its airport workflow. An incoming affiliate confirmation needs the right direction. “Home” can mean an address saved on the customer’s account, not a word to type into a street field.

We spent months turning those operational patterns into a tool built specifically for this work. The details that slowed our teams down became the details we designed around.

Filly reads the reservation request you select from an email, PDF attachment, spreadsheet, image, or pasted text. It shows you the extracted details, then fills the supported fields in Limo Anywhere.

It is built around transportation workflows, including airport and affiliate trips, stored addresses, and batches of reservations. When a supported check finds an unclear choice, Filly can stop and ask for your input.

Our experience at the dispatch desk shapes what we build and test. Each new case is another opportunity to make the workflow more reliable.

You still make the final call. Review and save manually, or choose optional Auto-Save for supported workflows. Filly takes on the repetitive entry so your attention can stay on the reservation.