> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/help/cases/case-comments/adding-comments.md).

# Adding Comments

Open the case that you need to add a comment for and click on the **Comments** tab.

Click on the **New Comment** button.

In the **Comment** card add the following information:

* **Text** - In the Text field, add the comment related to the case.
* **Assigned to** - ***To be updated***
* **Category** - Comments can be assigned a Category (e.g. Decision, Resolution, Approval). These categories are customizable per organization and need to be setup by **Shift iQ Support**, please email [**support@shiftiq.com**](mailto:support@shiftiq.com) to add categories if needed.
  * A **Subcategory** can be added for a Category to provide further information regarding the comment (e.g. If Category = Decision a Subcategory can be added to provide the Decision made):
    * Category = Decision
    * Subcategory = Membership Cancelled
* **Flag** - Color flogs can be assigned to a comment. Within your organization you can assign a value for each flag color (e.g. Red = Important, Yellow = Requires Attention, Green = Approved)
* **Tag** - ***To be updated***

Click the **Save** button.


---

# 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.shiftiq.com/help/cases/case-comments/adding-comments.md?ask=<question>&goal=<endgoal>
```

`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.