> For the complete documentation index, see [llms.txt](https://docs.flip.to/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flip.to/changelog/february-2025/new-support-for-sold-out-inventory-and-group-bookings.md).

# New support for sold out inventory and group bookings

26 February 2025

## <mark style="color:purple;">Smoothly handle when inventory is sold out</mark>

Every hotel has it's fair share of busy periods. When planners go from the website to the booking engine to find that dates are sold out, we've made adjustments for the best experience possible, for traveler and business alike.

Discovery now logs these new signals for sold out inventory or denials.

From there—out-of-the-box—their one-to-one conversation is adjusted, and planners can kick off a new set of plans.

## <mark style="color:purple;">Better understand the impact of group bookings on your website</mark>

Group bookings are a powerful audience for many customers. Since many group bookings are made on the website, understanding their impact to performance to this channel is a win.

In this update, Flip.to now captures group codes along with other signals from group bookings.


---

# 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.flip.to/changelog/february-2025/new-support-for-sold-out-inventory-and-group-bookings.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.