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

# Tickets

Create, track, and close your incidents and requests from the dashboard, without relying on email.

With the **Ticketing** you communicate with our support team directly from the dashboard, without relying on email or external tools.

From **Support > My Tickets** you create, view, update, and close your tickets quickly, centrally, and in your language.

> #### 📘 **What will you get?**
>
> Centralize all support communication in the dashboard: every incident, request, or inquiry is recorded, organized, and accessible to you and your team.

### What can you do

* Create and manage tickets directly from the dashboard.
* Receive notifications in your language (Spanish, English, Portuguese, or French).
* Associate each ticket with your organizations or services.
* Track the status in real time, from creation to resolution.

### Where to find your tickets

Access from **Home > Support > My Tickets**. There you can see all your tickets, with a total counter, a button **New ticket** and a button **Filters** to narrow down the list.

![My Tickets section in the dashboard](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-cdf5dda61668291a87a5cf247b8a8f2ddf889cb2%2F1.png?alt=media)

The list shows these columns:

| Column        | What it shows                                                  |
| ------------- | -------------------------------------------------------------- |
| ID            | The ticket identifier.                                         |
| Title         | The ticket subject.                                            |
| Status        | The current status (with the Escalated label when applicable). |
| Created       | The creation date and time.                                    |
| Updated       | The date and time of the last update.                          |
| Organization  | The associated organization.                                   |
| Owner         | The user who opened the ticket.                                |
| Notifications | Yes / No switch to receive notifications for that ticket.      |

### How to create a ticket

Click **New ticket** and fill in the fields:

* **Type** — Incident or Request.
* **Category** — General, Billing, or Organization/Service.
* **Organization** — the affected organization, if applicable.
* **Service** — one or more related subscriptions (optional).
* **Title and description** — clearly explain the problem or inquiry.
* **Attachments** — add screenshots, logs, or documents (optional).
* **Interested users** — other users who should receive updates (optional).

Click **Submit** to create the ticket.

![Ticket creation form](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-e5e1a727aab2e1ead05ba6cac378d12bf7c37bfe%2F2.png?alt=media)

#### 📘 **Tip**

If the incident affects more than one service, include them all in the same ticket to speed up handling.

### The statuses of a ticket

Once created, the ticket is recorded in your dashboard. From there you can see its status, update it, add information, and follow all communication with support.

| Status      | What it means                                                                   |
| ----------- | ------------------------------------------------------------------------------- |
| New         | The ticket has been created and is pending assignment.                          |
| In progress | The support team is working on it.                                              |
| Reopened    | You have reopened the ticket to review or provide new information.              |
| Resolved    | The case is resolved. If it is not reopened, it closes automatically in 7 days. |
| Closed      | The ticket is considered finished.                                              |

![Ticket statuses](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-b7a005abaeb6e408be25bd75f60b0acf306265d5%2F3.png?alt=media)

### How to manage your tickets

From **My Tickets** you can do everything without leaving the dashboard:

* **Add or edit comments** to keep the ticket up to date.
* **Upload new files or screenshots.**
* **Add or remove interested parties** to include other members of your organization.
* **Escalate the ticket** if you need priority attention.
* **Request a call** to resolve the case more directly.
* **Turn notifications on or off** for a specific ticket.
* **Close the ticket** when the incident is resolved.
* **Reopen it** if the problem persists, keeping the full history.

### Notifications

To keep you informed without creating noise, email notifications are sent only at key moments:

* When **creating** a ticket.
* When it is **escalated**.
* When it changes to **Resolved**.
* When it is **closed**.

Emails are sent in the language configured in your user profile. In addition, you can turn notifications for a specific ticket on or off from its details.

### Support rating

When a ticket is closed, you can **rate the support received** with a rating of 1 to 5 stars, from very dissatisfied to very satisfied. Your rating helps us improve the service.

### Usage tips

* Use clear and specific titles to identify each ticket.
* Add screenshots or logs to speed up resolution.
* If a case becomes complicated, use **Escalate** to prioritize it.
* Before opening a new ticket, review the ones that are already closed.
* Keep notifications active only on the tickets that matter to you.

### Frequently asked questions

<details>

<summary><strong>Can I choose the ticket priority?</strong></summary>

No. Priority is defined by the support team according to the type and category.

</details>

<details>

<summary><strong>Can I close a ticket manually?</strong></summary>

Yes, as long as support has confirmed that the incident is resolved.

</details>

<details>

<summary><strong>Can I reopen a closed ticket?</strong></summary>

Yes. The ticket retains all information, comments, and attachments.

</details>

<details>

<summary><strong>Why am I not receiving emails?</strong></summary>

Check whether you have disabled ticket notifications or whether the email address in your profile is correct.

</details>

### Next steps

* Enable the WhatsApp channel in [How to set up support through WhatsApp.](https://docs.plenit.com/docs-en/support/whatsapp.md)
* Manage operations contacts in [How to manage an organization's contacts.](https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-manage-organization-contacts.md)


---

# 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.plenit.com/docs-en/support/tickets.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.
