> 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/faq-on-reservations/can-i-use-routing-after-a-guest-has-checked-in.md). # Can I use routing after a guest has checked in? Yes, you can use routing **after a guest has checked in**, as it is one of the four specific junctures where the system allows this feature to be applied. In addition to being used after check-in, routing can also be configured while creating the reservation, during the check-in process, or even while checking out.
The routing button is designed for **advanced bill splitting**, which saves staff the manual effort of splitting charges at a later time. To use this tool, you click the routing button after the guest and room creation is complete and use the **"Assign to"** field to designate the number of splits required for the reservation. Within the split settings, you can specify a particular **guest name or company name** and then select the specific **revenue groups or individual items** (such as Room Tariff or Tips) that should be automatically moved to those separate folios. Once you save these preferences, the system will handle the bill splitting automatically based on your defined rules. --- # 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/faq-on-reservations/can-i-use-routing-after-a-guest-has-checked-in.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.