> For the complete documentation index, see [llms.txt](https://docs.cryptoix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptoix.io/contact-and-support.md). # Contact and Support We're here to help you make the most of Cryptoix! Whether you have a question, need assistance, or have a brilliant idea for a new feature, we want to hear from you. ## Support Channels You can reach our support team through the following channels: * **Email:** For general inquiries, technical issues, or account-related questions, please email us at . * **Help Center:** You are currently viewing our Help Center. Browse our articles for answers to common questions and step-by-step guides. ## Business Hours Our support team is available to assist you during the following hours: * **Monday to Friday:** 9:00 AM - 5:00 PM UTC * **Weekends and Public Holidays:** Limited support is available. For urgent issues outside of business hours, please use our email support, and we will respond as soon as possible. ## Response Times We strive to respond to all inquiries promptly. Here's what you can typically expect: * **Email Support:** We aim to respond to all emails within **8 business hours**. * **Urgent Issues:** If your issue is critical and impacting your business operations, please clearly mark your email subject line as "URGENT" and provide as much detail as possible. ## Submitting a Support Ticket The easiest way to get detailed help is by submitting a support ticket via email. Please include the following information in your request to help us resolve your issue faster: 1. **Your Account Information:** Your registered email address or business name. 2. **Subject Line:** A clear and concise summary of your issue (e.g., "Payment Gateway Error," "Unable to Create Invoice"). 3. **Detailed Description:** Explain the problem you are experiencing. What were you trying to do? What happened? What did you expect to happen? 4. **Screenshots or Videos:** If possible, include screenshots or a short video demonstrating the issue. This is incredibly helpful! 5. **Affected Area:** Specify which part of Cryptoix you are having trouble with (e.g., Dashboard, API, specific plugin). 6. **Error Messages:** If you see any error messages, please provide the exact text. Once submitted, you will receive an automated confirmation email with a ticket number. Our support team will then investigate and get back to you. ## Feature Requests We are constantly working to improve Cryptoix and add valuable new features. If you have an idea for a new feature or an improvement to an existing one, we'd love to hear it! You can submit your feature requests by emailing your suggestions to with the subject line "Feature Request". Please describe your idea clearly, explaining the problem it solves or the benefit it would provide to your business. While we can't promise to implement every suggestion, all feedback is reviewed and helps shape the future of Cryptoix. --- # 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://docs.cryptoix.io/contact-and-support.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.