Get Support
Every support request goes through one channel: the in-app support ticket. A ticket reaches the Plexicus team together with your organization and your user, so we can answer by email without asking who you are.
Open a ticket
- Sign in to Plexicus.
- Select Support in the sidebar, or open the profile menu and select Support.
- Fill in the Subject and the Message, and choose a Category and a Priority.
- Select Send ticket.
| Field | Values |
|---|---|
| Subject | Required, up to 200 characters |
| Message | Required, up to 5000 characters |
| Category | Question, Bug, Feature request, Billing, Security, Other |
| Priority | Low, Normal, High, Urgent |
Our team replies by email to the address of your Plexicus user.
State what you did, what you expected and what happened. Do not paste passwords, tokens or secrets: a ticket is read by humans and stored by our support tooling.
What a ticket contains
Besides the form fields, Plexicus attaches your organization, your user email and your first name. It does not attach findings, source code or scan results; paste only what you want us to see.
File a ticket from a script or the CLI
Tickets can also be created with a personal API token through POST /support/tickets. The caller needs a role that can create support tickets (Admin, Cyberoper and Developer can). Keep it to real requests: do not file tickets in a loop.
When you cannot sign in
If you are locked out of your account or of your organization, you cannot open an in-app ticket. Email info@plexicus.ai from the address of your Plexicus user and describe the problem. See also Passkeys and SSO for the self-service recovery flows.
Self-hosted deployments
A self-hosted instance sends its in-app tickets to the support mailbox configured by your own operators. For chart bugs, registry access or license keys, use the contact listed in Self-Hosted Overview.
Feature requests
Choose Feature request as the category, or vote on existing ideas on the public feature request board.