BC Game Support Contact Guide: How to Report a Problem Clearly
How a problem is reported often matters as much as the problem itself. This page focuses specifically on communication: what to include, what to attach, and what usually slows a case down.
One complete, factual message with your UID, the exact issue and supporting proof resolves cases faster than several short or emotional messages sent across different channels.
Why good support messages solve more than angry ones
Support teams work faster with clear, specific information than with frustration alone. A message that states exactly what happened, when, and with what proof gets triaged and resolved more efficiently than a vague complaint.
What every support request should include
- your account UID
- the exact date and time the issue occurred
- the specific action affected: deposit, login, withdrawal or verification
- the amount or reference involved, if relevant
- supporting screenshots or transaction details
| Problem type | What support needs | What the user should attach |
|---|---|---|
| Deposit issue | amount, time, route | screenshots and transaction proof |
| Login issue | account identifier, error message | screenshots and access details |
| Withdrawal issue | UID, wallet details, status | withdrawal history and notices |
Problem-specific checklists
A deposit issue needs the asset, network and transaction proof. A login issue needs the sign-in method used and any error message shown. A withdrawal issue needs the UID, wallet details and current status. Matching your message to the right checklist avoids back-and-forth requests for missing details.
A complaint template you can copy
"Hello, I need help with a specific account issue. My UID is [UID]. The issue began on [date/time]. The affected action was [deposit / login / withdrawal / verification]. The amount or relevant reference is [value]. I have attached screenshots and transaction details below. Please review the case and advise the next required step."
What not to send and why
- vague messages with no transaction or account details
- multiple tickets describing the same issue differently
- accusations without proof, which slow down triage rather than speeding it up
When to follow up and how to stay consistent
If a reasonable amount of time has passed with no update, one calm follow-up referencing your original case is enough. Repeating the same complaint across new tickets usually resets progress rather than accelerating it.
Frequently asked questions
What should every BC Game support message include?
Your UID, the exact date and issue type, the amount or reference involved, and supporting screenshots or transaction proof.
Why do some support cases take longer to resolve?
Incomplete details, multiple inconsistent tickets and messages without proof are the most common reasons a case takes longer than necessary.
Is there a template I can use to contact support?
Yes. State your UID, the date and time, the affected action, the relevant amount, and attach your proof in one complete message.