> 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-platform/properties/general-listings-details.md). # General (Listings Details) The **General** settings page is where you fine-tune the visuals, addresses, access info, and other essential listing details that shape the first impression in the [Guest Portal](https://docs.guestway.io/guestway-platform/guest-portal), reduce repetitive guest questions, and keep your operational data accurate. {% @guideflow/guideflow-embed requestedUrl="" %} *** ### Accessing the General settings 1. Go to **Properties → Listings**. 2. Open the listing you want to edit. 3. The **General** tab opens by default — alongside **Guidebooks**, **Saved Replies**, **Checklists and** **Custom Fields**. *** ### Listing images When a listing is connected to Guestway, we automatically **pull images from the OTA** (such as Airbnb), so you don't have to upload everything manually. Inside each listing you can choose which image is the **primary image** — the one displayed prominently in the [Guest Portal](https://docs.guestway.io/guestway-platform/guest-portal), booking confirmations, and guest access pages — and add any additional images you want guests to see. #### Why this matters * **Control the guest experience.** The first image guests see sets expectations for the stay. * **Avoid OTA bias.** The "best" Airbnb image isn't always the most informative or relevant for an in-stay experience. * **Keep portfolios consistent.** Especially important for PMCs managing multiple brands or properties. * **Support operational clarity.** Prioritise images that help guests recognise the property easily — building façade, entrance, key areas. #### How to set or change the primary image 1. Go to **Properties → Listings**. 2. Open the listing you want to edit. 3. Navigate to the **Images** section. 4. Select an existing image pulled from the OTA, or upload a new one. 5. Set it as **Primary image**. 6. (Optional) Upload additional images if needed. Changes apply instantly to the **Guest Portal**. *** ### Wi-Fi details Guestway pulls Wi-Fi information from the OTA when it's available, but OTA Wi-Fi fields are often incomplete, inconsistent, or not formatted for guest use. To make sure guests have clear access instructions, you can manually add or edit Wi-Fi details on the listing — the values display directly in the [Guest Portal](https://docs.guestway.io/guestway-platform/guest-portal). The Wi-Fi card on a listing accepts three values: * **Network name (SSID)** — the network guests connect to. * **Password** — the connection password. * **Additional information** — anything extra guests need (e.g. *"5GHz network only — the 2.4GHz one is for smart devices"*, or special routing instructions). #### Why this matters * **Reduce guest messages.** Wi-Fi questions are one of the most common inbound requests. * **Improve the first-day experience.** Guests can connect immediately without contacting support. * **Standardise information.** Especially useful when managing listings across multiple OTAs. * **Better for virtual agents.** Clear Wi-Fi info avoids unnecessary back-and-forth in the inbox. #### How to add or update Wi-Fi details 1. Go to **Properties → Listings**. 2. Open the relevant listing. 3. Locate the **Wi-Fi** section. 4. Enter or paste: * **Network name (SSID)** * **Password** * **Additional information** (optional) 5. Save your changes. The Wi-Fi details are now visible to guests in the **Guest Portal**. *** ### Address details Guestway syncs the listing address from the OTA, but OTA addresses are sometimes incomplete, generic for safety reasons, or formatted in ways that don't help guests reach the property. Override any of the address fields directly on the listing — the values flow into Google Maps links, the [Guest Portal](https://docs.guestway.io/guestway-platform/guest-portal), and every reservation tied to the listing. The editable address fields are: * **Street** * **City** * **ZIP code** * **Floor** — which floor the unit is on. * **Apartment** — apartment number or letter. You can also set the listing to **fully override the OTA address with your manual values**. Once enabled, Guestway stops pulling address updates from the OTA and trusts what you've configured — useful when the OTA's address is intentionally vague (e.g. only the neighbourhood) but your guests need the exact location. *** ### Subscription and active state Each listing carries a **subscribed** state that controls whether Guestway treats it as active. When subscribed, Guestway: * Syncs reservations, messages, and listing updates from the connected channel. * Includes the listing in the [Unified AI Inbox](https://docs.guestway.io/guestway-platform/unified-ai-inbox), the [Multi-Calendar](https://docs.guestway.io/guestway-platform/multi-calendar), reports, and automations. * Surfaces the listing in dropdowns when configuring automations, broadcasts, or saved replies. Unsubscribing pauses all of that without deleting the listing — useful when a unit goes off the market temporarily but you plan to bring it back later. *** ### Linked operational settings A few operational settings live on the General page but are managed through dedicated areas elsewhere in Guestway: * **Cleaning team** — assign the team responsible for turnover on this listing. The team owns cleaning tasks across every reservation tied to the listing. See [Cleaning](https://docs.guestway.io/guestway-platform/cleaning). * **Smart locks** — link smart-lock devices that issue per-reservation codes automatically. See [Smart Locks](https://docs.guestway.io/guestway-platform/smart-locks). * **Static locks** — link fixed codes used for shared doors or backup keyboxes. See [Static Locks](https://docs.guestway.io/guestway-platform/static-locks). * **Property value** — record the property's value for internal tracking, insurance, or reporting. Not shown to guests. *** ### Tips * Use **clear, recognisable images** as primary visuals — not overly stylised shots. * Keep Wi-Fi information **simple and copy-paste friendly**, and use the additional info field for anything non-obvious. * **Override the OTA address** whenever it's vague, abbreviated, or hides the floor/apartment guests need. * **Unsubscribe rather than delete** when taking a unit off the market temporarily — your data, automations, and saved replies stay intact for when it returns. * Align listing visuals with your **brand or operational standards**. * Review these settings when onboarding a new listing or rolling out new virtual agents. *** ### Related pages * [Properties](https://docs.guestway.io/guestway-platform/properties) — the hub for listing-level configuration. * [Guest Portal](https://docs.guestway.io/guestway-platform/guest-portal) — where the primary image, address, and Wi-Fi details surface for guests. * [Guidebooks](https://docs.guestway.io/guestway-platform/properties/guidebooks) — local recommendations, house rules, and check-in instructions. * [Saved Replies](https://docs.guestway.io/guestway-platform/properties/saved-replies) — pre-written replies attached to the listing. * [Checklists](https://docs.guestway.io/guestway-platform/properties/checklists) — operational checklists attached to the listing. * [Custom Fields](https://docs.guestway.io/guestway-platform/properties/custom-fields) — custom metadata attached to the listing. * [Cleaning](https://docs.guestway.io/guestway-platform/cleaning) — manage cleaning teams assigned to listings. * [Smart Locks](https://docs.guestway.io/guestway-platform/smart-locks) — connect smart-lock devices. * [Static Locks](https://docs.guestway.io/guestway-platform/static-locks) — manage manual lock codes. * [Unified AI Inbox](https://docs.guestway.io/guestway-platform/unified-ai-inbox) — where the listing context surfaces alongside conversations. --- # 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://docs.guestway.io/guestway-platform/properties/general-listings-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.