> 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.md).

# Support

Plenit's support is managed from the dashboard, in Home > Support. 

You centralize all communication with our team: each incident, request, or query is recorded as a ticket, with its history and tracking, without relying on email. 

You have two channels on the same system: the dashboard and WhatsApp.

{% hint style="info" %}
Is this your first time here? Go to Getting started below and open your first ticket in minutes.
{% endhint %}

### Explore Support

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Tickets</strong></td><td>The main channel: create, track, escalate, and close your cases from the dashboard.</td><td><a href="/pages/a1a11dc697e01cac2c28b17f8753b8b0a5fff6a1">/pages/a1a11dc697e01cac2c28b17f8753b8b0a5fff6a1</a></td></tr><tr><td><strong>WhatsApp</strong></td><td>Open and comment on tickets from your phone with the Partner Success team.</td><td><a href="/pages/a638dd43cf0ea5d56ca4aa18602ab54dd195b61d">/pages/a638dd43cf0ea5d56ca4aa18602ab54dd195b61d</a></td></tr><tr><td><strong>Contact</strong></td><td>Support channels, Partner Success, and after-hours support.</td><td><a href="/pages/113940d401afe33430a22f569d775b9a109e36b6">/pages/113940d401afe33430a22f569d775b9a109e36b6</a></td></tr></tbody></table>

### Getting started

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Create your first ticket</strong></td><td>Open an incident or a request from the dashboard in four steps.</td><td><a href="/pages/a1a11dc697e01cac2c28b17f8753b8b0a5fff6a1">/pages/a1a11dc697e01cac2c28b17f8753b8b0a5fff6a1</a></td></tr><tr><td><strong>Set up support via WhatsApp</strong></td><td>Authorize your team's numbers and operate from chat.</td><td><a href="/pages/a638dd43cf0ea5d56ca4aa18602ab54dd195b61d">/pages/a638dd43cf0ea5d56ca4aa18602ab54dd195b61d</a></td></tr><tr><td><strong>Check the channels</strong></td><td>Find out which channel to use in each case.</td><td><a href="/pages/eb9b6872a141e0924e0a3efcf666acde243253f1">/pages/eb9b6872a141e0924e0a3efcf666acde243253f1</a></td></tr></tbody></table>

{% hint style="success" %}
Can't find what you're looking for? Open a ticket and our team will help you. Outside business hours, Eliot, our AI agent, will assist you.
{% 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 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.plenit.com/docs-en/support.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.