> 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/advocacy/curation/getting-the-most-out-of-curation.md).
# Getting the most out of Curation
Congratulations on curating your first story! You’ve taken the first step to introduce your hotel to a right-fit audience by turning this storyteller into an advocate.
[As we shared, this is done in clicks.](https://docs.flip.to/platform/advocacy/curation) And from here, the platform puts these stories to work. By rating your stories, curation impacts how that happens. Here’s how you can ensure your top picks are bubbled up.
***
## Advancing storytellers
Most customers advance the majority of stories they receive. That’s because more storytellers means a bigger audience.
#### What if the image isn't marketing-quality
Don’t worry, we’ll take care of that in the ratings, below.
#### When to say "No"
On a rare occasion, you’ll come across a story not to advance. Consider this a judgment call for anything that’s inappropriate or offensive.
And if you need additional guidance, say hello to your friendly, neighborhood [Customer Success Manager.](/docs/support/customer-success.md) 👋
***
## How ratings are used
The higher the rating, the more we’ll put a story to work. For examples on where stories might appear:
* Three-star ratings are used across your experiences with the most frequency—consider these your all-stars.
* Two-star ratings can appear on the story river or home page, and [places unique to a campaign](https://rushcreeklodge.stories.travel/invite/guest-storytellers).
* A one-star rating can appear in a [Story Explorer](https://rushcreeklodge.stories.travel/photo-explorer/gallery) for your property.
* Stories that you give a thumbs down would only appear in specific campaign experiences, and to a storyteller's own audience of friends.
***
## Nice-to-knows
### What to expect
{% hint style="success" %}
**How will I know when I have stories to curate?**
* Your platform automatically notifies you with a daily email every time new stories are submitted. Let your [Customer Success Manager](/docs/support/customer-success.md) know anyone you’d like to be included.
**How often should I curate stories?**
* Curate stories within a day or two. The sooner you can curate, the sooner the storyteller can start becoming an advocate for your brand.
**How often should I curate stories?**
* Curate stories within a day or two. The sooner you can curate, the sooner the storyteller can start becoming an advocate for your brand.
**How long does curation take?**
* Curation should be one of the exciting parts of your day, and takes **just ten to fifteen minutes a week** for top-performing customers.
{% endhint %}
### Dialing in even more
{% hint style="info" %}
**Once a story is curated, can I change my mind?**
* Ratings can be changed at any time.
* If you’ve advanced a storyteller and need to make a change, your dedicated Customer Success Manager can jump in.
**What about Quotes and Captions?**
* You can also keep in mind that Quotes typically take precedence over Captions, unless the rating reflects otherwise.
{% endhint %}
***
## I need more help!
If you ever need extra guidance, we’re just a few clicks away. [Say hello today.](/docs/support/customer-success.md)
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.flip.to/docs/platform/advocacy/curation/getting-the-most-out-of-curation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.