> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/front-office-module/fo-reserv/reservation-creation/itinerary-booking.md).
# Itinerary Booking
Steps to create a Itinerary Booking
Itinerary booking is done for those Guests who want to create multiple bookings for different locations that fall within the same property/group.
### Steps to Create an Itinerary Booking
1. Go to Reservation and click the Itinerary Booking sub menu
2. Click on the plus icon (+) on the itinerary booking menu to add or select a property.
* Next, select the property from the property field
4. After selecting the property, double-click on the property name to open the reservation detail screen.
5. Fill in the quick reservation details as shown below and save.
Tip: You can also edit the rate, route, add a package, and add other charges from this screen as well.
6. To add a new reservation, click on the plus icon (+) within the itinerary screen. This line can be added to book another property for the same guest.
7. Select the new property from the property field.
8. Double-click on the property to open the reservation detail screen.
9. Once the detail screen opens, enter the reservation details and save the reservation for the new location.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rbsgo.com/front-office-module/fo-reserv/reservation-creation/itinerary-booking.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png?alt=media)
.png?alt=media)
