Skip to main content
Support lets you raise tickets without leaving Ankra. Open a ticket from the portal, attach logs or screenshots, and follow the conversation through to resolution - all tied to the cluster it concerns. An AI review step triages each ticket before it’s filed, so the right severity, category, and context are attached from the start and duplicates are caught early.

Raising a ticket

1

Describe the problem

Give the ticket a subject and description, pick a category, and optionally link the cluster it relates to. Context about the selected cluster is attached automatically.
2

AI review

Before the ticket is filed, Ankra runs an AI review that enriches it - suggesting a summary, severity, and category - checks quality, may ask clarifying questions, and surfaces likely duplicates of existing tickets.
3

Submit

Accept the review (or answer its clarifying questions) and submit. If a strong duplicate is found, you can link to the existing ticket instead of opening a new one.
4

Track and reply

Follow status changes, read replies from the Ankra team, and add your own comments and attachments as the conversation continues.

Categories

Severity (low, medium, high, critical) is suggested by the AI review and can be adjusted.

Ticket lifecycle

A ticket moves through these statuses: Each ticket records its source (portal, api, cli, or agent), an AI summary, the AI review status, comments (from you, the Ankra team, AI, or the system), and any attachments.

Attachments

Attach logs, manifests, or screenshots to give the team what they need. Attachments are validated by type and size, and there is a per-ticket limit. Download an attachment again from the ticket at any time.

API

Support tickets are available programmatically. Browser sessions use the /org/support/tickets routes; token-authenticated clients (CLI, scripts) use the /api/v1/org/support/tickets equivalents. See the API Reference for full request and response schemas.