> For the complete documentation index, see [llms.txt](https://docs.faronics.com/faronicsdeploy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.faronics.com/faronicsdeploy/ticketing/ticket-actions/add-a-note-to-a-ticket.md).

# Add a Note to a Ticket

Notes are a useful way to log information and steps taken to resolve a Ticket. They can be added to Tickets in the following ways:

* Add notes from the main Tickets View.
* Add a note when closing a Ticket.

### Adding a Note via the Tickets View

![](https://3007061244-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MRkQfx_2cLnNNBX1muO%2F-MeWQm2mRlV85CSVL-uE%2F-MeWRxDBRF_NI0ofFcDS%2Fimage.png?alt=media\&token=0ca3e51c-ae18-4bba-a562-d22748e47be5)

1\. Select the **Tickets View** tab on the top menu bar.

2\. Click the Edit icon in the **Notes** column of the Ticket you wish to edit.

3\. Enter a note in the text box provided.

4\. Click **SAVE**.

{% hint style="success" %}
A note has successfully been added to the Ticket.
{% endhint %}

### Adding a Note when Closing a Ticket

![](https://3007061244-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MRkQfx_2cLnNNBX1muO%2F-MeWS7Sgu-0DDi7lxehi%2F-MeWUEGo1C1tmJwZ_bCf%2Fimage.png?alt=media\&token=b1ebed3d-0cc2-4d94-89d5-de97e08e7790)

1\. Select the **Tickets View** tab on the top menu bar.

2\. Select a **Ticket Report** from the list.

3\. Click the **TICKET ACTIONS** button, and select **Closed** under Change Status in the drop-down menu.

4\. (**optional**) Check the box to send a closure confirmation email to the user who submitted the Ticket.

4\. Enter a note in the text box provided.

5\. Click **DONE**.

{% hint style="success" %}
A note has successfully been added to the Ticket, and the Ticket has now been closed.
{% endhint %}


---

# 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.faronics.com/faronicsdeploy/ticketing/ticket-actions/add-a-note-to-a-ticket.md?ask=<question>&goal=<user_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.