> 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/pd-ag/parallels-desktop-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 the **Support** button on the product card.
2. Click **My Tickets** in the top-right corner.
3. 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).
4. In the dialog that opens, click the **Ticket Watchers** tab.
5. Select an account administrator in the drop-down menu and then click **Add**.
6. 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pd-ag/parallels-desktop-licensing-guide/support-services/adding-watchers-to-a-support-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.