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

# January 2026

Organization-wide two-factor authentication, a Currently staying inbox filter, guidebooks and saved replies from the inbox, and Arabic in the mobile app.

Versions this month: web app 1.67.0 – 1.68.0 · guest portal 1.20.0 – 1.21.0 · mobile app 1.2.23

## New

### A Currently staying filter in the inbox

You can now filter the inbox to guests who are on site right now, so your team can prioritize and respond faster.

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

Technical details: web app 1.67.0.

Learn how to [filter conversations and save a view](https://docs.guestway.io/inbox-and-messaging/unified-ai-inbox/how-to-filter-conversations-and-save-a-view).

### Create guidebooks from the inbox

You can now create a guidebook straight from an inbox conversation, without switching screens.

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

Technical details: web app 1.67.0.

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

### Create saved replies from the inbox

You can now turn a real conversation into a reusable saved reply, directly from the inbox.

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

Learn how to [create a saved reply](https://docs.guestway.io/inbox-and-messaging/saved-replies/how-to-create-a-saved-reply).

### An in-app support widget

You can now get help without leaving Guestway.

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

Technical details: web app 1.68.0.

### Arabic and right-to-left support in the mobile app

The mobile app now supports Arabic, with right-to-left (RTL) layout.

Who it affects: Arabic-speaking users. Action needed: update the Guestway mobile app to 1.2.23 or later.

## Improved

### Smaller improvements

* **A clearer Properties page.** The **Properties** interface is refreshed and easier to navigate. No action needed. Technical details: web app 1.67.0.

## Security

* You can now require two-factor authentication (2FA, a second check when signing in) for your whole organization, instead of per role. Who it affects: organizations that want stricter sign-in security. Action needed: none. Technical details: web app 1.67.0. Learn how to [require two-factor authentication for your organization](https://docs.guestway.io/account-and-administration/holding-settings/how-to-require-two-factor-authentication).
* Only Super Operators can now block email domains. This prevents accidental lockouts. Who it affects: users who are not Super Operators. Action needed: ask a Super Operator to block an email domain for you. Technical details: web app 1.67.0.


---

# 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/january-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.
