> 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/docs/platform/discovery/experiences.md).
# Experiences
With **Discovery + Experiences**, inspire travelers planning a stay by introducing the experiences and local community where they'll spend their time.
Plus, start learning new signals of traveler’s interests, blend into the site and communication, and save their plans for when they’re ready to book.
## Experiences in the planner journey
### Start with a better user experience that's proven to outperform
This reimagined approach ultimately helps properties to **sell more time**.
### Guide planners, and encourage longer stays
Elevate the reasons for choosing your property, and provide the opportunity to convert and increase stay length.
{% embed url="" %}
## Impact is proven
Don't just take our word for it. The impact of inspiring planners right from the planner journey has a major impact on your bottom line.
{% embed url="" %}
---
# 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/docs/platform/discovery/experiences.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.
