Shared Cloud and Platform support
Open Ankra Support for an AI chat or choose Contact Ankra to send a message directly to the team. Cloud and Platform both use this support center. Support reuses its existing session. If it needs a new session, it automatically continues through the product you last used for Support; a direct first visit uses Cloud. If that product needs you to sign in, complete its normal sign-in and return to your chat. You can choose Continue with Platform or Continue with Cloud if the automatic connection does not finish. Signing out of Support keeps you signed out in that browser tab until you choose to continue again. Documentation remains available without signing in. An unsent AI question is restored for review after reconnecting within ten minutes, in the same browser tab. It is not sent automatically. To bring in the team, choose Contact Ankra, review your message and any AI conversation you choose to share, and send it. Follow replies under Conversations. A successful submission shows a neutral confirmation with a green accent; red notices indicate an error. Staff can open Support administration, which starts the staff sign-in handoff. Verified@ankra.io and @ankra.ai accounts can also enter through a Cloud or Platform issuer configured for Ankra staff. Open a case in the Support queue to reply publicly or choose a private staff note. Support access does not grant permission to act on customer infrastructure; Cloud and Platform access grants still apply.
Staff AI assistance
Open a ticket in the Support queue to use the investigation assistant beside the conversation.- Rewrite a reply - write your draft and choose AI rewrite. Review the preview, then choose Use rewrite or Keep original. You can undo an applied rewrite before editing it further. Rewriting uses only your draft, and never sends a reply automatically.
- Investigate a case - ask a question or choose Summarize case or Plan investigation. The assistant reads the selected ticket, recent messages and official Cloud and Platform docs. It identifies unavailable documentation and omitted older messages.
- Include private staff notes - under Context & connections, select this only when you want internal staff discussion included. Changing the setting clears the current AI chat.
- Keep a finding - choose Add to private note, review the draft, then send it when ready. The assistant does not post directly to the customer.
Where to open a ticket
- Portal - open the Account menu at the bottom of the sidebar and choose Support to enter the shared support center, then Contact Ankra to start a request.
- Command palette - press
⌘ K/Ctrl Kand choose Support to enter the shared support center. See Command Palette. - CLI -
ankra support create, below. - AI Assistant - ask it to raise a ticket, below.
Linked Platform ticket review
Requests linked to existing Platform operating tickets keep this native review flow, on the New support case page. New requests go through Contact Ankra in the shared Support center.1
Describe the problem
Fill in Subject and What do you need help with?, and pick a Category and a Severity. The cluster of the linked ticket is attached automatically.
2
AI review
Press Check the case with Ankra. Before the case is sent, Ankra runs an AI review that enriches it with a summary, checks quality, may ask clarifying questions, and surfaces possible related cases. The result appears under Review before sending.
3
Submit
Answer any clarifying questions. If Ankra found possible related cases, choose one under Related case, or keep A separate issue. Tick I reviewed this case and want to send it to Ankra support. and press Send support case. The check expires: if it has, check the case again.
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. These are the severities the SLA sets response times for; medium is the SLA’s Normal.
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.
While working a ticket, Ankra support may open a time-limited, read-only support session in your organisation to see what you see, or an elevated one with your consent. See Ankra Support Access.
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.From Ankra AI and the MCP server
The assistant and the MCP server work the same tickets. Ask Ankra AI to “raise a support ticket about the ingress 502s” and it proposes a Raise support ticket action naming the subject, category, severity and cluster; confirm, and the ticket is filed with sourceagent, tied to the cluster you were chatting about. It can also list your tickets, read one by its number, reply on your behalf, and close one you consider resolved. The tools are list_support_tickets, get_support_ticket, create_support_ticket, comment_support_ticket and close_support_ticket - see the MCP Tool Reference. Attachments stay in the portal and the CLI.
From the CLI
create runs the same AI review as the portal and asks you to confirm when it flags the ticket or finds a likely duplicate; --force skips that prompt. See ankra support for every flag.