> 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/changelog/july-2024/supporting-special-codes.md). # Supporting Special Codes 18 June 2024 ## Discovery handles promotion, group, agent or other special codes with ease Like everything from Flip.to, [this new feature Is easily configured and it works out-of-the-box](https://docs.flip.to/platform/discovery/special-codes). **Planners enter their code into Discovery, or it's passed in automatically.** Plus, planners can view and edit their promotion or group code at any point. If planners don't complete their booking, their code is saved to their plan when they return.

Head over to your Flip.to account, or [say hello to your Customer Success Manager to get set up.](https://docs.flip.to/support/customer-success) 👋 --- # 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/changelog/july-2024/supporting-special-codes.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.