Skip to content

Glossary

Every dispatch term, defined.

Farm-in, FBO, IATA, PAX, deadhead — the vocabulary Limo Anywhere operators speak, and how Filly handles each one.

Farm-in
A reservation received from another operator (a broker) who has subcontracted the trip to your fleet.
How Filly handles it: Filly detects farm-in bookings automatically by matching the sender's email domain to an existing broker account in Limo Anywhere, and sets the dispatch type radio accordingly.
Farm-out
A reservation your dispatch team sends to another operator to fulfill on your behalf.
How Filly handles it: Filly sets the dispatch type to farm-out and preserves the original broker relationship in the notes and billing fields.
FBO (Fixed-Base Operator)
A private aviation terminal where charter jets and private aircraft handle passenger pickups and drop-offs.
How Filly handles it: Filly detects FBO names like Signature Flight Support, Jet Aviation, and Atlantic Aviation, then fills the FBO tab with name, address, and tail number.
IATA code
The three-letter airport identifier used by airlines and dispatchers (e.g., JFK, LAX, ORD).
How Filly handles it: Filly resolves IATA codes to full airport names and terminals automatically, and cross-references live flight data via AirLabs.
PAX (Passenger count)
Shorthand for the number of passengers on a trip; drives vehicle assignment and pricing.
How Filly handles it: Filly reads PAX counts from email text or attachment tables and fills the passenger count field along with any child seat requirements.
Deadhead
A leg of a trip with no revenue passenger — the driver repositioning to or from a pickup or drop-off.
How Filly handles it: Filly handles deadhead legs when the source email specifies them, but by default fills only the revenue portion of the trip.
Round trip
A booking with both an outbound leg and a return leg, often on the same or a later day.
How Filly handles it: For supported bookings, Filly maps return date, time, flight, and routing details into the Limo Anywhere round-trip workflow for review.
Multi-stop
A reservation with two or more intermediate stops between pickup and final drop-off.
How Filly handles it: Filly supports multi-stop trips including address, POI, and FBO stops — sequentially and in the correct order.
POI (Point of Interest)
A named location like a hotel, venue, or landmark used as a pickup or drop-off point.
How Filly handles it: Filly recognizes POI names in booking emails and fills the POI tab in Limo Anywhere with the location, address, and any relevant notes.
Airline / Flight lookup
Verifying a flight's schedule, terminal, or gate against live airline data.
How Filly handles it: When a supported booking is missing flight timing, Filly can query AirLabs and present available schedule data for review.
Batch fill
Filling multiple reservations at once from a spreadsheet or multi-page PDF.
How Filly handles it: Filly's batch fill previews every trip inside a PDF or Excel file, then fills them sequentially in Limo Anywhere with automatic pauses between trips.
Dispatch type
How a reservation is fulfilled — in-house, farm-in from a broker, or farm-out to another operator.
How Filly handles it: Filly sets the correct dispatch type radio in the Limo Anywhere new-reservation form based on sender domain matching.
Tail number
The unique registration identifier for a private aircraft (e.g., N123AB), used to match FBO arrivals.
How Filly handles it: Filly extracts tail numbers from private jet booking emails and fills them into the FBO tab alongside the FBO name and terminal address.
Account memory
A system that remembers approved corrections made for a specific account so they can be reused on matching bookings.
How Filly handles it: Filly can save approved account-specific rules and apply them when relevant details match on a future booking.
Team memory
Approved operating rules shared across eligible seats on a dispatch team.
How Filly handles it: Eligible multi-seat Filly packages can share approved account and sender rules across dispatcher seats.
Airline dropdown matching
Selecting the correct airline in a form dropdown based on the flight code or airline name in a booking.
How Filly handles it: Filly parses flight codes like 'DL 447' and selects the correct airline (Delta) in the Limo Anywhere dropdown automatically.
Child seat detection
Identifying whether a passenger requires an infant, booster, or toddler seat.
How Filly handles it: Filly parses child seat mentions ('1 booster', 'infant car seat') and fills the seat requirements in the reservation notes and equipment fields.
PAUSE and learn
A feature that pauses an automated fill so a dispatcher can correct a field, then remembers the correction.
How Filly handles it: Filly pauses at any field where the source data is ambiguous. Correct it once, and the corresponding account memory rule ensures Filly won't ask again.

See how Filly handles common transportation workflows.