> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/general/contacts.md). # Contact Us Contact Navixy Team ## Need Assistance? If you have any questions or need support, our team is here to help. Reach out to us through any of the following methods: * **Phone**: [Call Us](https://www.navixy.com/contact/) * **Email**: ## Stay Connected Keep up with the latest updates and connect with us on social media: * [**GitHub**](https://github.com/Navixy/navixy-api): Follow our repository for the latest code and updates. * [**LinkedIn**](https://linkedin.com/company/navixy/): Connect with us professionally and stay informed about our business updates. * [**Twitter**](https://twitter.com/Navixy): Follow us for real-time updates and announcements. * [**Facebook**](https://facebook.com/NavixyGPS): Join our community and engage with us. * [**Instagram**](https://instagram.com/navixygps): See our latest posts and stories. * [**YouTube**](https://youtube.com/channel/UCL0u39pv4NlECAmFOZCZ-nw): Watch our videos for tutorials, updates, and more. For further information and detailed inquiries, visit our [Contact Page](https://www.navixy.com/contact/). --- # 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://navixy.com/docs/navixy-api/general/contacts.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.