> 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/places.md).

# Places

Let guests share where their stories happened in the community

{% hint style="info" %}
**Places** is in beta. To switch this on for your property, [get in touch with your Customer Success Manager.](/docs/support/customer-success.md)
{% endhint %}

When inviting storytellers to share their favorite moment, you may want to know where their experience happened.

That includes if it was on-site—like at one of your property's restaurants, spas or anywhere else. Easily configure the platform to do just that.

## First, set up your places

{% stepper %}
{% step %}
**Head to Mission Control.**

On the details tab, scroll down to **Your places**.

<figure><img src="https://639029760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8PYvV9n7ZxZ5iS2rITSl%2Fuploads%2FFwTyomnI2bI66UmFiSd0%2Fplacesconfig1.png?alt=media&amp;token=83e876b6-e88d-4f0a-8ca1-e7fcb9cf30c3" alt=""><figcaption></figcaption></figure>

<figure><img src="https://639029760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8PYvV9n7ZxZ5iS2rITSl%2Fuploads%2FaibGElBE8Tb9uFqvIWUi%2Fplacesconfig2.png?alt=media&amp;token=a48e228c-6624-47f1-94d6-c01a5ff0a927" alt=""><figcaption></figcaption></figure>

Search for and add places that belong to the property. Save them to your account.

<figure><img src="https://639029760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8PYvV9n7ZxZ5iS2rITSl%2Fuploads%2Fe8fYtTyogsOtGdTPA6b1%2Fplacesconfig3.png?alt=media&amp;token=17412a00-91bf-4b81-bf2e-c46ebd0e6ef9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Next, configure Advocacy**

Navigate to **Campaigns** and head to **Invitations**.

<figure><img src="https://639029760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8PYvV9n7ZxZ5iS2rITSl%2Fuploads%2FZSmRztB1ftekEEcUuPHb%2Fplacesconfig4.png?alt=media&amp;token=b6ba4b61-c959-419d-b9ed-385d4a2b2d8a" alt=""><figcaption></figcaption></figure>

Scroll down to places details to configure the campaign. **Save and you're all set.**

<figure><img src="https://639029760-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8PYvV9n7ZxZ5iS2rITSl%2Fuploads%2F20J3BgTWmfpyXthhQ7pP%2Fplacesconfig5.png?alt=media&amp;token=51083a4f-7106-47e2-bc2c-7193d0921260" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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/advocacy/places.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.
