> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/ai-tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/ai-tools/contact-us.md). # Contact Us Assistance is a click or call away! ## Getting Help Please submit a ticket of your issue or feature request to with your subject starting with "CCV AI Services:" so our fantastic Help Desk staff can direct this to the correct group. The Help Desk can also be contacted during normal business hours: * Via Chat on the bottom right of the [OIT Knowledgebase](https://ithelp.brown.edu/). * By phone at [401-863-4357](tel:4018634357). * In person at [Page Robinson Hall - 69 Brown St., Room 510](https://www.google.com/maps/place/69+Brown+St,+Providence,+RI+02906/@41.8275262,-71.4038802,18z/data=!3m1!4b1!4m5!3m4!1s0x89e4453c8eaabc71:0xcb2af2f03465cf57!8m2!3d41.8275262!4d-71.4027859). {% hint style="warning" %} Please utilize e-mail for bugs (and [include screenshots](https://www.take-a-screenshot.org/)) so we can handle system issues more quickly! {% endhint %} ## Providing Feedback We always appreciate your feedback! Please use the [CCV AI Services Feeback Form](https://forms.gle/w9bn1zFXrYatc1V57) for any comments/feedback/suggestions related to Transcribe, LibreChat, or Ask Oscar. --- # 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.ccv.brown.edu/ai-tools/contact-us.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.