Before contacting support
- Confirm your internet connection is stable.
- Make sure your Telegram session or app state is current.
- Prepare your player or account context before reporting.
How to get effective support in TAPCO
Use this guide to submit a clear report, understand what the support team can handle, and avoid common security mistakes during issue resolution.
Best report format
Describe what happened, when it happened, and what you expected instead. Add screenshots when possible. Clear reports reduce back-and-forth and speed up investigation.
Support scope
Support can help with gameplay consistency, account access questions, referral visibility concerns, mission or progress confusion, and general product understanding.
Security warning
Never share private keys, seed phrases, one-time codes, or any wallet secret with anyone claiming to be support. TAPCO support will not ask for those secrets.
What support can and cannot do
Understanding what falls within support scope saves time for both sides. Support can investigate reports that include enough context to reproduce or trace the issue. It can confirm whether a reward event was processed, explain why a referral credit is pending, clarify which policy rule applies to a specific situation, and provide account status information based on verified identity.
Support cannot override verified server-side outcomes or manually grant rewards that were blocked by anti-abuse validation. It cannot bypass withdrawal policy limits, restore progress that was not server-recorded, or confirm outcomes that depend on future platform decisions. If you encounter a response that does not match your expectation, check whether the behavior is documented in the FAQ or rewards policy before requesting escalation — most apparent discrepancies are explained by system rules that are published on the site.
Contact and response expectations
The official support contact is support@tapcogame.io. When submitting a request, include your Telegram username or account context, the date and approximate time of the issue, a clear description of what you observed versus what you expected, and any screenshots that show the visible discrepancy. Reports submitted without this information typically require at least one follow-up exchange before investigation can begin, which delays resolution.
Response times vary depending on volume and issue complexity. Policy and account questions that are fully documented in the request usually receive faster responses than technical escalations that require backend log review. If you do not receive a reply within a reasonable period, sending a follow-up with the original message context attached is appropriate. Do not submit duplicate reports across multiple channels, as this fragments the case context and can delay rather than accelerate resolution.