On this page
Support tickets and live chat
Reach the Patrii Cloud team by opening a support ticket or starting a live chat. Tickets carry a category and a priority, move through a clear set of states, and keep the full conversation history; your support plan determines how quickly they are picked up.
A ticket is the durable record of a request or problem. You describe the issue, choose a category (and optional subcategory) so it is routed correctly, and set a priority. Every reply from you and from the team is added to the same thread, so nothing is lost and anyone on your side can follow along.
Live chat is the fast lane for short questions during business hours. It shares your account context so you don't have to repeat who you are, and it can hand off to a ticket when a question needs deeper investigation. Your support plan sets which channels are available and how responsive they are — this guide describes the workflow, not specific response-time commitments.
Key concepts
Ticket — A tracked request or problem with its own conversation thread, category and priority.
Category / subcategory — How a ticket is classified so it reaches the right team.
Priority — How urgent the ticket is; higher priorities are attended to sooner within your plan.
State — Where the ticket is in its lifecycle, from New to Closed.
Live chat — A real-time conversation for quick questions during business hours.
Support plan — The tier that sets your available channels and response expectations.
Before you start
- A signed-in Patrii Cloud account.
- The project the request relates to, so the team has the right context.
- For live chat, a browser session during business hours.
Step by step
- Open the Support area
Go to Support to see your ticket list, ticket statistics and your current support plan.
Screenshot — The Support dashboard with the ticket list and statsThe Support dashboard with the ticket list and stats - Create a ticket
- Choose New ticket and write a clear subject and description.
- Pick a category (and subcategory if offered) so it is routed to the right team.
- Set a priority that matches the real impact.
Screenshot — The New ticket form with subject, category and priority fieldsThe New ticket form with subject, category and priority fields - Add detail and attachments
Include the affected resource, the exact error, and what you already tried. Precise detail shortens the back and forth.
- Track and reply
Open the ticket to follow its state and post replies. New messages from the team appear in the same thread, and the ticket moves through states as work progresses.
Screenshot — A ticket detail view showing the message thread and the current stateA ticket detail view showing the message thread and the current state - Use live chat for quick questions
During business hours, start a live chat from the console for short questions; it already knows who you are and can open a ticket if the issue needs deeper follow-up.
Screenshot — The live chat widget open in the consoleThe live chat widget open in the console - Resolve and close
When the fix is confirmed, the ticket is marked Resolved and then Closed. You can reopen by replying if the issue returns.
Examples
curl -H "Authorization: Bearer $TOKEN" \ https://api.patrii.cloud/support/tickets
# multipart form fields; priority: "1" low, "0" normal, "2" high, "3" critical curl -X POST -H "Authorization: Bearer $TOKEN" \ -F subject="Cannot reach instance" \ -F description="SSH times out since 14:00" \ -F category_id=3 \ -F priority=2 \ -F files=@ssh-debug.log \ https://api.patrii.cloud/support/tickets
patrii support categories patrii support create --subject "Cannot reach instance" \ --description "SSH times out since 14:00" \ --category <category-id> --priority high patrii support list
Limits & specifications
Ticket states and priorities:
| Value | Meaning |
|---|---|
New | State: just submitted, not yet picked up. |
Open | State: acknowledged and being worked on. |
In progress | State: actively under investigation. |
Waiting on customer | State: the team is waiting for your reply or information. |
Resolved | State: a fix has been provided, pending your confirmation. |
Closed | State: completed; reply to reopen. |
Low / Normal | Priority: routine questions and non-blocking issues. |
High / Critical | Priority: significant or blocking impact, attended to sooner within your plan. |
Best practices
- Set a priority that reflects real impact so genuinely urgent issues stand out.
- Give one clear subject per ticket and keep one issue per thread.
- Include the project, resource ID, exact error and steps to reproduce.
- Reply promptly when a ticket is Waiting on customer so it keeps moving.
- Use live chat for quick questions and tickets for anything that needs a durable record or investigation.
FAQ
Ticket or live chat — which should I use?
What priority should I choose?
My ticket is Waiting on customer — what does that mean?
Can I reopen a closed ticket?
How do response times work?
Learn more
Everything you can do here in the console is also available through the Patrii Cloud API for automation and scripting.