Support & Contact

Contact VPNPF: Support Channels

Account, subscription, connection and billing questions all go through the ticket system in your dashboard; including your account name, platform and any error messages cuts down on back-and-forth. For pricing and route questions before you buy, check the plans page and the troubleshooting guide first.

Go to Tickets Read the troubleshooting guide

Support Channels and When to Use Them

Human support is handled entirely through the ticket system in your dashboard. Tickets are tied to your account, so the support team can see your orders, data usage and route history directly instead of asking for them again; every ticket has its own ID and status, and closing the window never loses the context.

Before opening a ticket, it is worth trying the self-service option that matches your issue:

  • Installation and first-time setup: follow the per-platform steps in the getting started guide, which covers the order of app downloads, subscription import and connectivity checks.
  • Connection failures, unstable speeds, frequent disconnects: work through the troubleshooting guide by symptom first — it covers common cases such as failed subscription updates, DNS errors and mobile clients dropping in the background.
  • Account, subscription, orders and refunds: submit these through the ticket area in your dashboard — they require checking account data and are handled by the support team.
  • Choosing a plan or route: see the plans page and the network page for the full list of prices, data packs and coverage across 110+ countries / 250+ routes.

Steps to Submit a Ticket

  1. Open the dashboard and sign in. The ticket area lives inside the dashboard and requires a login, so your request automatically carries your account and subscription status and the support team does not have to ask for order details.
  2. Pick a category. The dashboard files tickets under four headings — account and subscription, connection and faults, speed and routes, billing and refunds. The category only affects the handling order, and if you pick the wrong one the support team can pass it on.
  3. Describe the problem and include the details. Writing everything listed in the next section in one go cuts down on back-and-forth; paste error messages and screenshots straight into the ticket rather than linking to an external file host.
  4. Check the ticket status after submitting. Once the support team replies, the ticket shows a new message; add follow-up details for the same issue as a reply in the original ticket rather than opening a new one, which would split the context.

What to Have Ready Before You Open a Ticket

  • Your account username. You never need to provide a password, and you should never send one in a ticket under any circumstances.
  • Device platform and client name: which of Windows / macOS / iOS / Android / Linux you are on.
  • Subscription status: the remaining data and expiry date of your current plan or data pack, visible on the dashboard home page.
  • The name and location of the route that is having problems.
  • The exact error message or a screenshot, plus roughly when the problem started.
  • The troubleshooting steps you have already tried and what happened.
Do not submit passwords, screenshots of payment receipts or full subscription links. The support team does not need any of these to look into an issue; ignore any message that asks for your password or payment details in the name of this service.

Handling Order and Response Times

Tickets are handled in the order they arrive, and there is no instant response. How quickly you get a first reply depends on how many tickets are waiting, and it takes longer during holidays and peak periods of route faults. A complete, specific ticket usually reaches a conclusion in one round; a ticket missing information needs details confirmed first, which adds rounds.

If a ticket has had no status update for a long while, you can add a single follow-up question in the original ticket; submitting new tickets does not speed anything up and only splits the context of the same issue.

Route fault tickets take priority over general usage questions. If several routes misbehave at the same time, check the dashboard home page for a notice first, then decide whether to open a ticket.

Open a ticket when:

  • you cannot sign in, a subscription has not activated, or an order status looks wrong;
  • a connection problem persists after working through the troubleshooting guide step by step;
  • refund requests and billing checks;
  • anything else that needs a human to check your account data.

Try self-service first when:

  • a single website will not load: check whether the site itself is down or the route is at fault, and try another route;
  • your configuration stops working after a client update: re-importing the subscription usually fixes it;
  • connecting a new device for the first time: go through the getting started guide step by step to check permissions and settings.

Refunds and Billing Issues

Refund requests are submitted as a ticket — just include the order number and your reason. This service offers a 60-day no-questions-asked refund, returned through the original payment channel; how long it takes to arrive depends on that channel's processing speed (Alipay / WeChat / USDT).

Data packs are a one-time purchase: use them until they run out, and they never expire. Monthly subscription data resets each month on the activation date; if you upgrade mid-cycle, the price difference is converted into remaining days.

If a charge looks wrong, include the order number and payment time in your ticket and the support team will check the order record and explain. Full pricing for plans and data packs is listed on the plans page.

FAQ

Where is the ticket area?
Sign in to the dashboard and go to the ticket section to submit one. Opening the ticket area while signed out takes you to the login page first; signing up only needs a username and password — no email address required.
Why do support requests require a login?
Because tickets are tied to your account, the support team can see your subscription status, order history and route usage directly — you do not have to supply that data by hand, and account details never have to travel through public channels.
How long does a reply take?
Tickets are handled in the order they arrive and instant replies are not promised; the time to a first reply depends on how many tickets are waiting and takes longer during holidays and peak periods of route faults. A complete ticket usually reaches a conclusion in fewer rounds.
Can I submit multiple tickets for the same issue?
It is not recommended. Duplicate tickets do not speed anything up and split the context of the same issue. Add extra details as a reply in the original ticket, which always stays in the dashboard's ticket list.
How do I request a refund, and how long does it take?
Just include the order number and your reason in a ticket. This service offers a 60-day no-questions-asked refund, returned through the original payment channel, and how long it takes depends on that channel's processing speed. Data packs are a one-time purchase: use them until they run out, and they never expire.
Can I send a password or subscription link in a ticket?
No need. When looking into an issue the support team views what it needs through the account link and will never ask for a password or a full subscription link, so keep ticket contents to the technical information needed to troubleshoot.