# Getting Help

## Filing a Support Ticket

Filing a good support ticket makes it much easier for CCV staff to deal with your request

When you email `support@ccv.brown.edu` aim to include the following:

* State the problem/request in the subject of the email
* Describe which software and with version you are using
* Error message (if there was one)
* The job number
* How you were running, e.g. batch, interactively, vnc
* Give as as small an example as possible that reproduces the problem

## Q\&A Forum

Ask questions and search for previous problems at our [OSCAR Question and Answer Forum](https://github.com/brown-ccv/oscar-documentation/discussions/categories/q-a).

## Slack

Join our CCV-Share Slack workspace to discuss your questions with CCV Staff in the #oscar channel. [Sign-up here](https://ccv-share.slack.com/signup#/)

## Office Hours

CCV holds weekly office hours. These are drop in sessions where we'll have one or more CCV staff members available to answer questions and help with any problems you have. Please visit [this page](https://events.brown.edu/ccv/all) for upcoming office hours and events.

## Arrange a Meeting

You can arrange to meet with a CCV staff member in person to go over difficult problems, or to discuss how best to use Oscar. Email `support@ccv.brown.edu` to arrange a consultation.


---

# Agent Instructions: 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:

```
GET https://docs.ccv.brown.edu/oscar/getting-help.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
