> For the complete documentation index, see [llms.txt](https://help.meetmadison.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.meetmadison.ai/settings/brand.md). # Brand Your **brand** settings make sure everything Madison creates looks and sounds like it comes from your business. Manage them under **Settings → Brand**. ## Logo Upload your business logo. It appears on your review request pages, emails, and more. If you run more than one location, you can also set a **logo per location**, which takes the place of the business logo on that location's review pages and emails. ## Your brand voice On every plan, Madison **learns your voice automatically**. As you edit and approve replies and posts, your content gets more "you" over time, with nothing to set up. This is the recommended way to keep everything on-brand, and for most businesses it's all you need. ### Style guide (advanced) The **Style guide** is an **Ultimate** feature for those who want extra, hands-on control over how Madison writes. It's a plain-text description of how your business sounds, your tone, the words you do and don't use, and anything Madison should keep in mind, and Madison follows it whenever it writes for you. Most businesses don't need this, automatic learning already keeps you on-brand. It's best suited to people who know exactly how they want to sound and want to set it explicitly. There's **one Style guide per organisation**, and saving a new one replaces the previous version. {% hint style="info" %} The Style guide is available on **Ultimate**. See [Settings → Plan & Billing](/settings/billing.md) to upgrade, or contact us at . {% endhint %} --- # 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://help.meetmadison.ai/settings/brand.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.