Login or access problem
Use the account-access guide to understand the .live route and the redirect that follows the access button.
The legacy gobet365.live template includes Email, WhatsApp and Telegram labels filled with 0000000. Those values are placeholders, not usable contacts. No working first-party email, phone, WhatsApp or Telegram destination is published in the site files examined for this guide.
The legacy support block uses Email, WhatsApp and Telegram labels, but the values are placeholders rather than usable contact details. Do not use 0000000 as an email address, phone number or messaging account.
| Channel | Status | What was found |
|---|---|---|
| PLACEHOLDER | The legacy template shows 0000000. No working mailto: destination is published. | |
| PLACEHOLDER | The legacy template shows 0000000. No working WhatsApp or wa.me destination is published. | |
| Telegram | PLACEHOLDER | The legacy template shows 0000000. No working Telegram or t.me destination is published. |
| Telephone | NOT PUBLISHED | No tel: link or customer-service telephone number is present in the .live files examined for this guide. |
| Support identity | NOT IDENTIFIED | The .live files do not identify a legal operator, support department, service address or published support hours. |
The placeholder value 0000000 is not a usable support contact. A brand name, logo, support icon or social-media profile is also not enough to establish that a contact belongs to the service.
Use the account-access guide to understand the .live route and the redirect that follows the access button.
No password-reset form is present on the .live pages. If a recovery option appears after a redirect, verify the destination independently before using it. A redirect from .live alone does not establish who operates the destination.
If the problem appears only on a phone, first check that the same .live page opens in the browser. A separate m. address is not required simply to view the responsive interface.
Do not assume that .info, .org, .net, .me or an m. address is operated by the same entity as .live.
No payment-support contact or complete payment/withdrawal terms are published in the .live files. Keep transaction records and do not send identity or payment documents to an unverified chat account.
For gambling-harm support, use independent help rather than waiting for a first-party support channel that is not published on the .live pages.
Before sharing account, identity or payment information with a support contact, check the contact itself first:
Do not send your password, one-time login code, recovery code or two-factor authentication code to a person claiming to be support. Enter credentials only on a service page whose address you have independently checked.
Do not install screen-sharing or remote-control software at the request of an unverified contact. A WhatsApp, Telegram or social-media account is not validated support simply because it uses a familiar brand name or logo.
If identity verification is required, use a secure upload area only after checking the service and destination. Avoid sending passports, payment-card images or financial statements through an unverified chat channel. The KYC guide explains the verification status for .live.
For an account or payment dispute, keep transaction references, dates, screenshots and the exact web addresses used. These records can help when speaking to a verified operator, payment provider or relevant authority.
The .live project does not publish a working first-party support email, telephone number, messaging account, service address or support hours. It also does not identify a legal operator or gambling regulator that could independently tie a support channel to the service.
If first-party contact details become available, this page should publish the exact channel, the source that connects it to the service and the review date—not a number or handle based only on name similarity.