Skip to content
CasinoCanFollow the money, understand the account
Follow the money, understand the account

Build a clear Zora support case

A support message is easier to investigate when it names one specific unresolved process.

3 min read
01

Keep one problem identifiable

A support message is easier to investigate when it names one specific unresolved process. For Zora, distinguish a deposit that has not credited, a reward that has not activated, a withdrawal awaiting action and a game round with an unclear result. They can be related, but they use different references. State which result you expected and what the interface actually shows. Avoid sending a long list of assumed causes before the underlying operation has been identified.

02

Use a compact chronology

A useful timeline has the action time, reference, amount or stake where relevant, and subsequent status changes. For an illustrative case, list a deposit submission, the provider’s confirmation and the casino entry still showing pending. If support later requests a document, add that request and the submission date as separate events. Do not erase the earlier states when the case changes: the sequence can explain why two screenshots seem inconsistent.

03

Follow the response rather than duplicate the request

Read whether the answer asks for information, confirms an investigation or reports a final outcome. Those are different states. Keep the case identifier when replying so the new detail is connected to the original enquiry. Use the operator’s secure channel for requested documents, and omit passwords or authorisation codes. If the response refers to a rule, compare it with the selected campaign or transaction rather than a general banner. CasinoCan can explain this recordkeeping method but cannot access, expedite or decide an individual Zora case.

The public support entry is available before logging in
The public support entry is available before logging inPublic Zora interface · 9 November 2026 · English version.
04

Use a factual message with one requested outcome

A practical first message can state: “I submitted the transaction identified below; the provider reports this state; the casino history reports that state; please explain whether an action is required from me.” Add amount, currency and the relevant times. For a game issue, replace the payment references with the exact title and round identifier. Avoid including unrelated promotions, assumptions about system failures or a demand based on a different player’s experience. The requested outcome should be specific: identify a transaction, explain a status or reconcile an amount. This helps keep a case focused even if it passes between support staff.

05

Separate evidence, interpretation and unanswered questions

A timeline entry such as “14:05: screen showed pending” is an observation. “The provider rejected the payment” is an interpretation unless a record actually says so. “Which side is awaiting confirmation?” is the unanswered question. Keeping those three types apart prevents a later correction from making the entire account look inconsistent. Attach or reference evidence that supports the observation and label any uncertainty plainly. If two screenshots show different states, preserve their order and capture times. The change may be exactly what the investigation needs to understand. Do not silently replace the first screenshot with the newer one and lose the sequence.

06

Close a case by checking the stated outcome

A response saying the case is resolved should be compared with the outcome it describes. If a credit was promised, locate the corresponding entry; if a document was requested, verify submission; if the provider must investigate, preserve the trace reference. Those are distinct closing conditions. If the result does not match, reply in the existing case with the specific remaining difference instead of restarting the full story. Record the final amount, status and explanation once they agree. This does not guarantee a favourable decision or a particular response time, but it creates an understandable record that can be used for an authorised follow-up without duplicate or contradictory claims.