> For the complete documentation index, see [llms.txt](https://fleetdocs.hyvikk.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fleetdocs.hyvikk.space/dashboard/my-bookings/view-booking-details.md). # View Booking Details {% embed url="" %} Users can see the selected booking with detailed information.

### Learn More about the booking!!! Here’s another way to phrase them more naturally: * **Map**\ Users can track the vehicle assigned to a specific booking. * **Booking Information**\ Users can view the pickup and drop-off locations for a booking. * **Fare Details**\ Users can check the fare breakdown for their booking. * **Assigned Vehicle**\ If a vehicle is assigned to a booking, its details will be displayed here. * **Driver Information**\ Users can access information about the assigned driver. > **"The information displayed here—such as driver details, fare, and assigned vehicles—is dynamic. The admin has the right to modify any of these details as needed. However, customers cannot edit or delete any booking records."** ### Driver Ratings

Customers can rate the driver after the booking is completed.

Frontend | Customer Log in | Driver rating

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://fleetdocs.hyvikk.space/dashboard/my-bookings/view-booking-details.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.