vipyes Support – Access and Website Help

Website problems

A website issue can include a page that does not load, a menu that does not open, a layout problem or information that appears missing. Refresh once, confirm the current page address and try a current browser. If the same website issue persists across devices, use Contact to report what page was affected and what you expected to see.

Do not include passwords, OTPs or bank details in a website report. A page URL, device type, browser name and a description of the visible error are normally more useful.

Device and browser problems

If the issue happens on only one device, check the connection, browser version, storage state and content-blocking settings. Private mode can also change cookies and session behaviour. Make one change at a time so you can tell what solved the problem.

If a downloaded file is involved, switch to the Download page. If the issue is about opening a mobile route, use the App page.

External account problems

Password recovery, account status, identity checks and account-specific restrictions are controlled by the service that owns the account. This website cannot safely solve those tasks by collecting your credentials. Use the recovery or support process provided by the account service.

Be cautious if someone offers to restore access only after you send an OTP, password or payment. Those are sensitive details and should not be shared in ordinary support messages.

What to include in a useful report

State the page, the action you tried, what happened, the browser or device type and whether the issue repeats. If you include a screenshot, remove personal account data first. Clear information helps distinguish a website problem from an account problem without exposing sensitive data.

Make the problem reproducible when possible

A useful report explains the exact page, action and result. Note whether the problem happens every time or only under one condition, such as mobile data, a particular browser or a specific screen width. This information is more actionable than a general statement that the website is broken.

If you can reproduce the issue, write down the shortest sequence that causes it. Do not include confidential account information in that sequence.

Use screenshots safely

Screenshots can help with layout errors, but they may also capture phone numbers, account names, balances, transaction references or notification previews. Crop or cover those details before sharing the image.

A screenshot of the browser address bar and the visible error can often be enough for a website problem. Avoid screenshots of password fields or one-time codes.

Cache and extensions can change what you see

A browser extension, content blocker or old cached file can affect one device while the site works elsewhere. Test in a clean current browser profile when practical. If that changes the result, re-enable extensions one by one instead of disabling security tools permanently.

Clear only the site data you understand. A full browser reset can remove useful sessions and settings from unrelated sites.

Be cautious with unsolicited support

Real troubleshooting does not require you to hand over a password, OTP, bank password or card PIN through chat. Messages that create urgency, ask you to install remote-control software or demand a payment before explaining the problem deserve extra caution.

Open the intended support destination yourself rather than relying only on a link sent by an unknown person.

Separate a temporary outage from an account problem

If several pages fail at the same time, the issue may be a website or network problem rather than your account. If the website works but one account action fails, the issue may be account specific. That distinction helps you choose whether to wait, troubleshoot the device or contact the account service.

Avoid changing passwords or registration details during a broad outage unless the account service specifically requires it.