Support
Open a ticket to get help with a server, billing or anything else.
If something isn’t working, or you have a question about your bill, open a ticket from Support in the dashboard. We reply on the ticket and email you when we do.
Opening a ticket#
Choose New ticket and tell us:
- Topic: technical, billing, sales, abuse, or something else
- Priority: how much it’s hurting. Save Urgent for a production server that’s down.
- Server: the one it’s about, if any. You can also choose Get help on a server’s page to start a ticket about it.
- Message: what happened, what you expected, and anything you’ve tried
Never put passwords or private keys in a ticket. We’ll never ask for them.
Replies and status#
A ticket shows whose turn it is:
| Status | Means |
|---|---|
| Waiting on support | We have it, and we’ll reply |
| Waiting on you | We replied, and need something from you |
| Closed | Sorted. Reply to open it again |
Close a ticket yourself when it’s sorted. If the problem comes back, reply to the closed ticket rather than opening a new one, so we have the history.
Tickets in a team#
Tickets belong to the workspace, not the person who opened them. Everyone in a team, whatever their role, can see, open and reply to its tickets. We email whoever opened the ticket when we reply.
From the API#
Tickets need support:read to list and read, and support:write to open, reply to and close them:
curl -X POST "$API/tickets" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"subject": "Server unreachable", "body": "Port 22 times out since 09:00 UTC.", "priority": "HIGH"}'See the API reference for the rest.