> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-licensing-guide/support-services/adding-watchers-to-a-support-ticket.md).

# Adding watchers to a support ticket

By default, all administrators of a Parallels business account can view and manage support tickets, but only you (the ticket owner) will receive email notifications about it. You can add other account administrators as watchers of a support ticket, so they can too receive email notifications.

To add ticket watchers:

1. Click **Support** on the page header (the red area).
2. Click the **Parallels Remote Application Server** card.
3. Click **My Tickets** in the upper right.
4. Select a ticket and click on the **Subject** column value (usually a combination of your company name and the issue description that you used when you created a ticket).
5. In the dialog that opens, click the **Ticket Watchers** tab.
6. Select an account administrator in the drop-down menu and then click **Add**.
7. Click **Done**.

To remove a watcher from a ticket, repeat the steps described above, but this time click the (X) icon next to the watcher and then click **Done**.


---

# 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.parallels.com/landing/ras-licensing-guide/support-services/adding-watchers-to-a-support-ticket.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.