Batch reservation entry in Limo Anywhere: a dispatcher’s checklist
How to review multiple booking emails, PDFs, or spreadsheet trips without losing track of missing inputs, duplicates, or incomplete reservations.
The short answer
A safe batch workflow checks the recognized trip count before entry and tracks every reservation separately. Filly supports batch intake and sequential filling, but the dispatcher should reconcile imported trips against the selected sources before starting.
Count trips, not just attachments
Three selected emails do not necessarily mean three imported reservations. One PDF may contain two trips, another email may repeat a previous request, and an attachment may fail to load. Compare the recognized trips with the actual requests before approving the batch. If the preview reports fewer trips than expected, investigate the missing input rather than assuming it is already in the queue.
Keep revised and original requests distinguishable. A return leg belongs in the batch only when the source provides return details; an outbound booking alone is not evidence of a return date or time. Separate unclear requests so they do not become plausible-looking entries.
Review each trip before running the queue
Look at passenger, date, time, pickup, destination, account, and vehicle for every recognized trip. Repeated passengers are not automatically duplicates: the same traveler may have an arrival and a departure. Conversely, two differently named files can contain the same reservation. Compare the trip details and references, not filenames alone.
For a spreadsheet, use clear column headings and keep each trip's information together. Review any notes that apply to several rows. Do not assume a vehicle or billing preference in one row applies to the entire file unless the source says so.
Treat completion as a per-reservation result
Filly works through recognized reservations in order with individual status. If a trip needs input, resolve that trip before treating the batch as complete. Keep track of what was filled, what was saved, and what remains unresolved. These are separate questions, especially when your team uses manual saving.
Requested confirmations also need per-trip verification. Before retrying after an interruption, check the existing reservation and delivery state to avoid duplicate entry or duplicate email. Batch speed is useful only when the final count can be reconciled with the source list.
Before you move on
- Reconcile source count with recognized trip count.
- Check duplicates, revisions, and explicit return details.
- Review each trip's account, vehicle, and route.
- Reconcile filled, saved, unresolved, and emailed results separately.
Product guidance from Filly AI. Supported workflows require operator review. Filly is independent of Limo Anywhere and is not endorsed by it.