Where to go for what
Support handles the things a guide cannot: account-specific problems, verification questions and payments that behave oddly. Before you reach out, this table shows the fastest route for common situations.
| Issue type | Where to go |
|---|---|
| How registration or KYC works | Registration and KYC guides |
| A payment that has not arrived | Official support with time and amount |
| Verification stuck or unclear | Official support with your account email |
| Setting or changing limits | Your in-account tools; Security explains |
| Login you do not recognise | Official support, treat as urgent |
verified on the official site — 2026-08-10
For anything account-specific, the official channels are the destination. You can reach Zora.bet support directly, and the rest of this page is about making that contact as efficient as possible.
What to have ready
The single biggest time-saver is arriving prepared. Support cannot look into an account it cannot identify, so gather a few things first.
Your account email, so they can find you. The rough time and amount of any transaction in question. Any reference or confirmation you were shown. And a one-line summary of what you expected versus what actually happened.
What you should never share is your password. No genuine support request needs it, and being asked for it is a warning sign, not a normal step. Keep it to yourself even mid-conversation.
How to describe an issue
A clear description gets a clear answer. Vague ones bounce back with questions and stretch a five-minute fix into a day.
Lead with what happened, plainly: what you did, what you expected, and what you got instead. Add the when and how much. Mention anything you already tried, so nobody suggests it again.
One concrete example beats a paragraph of frustration. "I requested a withdrawal on the 8th for X amount and the status still shows pending" tells the team more than "my money is stuck." The more precise you are, the faster they can act.
Screenshots help when they show a status or an error rather than a whole cluttered screen. Crop to the relevant part, and make sure no password or full card number is visible in what you send.
Escalation and complaints
Most questions end at the first contact. When they do not, there is a path forward.
If a first reply does not resolve things, say so and ask for the matter to be escalated or formally logged as a complaint. Keep your own record — dates, what was said, any reference numbers — because a tidy history makes a complaint far easier to progress.
Stay factual and specific even when you are frustrated. A calm, well-documented complaint moves faster than an angry one. The formal steps and any timelines are defined by Zora.bet, so follow the process the official channels lay out rather than any figure invented here.
Response expectations
It is fair to wonder how long a reply takes. Honestly, this independent site cannot promise a number — response times are set by Zora.bet and depend on the channel and how busy things are.
What you can do is influence your own outcome. A well-prepared, clearly described issue tends to resolve in one exchange, while a vague one invites a slow back-and-forth. If a matter is time-sensitive, such as a login you do not recognise, flag that urgency up front so it is triaged accordingly.
When you are ready, gather your details and contact support. Being prepared is the closest thing there is to a shortcut, and it costs only a minute or two before you ever open the chat.