> 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/contact.md). # Contact You have two channels to contact our support team. Both work on the same ticketing system, so communication is recorded and tracked, whichever one you use. ### Available channels | Channel | What it's for | Where | | -------------------------- | -------------------------------------------------------------------------------------- | ----------------------------------------- | | Dashboard (tickets) | Create, track, and close incidents and requests, with a full history. | Home > Support > My Tickets | | WhatsApp (Partner Success) | Open and comment on tickets from your mobile, sending screenshots or photos of errors. | Partner Success number: (+34) 931 550 213 | ### Which one to use * Use the **dashboard** as your main channel: it is where you have all the details, attachments, stakeholders, and the history of each case. * Use **WhatsApp** when you need speed or are away from the dashboard, for example to send evidence right away. The ticket is still recorded in the dashboard. > #### 📘 **Before using WhatsApp** > > The technician's number must be authorized by the subscription administrator. > > You have the steps in [How to configure support through WhatsApp.](/docs-en/support/whatsapp.md) ### Partner Success Team Our Partner Success team supports you with setup and inquiries during service onboarding. If you have a technical question about how to enable a channel or need guidance during the process, contact them through the usual channels. ### After-hours support: Eliot At night and on days when our team is unavailable, you are assisted by **Eliot**, our AI agent. Eliot responds on the Partner Success number and is trained to resolve your inquiries, open tickets, and follow up with you, so you also have support outside the team's hours. When the team returns, it takes over any case that requires it with all the context already recorded. ### Next steps * Create and manage your tickets in [How to create and manage your support tickets.](/docs-en/support/tickets.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 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/contact.md?ask=&goal= ``` `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.