Panel tickets
Account status, plan changes, refund requests, subscription import and connection issues all go here. A ticket automatically includes your account and current plan, so there is no need to paste purchase records.
Open a ticketPanel tickets are the main entry point and cover account, order, subscription import and connection issues; billing and refunds go by email, and short questions go to Telegram. Each of the three channels has its own use case — pick the one that matches your issue and submit there.
Tickets carry your account context, so they resolve fastest; email is best when you need a written record or reconciliation; Telegram suits short questions only.
Account status, plan changes, refund requests, subscription import and connection issues all go here. A ticket automatically includes your account and current plan, so there is no need to paste purchase records.
Open a ticketBest for billing checks, payment receipts and refund confirmations — anything that needs a written record. The address is included with your order confirmation and is also shown on the support page in your panel.
Replies in 1–2 business days
Suited to short questions and status checks, such as whether a particular route is currently working. The channel address is posted inside the panel; instant replies are not guaranteed and messages are handled in the order received.
Handled in the order received
The table below shows expected first-reply windows, not minute-level promises. Issues that need several rounds — refund verification, route troubleshooting — will take longer overall.
| Channel | Use case | Expected first reply |
|---|---|---|
| Panel tickets | Account status, plan changes, refund requests, subscription import, connection issues | Submitted during business hours: usually within 1 business day |
| Billing checks, payment receipts, refund confirmations | 1–2 business days | |
| Telegram | Short questions, service status checks | Not instant; handled in the order received |
Response times are counted in business days and exclude weekends and public holidays. Submitting the same issue on several channels will not speed things up — scattered records actually make it harder to verify.
Most tickets need several rounds because the information cannot be verified. Include these four points and the issue is usually located in one round.
Sign in to the panel; the overview page shows your current plan tier and this month's remaining data. Adding both to the ticket rules out "did I run out of data" straight away.
Say whether it is Windows, macOS, iOS, Android or Linux, plus the client version number. Clients come from the download page in the panel; the version number is on the client's About or Settings page.
Note which route, when it started, and whether it reproduces every time or only occasionally. If only one route is affected and the others are fine, that one sentence saves most of the troubleshooting steps.
Which routes you switched to, whether you restarted the client, whether you changed networks. Suggesting steps you have already done is the most common cause of ticket ping-pong.
Clear boundaries save time on both sides. The two columns below list what support can help with and what falls outside its scope.
Six questions and answers on channels, refunds and subscriptions; the figures in the answers match the pricing and terms pages.