> 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/collaboratives.md). # Collaboratives Brands and their local communities can join together on the Flip.to platform to drive impact, giving everyone an edge that leads to becoming more profitable. By working together, everyone taps a larger, more highly targeted, right-fit demographic and wins over travelers with the revenue impact measured in real-time. ## Enlist ambassadors Turn visitors into storytellers, growing a massive army of marketers for the destination and your brand with [Advocacy](/docs/platform/advocacy.md). ## Win over a new audience Win over the most profitable business with an entirely reimagined booking path, and introduce local experiences with [Discovery](/docs/platform/discovery.md). ## Unlock an industry first Bring a regional understanding of the marketing ecosystem in real-time to every member of the collaborative—tracked to revenue. Directly help lodging partners and the local community win over the most profitable business and improve their own marketing with demographic & behavioral [Insights](/docs/platform/collaboratives/collaborative-insights.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 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/collaboratives.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.