Request pilot access
Tell us which operators will use Filly and which inbox workflows your team relies on.
Filly user guide
A simple visual guide to every major Filly workflow, from the first Chrome setup to batches, stored addresses, confirmations, history, and memory.
SELECT
Choose the booking request
PREVIEW
Check what Filly found
FILL
Follow the visible checkpoints
COMPLETE
Review and save your way
01 · INSTALL
Pilot users receive access directly from the Filly team. Once Filly is publicly available, installation will use the standard Chrome Web Store flow.
Tell us which operators will use Filly and which inbox workflows your team relies on.
Use the private pilot invitation now, or Add to Chrome when the Web Store listing is available.
Open Filly and sign in with the email approved for your team. Use Forgot password if needed.
Open Chrome's Extensions menu and pin Filly so its launcher is easy to reach.
Sign in to the supported inbox and Limo Anywhere in the same Chrome profile.
Start with a representative booking, check Preview, and keep manual Save control for the first run.
Your pilot invitation includes the current approved installation path. If the extension does not appear after installation, contact Filly support before changing Chrome settings.
02 · FIRST FILL
The source may change, but the operator workflow stays familiar.
Open one booking or add the file, screenshot, spreadsheet, or text you want Filly to process.
Check the passenger, account, routing, flight, service, vehicle, notes, and number of trips.
Watch the live checkpoints while Filly enters supported fields into Limo Anywhere.
Save manually, or use optional safeguarded Auto-Save for the workflows your team approves.
PREVIEW
Nothing enters the form yet.
PROGRESS
Follow each live checkpoint.
SUCCESS
Review the completed reservation.
03 · WAYS TO IMPORT
Filly only processes the message or document you choose.
Use Import while the booking is open in Gmail, Outlook Web, Front, or Helpwise.
Add a supported PDF, spreadsheet, image, or other booking attachment.
Paste booking text or a copied screenshot directly into the drop zone.
Use selected Gmail rows, a multi-trip PDF, or an XLSX, XLS, or CSV file.
04 · USE-CASE PLAYBOOK
Each card shows when to use the workflow, what to do, and the detail that deserves a final check.
A reservation request is open in Gmail, Outlook Web, Front, or Helpwise.
Do this
Final check: Confirm the requested trip, account, date, and routing before entry begins.
The important trip details are inside an attachment or image.
Do this
Final check: Use clear, readable files. Confirm that the preview found every page or trip you expect.
A client or affiliate sends several reservations together.
Do this
Final check: Follow the status of each item. If one needs review, resolve that trip before continuing.
Several visible Gmail rows each contain a booking request or attachment.
Do this
Final check: Current guidance is up to 12 selected messages and 18 MB total. Wait for Gmail's attachment tray to finish loading.
The passenger or booking contact belongs to an account already in Limo Anywhere.
Do this
Final check: Do not approve an uncertain account only because the name looks similar. Confirm the contact or company details.
No appropriate existing account is available and a new account is required.
Do this
Final check: Make sure the request truly calls for a new account before creating one.
The request says 'from home,' 'to the office,' 'ride back home,' or similar wording.
Do this
Final check: The result should be a stored address selection, not the word 'Home' or 'Office' typed into a street field.
The route includes an airport code, flight, private terminal, venue, or street address.
Do this
Final check: An airport should appear in the airport workflow, not as a street address.
The source explicitly provides a return, ride back, second leg, or multiple vehicles.
Do this
Final check: Filly should not create a return leg unless the source provides return intent and usable details.
Another operator sends an affiliate confirmation or your team is assigning the work outward.
Do this
Final check: A Farm-Out Confirmation received from another operator is generally your farm-in.
Filly needs an account, address, route, or other operator decision.
Do this
Final check: Use Resume for the current fill. Start New Reservation is only for intentionally beginning another trip.
The source explicitly requests a confirmation or the operator chooses to send one.
Do this
Final check: An email address alone is not permission to send. A 'do not send' instruction always wins.
05 · AFTER THE FILL
Use these screens to review work, improve recurring matches, and tell the team what happened.
Review recent fills, search and filter results, check time saved, inspect details, and export supported history to CSV.
Review, edit, or remove approved account and routing shortcuts. Current booking details take priority over memory.
Manage account details, routing preferences, help tips, authorized testing, and other available preferences.
Rate the fill, choose what stood out, and add a short note. Do not include passenger or customer information.
Use the top tips, feature tours, What's New, and shortcuts to learn the workflow without interrupting a fill.
Use light or dark mode, open Filly from the browser toolbar, or use the page launcher where available.
06 · HELP & SAFETY
Filly is designed to assist the operator, not remove the operator's responsibility for the reservation.
NEED HELP?
Include what you expected, what happened, and a screenshot with customer details removed.