Skip to main content

Rider AI agents and how they book trips

The conversational flow of a rider AI agent booking a trip

P
Written by Product Team
Updated over 2 weeks ago

All our conversational agents are free flowing, our AI systems are very flexible and can engage in conversations, however they have an intended flow when trying to achieve an outcome.

Booking a New Trip Flow


  1. Initiation: The user expresses interest in booking a new trip ("I need a ride," "Book a trip," etc.).

  2. Location Collection:

    • The AI asks for pickup and drop-off locations.

    • It uses location lookup to validate addresses, offering suggestions if needed.

    • The AI confirms both locations with the user.

  3. Time Inquiry: The AI asks when the user would like to travel (date and time).

  4. Time Type: The AI clarifies if the requested time is for "leave at" or "arrive by."

  5. Service Selection: The AI identifies available transportation options and their estimated costs.

  6. Confirmation: The AI presents the trip details (locations, time, service, cost) to the user for confirmation.

  7. Booking: Upon the user's approval, the AI books the trip.

  8. Booking Confirmation: The AI informs the user that the booking was successful.

Rebooking a Previous Trip Flow


  1. Highlighting previous trips: If the user has previous trips, then the AI will highlight this and ask the user if they would like to rebook this trip.

  2. Rebooking Inquiry: The user indicates they want to rebook a recent trip ("Can I book that last trip again?").

  3. Time Inquiry: The AI asks for the desired date and time for the new trip.

  4. Estimate Retrieval: The AI retrieves the details of the previous trip and gets a new cost estimate for the requested time.

  5. Booking (Automatic): If the cost is the same or the user previously agreed to rebook similar trips, the AI may book the trip automatically. Otherwise, it might present the new time and cost for confirmation.

  6. Booking Confirmation: The AI confirms the details of the newly booked trip with the user.

Other logic


Negotiations

If there are no drivers available at the requested time, then the AI will suggest an alternative time, as close to the original requested time as possible. The functionality relies on windows & flexibilities logic which is set up on the service.

Service restrictions

If the rider tries to book a trip when there is a service restriction, e.g. you need to book 30 minutes in advanced. The the AI will tell the rider what the service restriction is.

Unmatched requests

By default AI will not be allowed to book unmatched trips, however in the Engine options on the service you are able to enable this functionality.

Did this answer your question?