> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/concepts/helpdesk.md).

# HelpDesk

The AI HelpDesk is where your AI-assisted DevOps work lives. It is the backend service that tracks and manages all of your tickets — whether standalone tasks or tickets that belong to a larger project — and acts as the central system of intelligence.

Tickets are the core unit of work in the HelpDesk. Each ticket represents a discrete task or request that the AI Agent works on alongside you. Through an intuitive interface, you can open tickets, interact with the Agent, visualize operations through a shared browser, and maintain oversight of AI-executed commands in production environments.

Because everything is ticket-based, the HelpDesk also serves as a collaboration layer — team members can work in parallel, hand off context between sessions, and maintain a complete audit trail. The result is a platform that enhances productivity, reduces operational overhead, and maintains the security and compliance standards intrinsic to DuploCloud.

Open the HelpDesk from the **HelpDesk** item in the left navigation sidebar. It expands to two options: **Add Ticket** and **History**.

![HelpDesk menu with Add Ticket and History](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-7dad0c296ecce54c5d68fcbb35c394d1e760e36c%2Fhelpdesk-v2-step-01-nav.png?alt=media)

***

## Add Ticket

Click **Add Ticket** to open a new ticket. The page asks *What should the agent work on?* Describe the task, optionally pick a model and scopes, review the **Agent loadout**, and submit.

![Add Ticket page](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-55edbf2f1d7551db96457495121b299797fa9681%2Fhelpdesk-v2-step-02-add-ticket.png?alt=media)

For a step-by-step walkthrough of every control on this page and of the ticket page that opens afterwards, see [Create a Ticket](https://docs.duplocloud.com/docs/concepts/tickets.md).

The **Recent tickets** panel on the right lists the latest tickets in the workspace. Its **History** button opens the full ticket list.

![History button in the Recent tickets panel](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-bb395e3a7be8b2b9ac30381ad523fa38836f6859%2Fhelpdesk-v2-step-03-add-ticket-history-btn.png?alt=media)

***

## History

Click **History** in the sidebar to see the tickets in the current workspace. The list opens on the **Helpdesk** tab, filtered to **Open** tickets and sorted by most recently modified.

![History list](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-f55de010660ae06c9bc3cd67a638eb88267f61c5%2Fhelpdesk-v2-step-04-history-overview.png?alt=media)

The table has the following columns:

* **Title** — the task or question submitted to the agent
* **LLM** — the model handling the ticket
* **Scopes** — the credential scopes attached to the ticket, or *No scopes*
* **Cost** — total cost the agent has accumulated on this ticket
* **Priority** — `Low`, `Medium`, `High`, or `Critical`
* **Status** — `Open`, `In Progress`, or `Closed`
* **Created By** — the user (or *System*) that opened the ticket
* **Last Modified** — when the ticket was last updated

**Priority** and **Status** are editable in place: click the badge in a row to change it without opening the ticket.

The **Add** button above the table opens the [Add Ticket](#add-ticket) page.

### Helpdesk and Linked tabs

* **Helpdesk** shows tickets opened directly in the HelpDesk.
* **Linked** shows tickets that were started from somewhere else — a Project, a Dashboard, a Dashboard Template, an external integration, or another source. This tab adds an **Origin** filter and an **Origin** column so you can see where each ticket came from.

![Linked tab with the Origin filter](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-af5faae086c31093a721285adee47ecad192feba%2Fhelpdesk-v2-step-08-linked-tab.png?alt=media)

### Filtering and searching

Use the filters above the table to narrow the list:

* **Priority** — show only tickets of one priority.
* **Status** — **All**, **Open**, **In Progress**, or **Closed**. Each option shows how many tickets it holds.

The **Search** box matches ticket names, titles, models, scopes, creators, and cost.

![Priority and Status filters](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-5185b4d509a7e386468ee9aa5a6add4d3fce798b%2Fhelpdesk-v2-step-05-history-filters.png?alt=media)

### Row actions

The **⋮** menu at the start of each row offers:

* **Copy Ticket ID** and **Copy Ticket Name** — copy the identifier to the clipboard, to reference the ticket elsewhere
* **Delete** — permanently remove the ticket, after a confirmation prompt

![Row actions menu](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-66fe92cbfff3b33a08813c4bd7ae1db5098a4dc2%2Fhelpdesk-v2-step-06-row-menu.png?alt=media)

### Resuming a ticket

Click a ticket title to open it and continue where you left off.

![Ticket title link](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-145e95ee7f285792870d9dcfbe7a17ff6144831b%2Fhelpdesk-v2-step-07-ticket-title.png?alt=media)

The full conversation with the agent is preserved. Type in the **Ask anything...** box to ask a follow-up question or direct the agent to its next task.

![Ticket conversation with the Ask anything input](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-e489d046b5dbed1bbf687886141681396f360efd%2Fhelpdesk-v2-step-09-ticket-bottom.png?alt=media)

### Closing a ticket

Set a ticket's **Status** to **Closed** to close it. A dialog asks whether the ticket was resolved. You can rate the experience and leave feedback before choosing **Yes, Resolved** or **No, Unresolved**.

![Close Ticket dialog](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-1ad0f410f1be7a42079e22ed993b37713933c14f%2Fhelpdesk-v2-step-11-close-dialog.png?alt=media)

The answer is recorded as the ticket's **disposition** and shown next to its status. When the **Closed** status filter is selected, a **Disposition** filter appears.

![Closed tickets with the Disposition filter](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-eebda2bfcb1d9fd46c07845fd6e39d6e684ff51a%2Fhelpdesk-v2-step-12-closed-disposition.png?alt=media)

Use it to show only **Resolved** or only **Unresolved** tickets.

![Disposition filter options](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-b900fcec9067b2f0259b0eaaeb1526acb2cd0eaf%2Fhelpdesk-v2-step-13-disposition-options.png?alt=media)

### Switching workspaces

Tickets belong to a workspace. To see another workspace's tickets, open the **Workspace** selector in the page header and pick a workspace, or type to search the list. The History table reloads with that workspace's tickets.

![Workspace selector](https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fgit-blob-4012fc9f0ee2d3fb0081366ac7f8b6239c21f700%2Fhelpdesk-v2-step-10-workspace-selector.png?alt=media)


---

# 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.duplocloud.com/docs/concepts/helpdesk.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.
