Airport codes, Home, and Office: getting AI reservation routing right
Why airport routing differs from street-address entry, and how to handle stored Home or Office addresses without guessing.
The short answer
Airport requests should use the appropriate airport workflow. Home and Office are references to an account's stored locations, not complete street addresses. Filly can use stored-address matches when the account and selection are unambiguous; ambiguous locations need operator review.
An airport name is not just an address
JFK, EWR, and LGA describe airport destinations, but an airport transfer can also need a terminal, airline, flight number, and a distinction between arrival time and pickup time. Entering a street address that happens to contain the airport name does not preserve all of that context. Review the routing category as well as the visible location text.
Private aviation deserves the same care. An FBO request should not become a generic commercial-terminal pickup. If the booking only names the airport and leaves the required pickup location unclear, ask for the missing information rather than inventing an FBO or terminal.
Resolve the account before interpreting Home or Office
Requests such as 'from home to EWR' and 'ride back to the office' rely on information outside the sentence. Check the matched account and its stored locations. A clearly labeled Home or Office entry can resolve the reference; several unlabeled addresses do not tell you which one the customer means.
For an ambiguous request, present the candidate addresses for selection or ask the operator to obtain clarification. Even a single unlabeled address may be a billing address rather than the requested pickup. Address availability is not the same thing as address intent. Never type 'Home' into a street field and treat that as a resolved route.
Preserve direction and return details
'From home to EWR' makes Home the pickup. 'Return home from EWR' makes it the destination. The words may be similar, but the routing roles are reversed. Check both endpoints in the preview and again after entry, particularly when working with a return request.
A reference to going home does not provide a return date, time, or flight. Only use details supported by the source or confirmed by the operator. Filly's purpose is to reduce repetitive entry while leaving these judgment calls visible, not to make an incomplete itinerary look complete.
Before you move on
- Check airport, FBO, POI, or street-address routing category.
- Match the correct account before using stored locations.
- Resolve ambiguous Home or Office references explicitly.
- Verify pickup direction and any separately requested return leg.
Product guidance from Filly AI. Supported workflows require operator review. Filly is independent of Limo Anywhere and is not endorsed by it.