> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/guestway_onboarding/about-how-guestway-fits-together.md). # About how Guestway fits together This page explains how your PMS, your booking channels and Guestway work together, from the booking to the check-out. ## Your PMS stays the source of reservations Guestway works on top of your property management system (PMS). The PMS sends your properties, listings, reservations and guests to Guestway, and tells Guestway about most changes as they happen. Some changes that your team makes in Guestway, such as reservation notes or the cleaning status, go back to the PMS. That is why the first thing a new organization does is connect its PMS. Without it, Guestway has no listings and no reservations to work with. What your PMS does not send, for example the Wi-Fi details, you add in Guestway on the listing. ## One inbox for every channel For most PMS, the guest messages of Airbnb, Booking.com and Expedia already reach Guestway through the PMS. All conversations land in one inbox, next to WhatsApp, SMS, email and the chat of the guest portal. Your team answers every guest from the same place, with the reservation details next to the conversation. You can also connect a booking channel directly. A direct connection adds to your PMS, it does not replace it: the reservations still come from the PMS. In return, messages travel faster and more actions and review features are in Guestway. Apaleo and Mews do not send guest messages at all, so for them Booking.com messages reach Guestway by email. ## From booking to check-out Once the reservations are in, Guestway takes over much of the routine around each stay: * **Automations** send the right message at the right time, from the booking confirmation to after check-out. * The **guest journey** lets guests check in online in the guest portal: their details, the agreement, protection, paid extras and ID verification, then self check-out at the end. * **Stripe** collects the money for damage waivers, security deposits and upsells. * **Smart locks** get a code for each reservation, which guests find in the guest portal. * Your **branding** makes the guest portal and the emails look like your company. The next pages set up each of these parts, one step at a time. ## Next step * [How to create your Guestway account](/guestway_onboarding/how-to-create-your-guestway-account.md) ## Related * [What syncs from your PMS](/integrations/property-management-systems/what-syncs-from-your-pms.md) * [About OTA connections](/integrations/online-travel-agencies-ota/about-ota-connections.md) * [Unified AI inbox](/inbox-and-messaging/unified-ai-inbox.md) * [Guest journey](/guest-experience/guest-journey.md) --- # 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://docs.guestway.io/guestway_onboarding/about-how-guestway-fits-together.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.