> 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/self-checkin.md). # Self-Checkin * [Allow Pre Registration](/front-office-module/fo-reserv/self-checkin/allow-pre-registration.md) * [Allow Self Checkin](/front-office-module/fo-reserv/self-checkin/allow-self-checkin.md) * [Document Template](/front-office-module/fo-reserv/self-checkin/document-template.md) Self-check-in enables a contactless guest onboarding process with pre-validated data, reducing front desk workload and improving efficiency. * A reservation is created for the guest. * A pre-registration link is sent to the guest. * The guest enters personal details, uploads ID proof, photographs, and provides a digital signature. * The submitted data is populated in the ‘Allow Self Check-in’ window. * The system validates the data against existing records. * If new or updated data is detected, the system prompts for confirmation before updating the guest profile. --- # 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/self-checkin.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.