> 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_changelog/july-2026.md).

# July 2026

Guest self check-out, house rules as their own step, the fees step out of "coming soon" and phone number search.

Versions this month: web app 1.102.0 – 1.109.0 · guest portal 1.34.0 – 1.40.0

## New

### Guest self check-out

Guests can now check themselves out. On departure day, they review your check-out instructions and complete check-out from their booking screen. The completed check-out shows on the reservation.

Who it affects: properties that use the guest portal. Action needed: none.

Technical details: web app 1.102.0, guest portal 1.35.0.

![](https://2896135848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uXjK7izLPx9cqNcRehh%2Fuploads%2F8nyNNU6oyGZcBVv7TdWq%2Fchangelog-2026-07-1.png?alt=media)

Learn how to [set up self check-out](https://docs.guestway.io/guest-experience/guest-journey/how-to-set-up-self-check-out).

### House rules as their own step

The agreement step in guest journeys now has separate sections for the rental agreement and house rules. Both support rich formatting, images, and booking details that fill in automatically.

Who it affects: properties that use guest journeys. Action needed: none.

Technical details: web app 1.102.0, guest portal 1.34.0.

![](https://2896135848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uXjK7izLPx9cqNcRehh%2Fuploads%2FBEU5bYJTLUJ9L6o8qJMJ%2Fchangelog-2026-07-2.png?alt=media)

Learn how to [set up the agreement step](https://docs.guestway.io/guest-experience/guest-journey/how-to-set-up-the-agreement-step).

### The fees step is fully available

The fees step in pre-check-in is no longer "coming soon". You can show guest fees clearly, control how they appear per booking source, and mark a fee as no charge when it shouldn't be offered.

* Additional fees can now be a percentage of the stay. This is useful for anything that grows with the booking, such as city tax.
* Additional fees now support VAT percentages, like your other chargeable items.

Who it affects: properties that charge guest fees. Action needed: none.

Technical details: web app 1.103.0.

![](https://2896135848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uXjK7izLPx9cqNcRehh%2Fuploads%2FkdmBattL7LTFzfIPN749%2Fchangelog-2026-07-3.png?alt=media)

Learn how to [add fees to the guest journey](https://docs.guestway.io/guest-experience/guest-journey/how-to-add-fees-to-the-guest-journey).

### Search by phone number

You can now find guests and reservations by phone number. When a number is the only detail you have, that is now enough.

Who it affects: all users. Action needed: none.

### A guest portal banner in your branding

You can now upload a dedicated banner for the guest portal. It carries over when you duplicate a branding setup.

Who it affects: all properties. Action needed: none.

Technical details: guest portal 1.38.0.

![](https://2896135848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uXjK7izLPx9cqNcRehh%2Fuploads%2FmyVj9C2D3keg4oU87Cuu%2Fchangelog-2026-07-7.png?alt=media)

Learn how to [create a branding profile](https://docs.guestway.io/guest-experience/branding/how-to-create-a-branding-profile).

### Preferred guest email or phone number

You can now set a primary email or phone number per guest. Future messages use it when available.

Who it affects: all users. Action needed: none.

Technical details: web app 1.102.0.

![](https://2896135848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uXjK7izLPx9cqNcRehh%2Fuploads%2Fn7M4y0iDSHDGzlnU9te9%2Fchangelog-2026-07-8.png?alt=media)

### A personalized redirect after pre-check-in

You can now send guests to the right follow-up page automatically once they finish pre-check-in.

Who it affects: properties that use pre-check-in. Action needed: none.

Technical details: web app 1.97.0, guest portal 1.34.0.

### Tidier guidebook editing

Image and icon previews in the guidebook editor now match what guests see. You can also adjust an image to fit the thumbnail you want.

Who it affects: properties that use guidebooks. Action needed: none.

Technical details: web app 1.105.0.

![](https://2896135848-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0uXjK7izLPx9cqNcRehh%2Fuploads%2FzUOV7krrnZmCvBq5UMcR%2Fchangelog-2026-07-9.png?alt=media)

Learn how to [create a guidebook](https://docs.guestway.io/properties/guidebooks/how-to-create-a-guidebook).

### Longer automation delays

Automation delays can now run up to two weeks. That leaves room for real post-stay follow-ups, like review reminders.

Who it affects: teams that use automations. Action needed: none.

See [how automations work](https://docs.guestway.io/reservations-and-operations/automations).

### More Apaleo billing from Guestway

Teams on Apaleo can now retrieve guest bills, add bill lines and record payments from Guestway.

Who it affects: Apaleo customers. Action needed: none.

See [how billing works with Apaleo](https://docs.guestway.io/integrations/property-management-systems/apaleo/apaleo-billing).

## Improved

### Clearer protection settings, with new defaults and names

Protection settings are easier to configure, and the wording now matches what guests see:

* A card hold is now the default, instead of an immediate charge.
* Per night is now the default pricing, instead of per stay.
* "Security deposit" is now called **deposit**. "Damage waiver" is now called **basic protection** or **full protection**.

Who it affects: properties that use protection. Action needed: none. If you set up new protection options, check that the defaults suit you.

Technical details: web app 1.106.0.

Read [how security deposits and damage waivers protect your properties](https://docs.guestway.io/guest-experience/guest-journey/about-protection).

### Smaller improvements

No action is needed for these improvements.

* **The agreement step now comes right after trip details.** This matches the order guests go through pre-check-in.
* **Guest journey setup names the properties that still need a deposit.** The warning updates as your selection changes, so you don't have to work it out.
* **Clearer warnings when a connected system can't support your setup.** Payment and settlement actions only appear where your PMS supports them. You get a clear message instead of a failure later.
* **Access details are easier for guests to scan.** Available doors and codes are clearer, and it is obvious which access option a guest is using.
* **A polished guest portal.** Booking details, pending payments, chat, room controls and navigation are cleaner. Your branding applies more consistently, and small screens work better.
* **Faster first load.** Pages become usable faster when you first open the platform.
* **Easier to browse knowledge entries.** Clearer previews, plus better filtering and sorting, help you find the entry you need.
* **Better AI reply suggestions.** Guest, reservation and amenity details are loaded before a suggestion is written. This includes extra Airbnb listing information where available. Answers about a specific stay are more accurate.


---

# 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_changelog/july-2026.md?ask=<question>&goal=<user_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.
