> For the complete documentation index, see [llms.txt](https://learn.fueled.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.fueled.io/more-info/get-support.md). # Get Support Connect with Us over Email For customer support issues, please contact . To learn more about Fueled and get more information, please contact . ## Join Our Slack Community To discuss all things CDP, join our Slack community using the form below. Connect with agencies, SaaS companies, and merchants who share your interest in leveraging customer data for more personalized and targeted digital experiences. **Discussion topics** in our community include: * How agencies can support DTC brands through customer data strategies; * Building data tracking plans; * Evaluating CDP and “modern data stack” technologies; * And, of course, answering any and all questions eCommerce merchants might have about CDPs. **Channel expectations:** * Differing opinions are encouraged. * Respectful discourse is required. * Please keep product and services pitches brief and infrequent. ### Slack Channel Sign-up Form Simply fill out the form below, and you’ll be added to our Slack channel. If you prefer to connect with a human about this, email: . {% @formspree/formspree %} --- # 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://learn.fueled.io/more-info/get-support.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.