> 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/october-2026/demand-capture-finds-the-nights-that-matter-most.md).
# Demand Capture finds the nights that matter most
27 October 2026
## Demand is nuanced—now your next move is, too
Demand stacks up differently for every hotel. A Tuesday in March can be quiet at one property and full at the next. Not every Saturday is created equal on the demand scale.
And while a room night report tells you how many room nights a channel brought in, it doesn’t separate the hard-won nights from those in high demand.
**That’s why we rebuilt Demand Capture**—a newly designed insight to do just that.
{% embed url="" %}
### A clearer read on the demand behind every channel
Every channel gets a plain-language headline on where its bookings landed. Below it are the nights, the timing and how it ranks against your other channels.
#### Which nights is your channel booking?
Is this channel helping on the nights that need it most, or landing on nights that were already filling?
See the channel side by side with your other channels on your low- and high-demand nights. Switch to revenue for the share and ADR behind each one, so the value shows up in dollars.
#### When did your guests book?
Early bookings on your busiest nights give you time to adjust rates before they sell out.
See how far ahead each channel’s guests booked, and every night it brought in on your calendar (setting aside any without enough data yet).
#### How does your channel rank?
If a slow stretch is coming, it helps to know what fills it.
Every channel is ranked by how much of its business lands on quiet nights, or one click re-ranks the list by busy nights instead. Room nights sit alongside, so you can tell a big percentage from a big contribution.
### Start exploring 🧑🚀
Open any channel, campaign or email for a hotel in Spacetime and scroll to **Contribution value.** You’ll see which channels fill your quiet nights, and which book your busy ones early.
Want a hand reading your own nights? [Say hello to Customer Success](https://docs.flip.to/docs/support/customer-success)—we’d love to show you around. 🚀
\
\
\
---
# 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/october-2026/demand-capture-finds-the-nights-that-matter-most.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.
