A working example
An airport pickup that is still a request
A traveler asks for an airport pickup tomorrow, gives a flight number, and prefers an SUV. The agent records those details. If no availability, price, and acceptance have been checked, the traveler has made a request; the vehicle and pickup are not reserved.
Use the word booking only after the agreed reservation path returns a durable confirmation. Until then, show the next owner and the next action.
Three possible outcomes from the same call
A captured request contains the trip details your team needs to follow up. A quote adds a price or range under the rules you have approved, but it may still need customer acceptance and an availability check. A reservation is the accepted trip recorded through the business's booking process.
The caller should hear the status in ordinary words. 'We have your request and the team will review it' is useful when the next step is manual. A confirmation number or accepted reservation status should come from the system that owns bookings, not from a polished voice response alone.
- Request: collect pickup, destination, date, time, passenger and vehicle needs, then identify the follow-up owner.
- Quote: show the price basis and any items still subject to review.
- Booking: verify the required acceptance, payment or deposit step if applicable, and the reservation record.
Design the path around your rules
Start with the trip types your team handles repeatedly and list the facts required for each. Airport pickups, hourly service, and unusual stops may need different questions. Decide who can approve exceptions, how a caller gets an update, and what happens if a connection is unavailable.
If you already have a booking system, Volimox reviews the actions it supports and the access you can authorize. A full-system discussion is appropriate when the business also needs a branded website, online booking, and an operations portal. Neither route makes every phone inquiry a confirmed trip.
Read the product tour as a demonstration
The Volimox limo tour combines a real operator's underlying system with fictional Example Limo records and illustrated screens. It shows the kind of customer and operations path to discuss; it is not evidence that a new operator is live. The reservation screen, payment status, and manual driver assignment should be reviewed as separate steps.
For a customer rollout, test the exact path your team expects: normal trip, missing detail, changed trip, failed payment or handoff, and an exception that needs a person. Keep the request status visible throughout.
Before setup
Questions to bring to the conversation
- 01Define the minimum trip details for each ride type.
- 02Name the system or person that can accept a reservation.
- 03Decide when a quote may be shown and what remains conditional.
- 04Write the exact message a caller receives for request, quote, and confirmed booking.
- 05Walk through an unavailable vehicle and a failed handoff before using the workflow with customers.
Common questions
Clear answers before a pilot
If the agent has all trip details, is the ride booked?
No. Complete details make a request actionable. A booking also needs the agreed availability, acceptance, and reservation steps to finish.
Can a quote be final before staff review?
Only if the business has approved that pricing path and the connected system can apply the required rules. Otherwise it should be described as a quote for review.
Does driver assignment happen automatically?
The current limo product description shows manual driver assignment in the operations portal. Discuss any different dispatch requirement as a separate workflow.
Can I use my current booking tools?
Possibly. The specific read and write actions, account access, and failure path must be checked for your tools before a booking outcome is promised.
See the next step
Explore the limo product tour
See the branded booking and operations path, including its demo boundaries.
Continue