# 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**.

<figure><img src="/files/DvM1Uo4VxJgxDjdrHSAE" alt=""><figcaption></figcaption></figure>

### Guide planners, and encourage longer stays

Elevate the reasons for choosing your property, and provide the opportunity to convert and increase stay length.

<div><figure><img src="/files/dajScEa1hUO34AFXylaO" alt=""><figcaption></figcaption></figure> <figure><img src="/files/93tJZnuSG9VylrTd4iZQ" alt=""><figcaption></figcaption></figure></div>

{% embed url="<https://stream.flip.to/new-and-improved-planner-flow-on-the-way>" %}

## 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="<https://stream.flip.to/what-is-discovery-flip-to-x-og-case-study-68fff8>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flip.to/docs/platform/discovery/experiences.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.