Support channels · Tickets first
Account, subscription, payment, refund and route issues all have a dedicated submission point on this page. Include your username, order ID and the time the issue occurred, and it can usually be pinpointed in a single round.
Use tickets for anything that needs a record or involves your account and orders; use email if you can't log in to the dashboard; use Telegram for questions that fit in one message. All three channels are monitored — they differ in the record they leave and how quickly they respond.
Account and subscription changes, payment checks, refund requests and connection problems are all best handled by ticket: your account details are attached automatically, the exchange is logged, and you can follow up at any time.
Open a ticketBest when you can't log in to the dashboard, or when you need to attach a long log or a screenshot. Include your username and the time the issue occurred and you'll save a round trip.
Send an emailGood for short questions: checking whether a particular route is available, following up on a refund, or asking how to do something. For anything involving account or order details, a ticket is still the better option — it keeps a record of the exchange.
Message us on TelegramFor the same type of issue, the more specific the details you include, the faster it can be pinpointed. The table below lists what's worth sending along, by issue type.
| Issue type | What to include |
|---|---|
| Account & login | Username, registration date, and the exact message you see when logging in |
| Payments & orders | Order ID, payment method, payment time |
| Connection & routes | Client platform, your region, and a screenshot or the exact error text |
| Refund requests | Order ID, and when you submitted the refund request |
| Clients & subscriptions | OS version, client name, and the message shown when importing the subscription |
All of the above can go in a single ticket — there's no need to submit the same issue twice. If you're not sure what to write, the time the problem occurred plus the exact message you saw at the time already covers most cases.
Five questions about support channels, response times and the refund process.
Most tickets get a first reply within 24 hours. You can keep adding information to the same ticket rather than submitting a new one; your updates are appended to the existing thread, so the person handling it sees the full context.
No. A username and password are enough to register — no email address required. Keep your username and password on a device you trust or in a password manager, and don't check "save password" on shared devices.
This service offers a 60-day refund with no questions asked: open a ticket in the dashboard, include your order ID and state that you're requesting a refund — no reason needed. You can follow the progress in the same ticket.
Start with the self-check steps in the Help Center under "Connection & Troubleshooting": switch route types, restart the client, and confirm your subscription has been updated. If it still doesn't work, submit a ticket with a screenshot of the error and your region — that speeds up handling.
Account changes, orders and refunds are handled more directly by ticket — the agent doesn't have to verify your identity again, and you can check progress in the dashboard at any time. Email and Telegram suit questions and confirmations, such as asking whether a route is available or following up on a refund request.
The Help Center groups troubleshooting steps into four categories — Account & Subscription, Connection & Troubleshooting, Speed & Routes, and Billing & Refunds. Taking a quick look is usually faster than waiting for a reply.