THE QUICK TAKE
Open the current store listing, check App support, and describe one observable problem. Include what happened and when; leave out passwords, login codes and unrelated personal details.
Android consumer information for readers in the Philippines · Documentation checked, no support response tested
Which contact details does Google Play show?
Google’s Android instructions say to open the app’s Play Store detail page, tap App support and review its contact information. For Tongits Go, the developer listing on Google Play is the source to recheck before sending a report.
On 20 September 2026, its App support section displayed tongits@playjoygame.com. The description separately listed hi@tongitsgo.com. These are two different addresses displayed on the same listing; we cannot establish which mailbox is monitored or how quickly either replies. Use the current App support field as your starting point and check again if it changes.
This independent guide cannot access your game account or open a ticket on your behalf. Do not put a report or account details into a public review just to reach us.
Turn “it is broken” into a short sequence
Start a private note before drafting the message. Record the date and time with Philippine time, UTC+8, the screen you were on, the action immediately before the problem and the exact visible error. If there is no error message, write that instead of inventing one.
Here is an invented wording example, not an incident we tested: “At [time], I opened [screen] and tapped [button]. I expected [result], but the app returned to [screen]. No error text appeared.” Replace every bracket with your own observation or remove the line.
Keep observation separate from explanation. “The screen stopped responding” describes something you saw. “The latest update caused it” needs evidence you may not have. If you have only seen the problem once, say once; do not describe it as happening every time.
Copy this private report template
Google recommends identifying the app, explaining the problem and stating the response you want. The extra fields below are our suggested way to organise that information. They are not a mandatory developer form.
| Field | What to write |
|---|---|
| Subject | Tongits Go — [one short problem] |
| Observed at | [date, time, Philippine time UTC+8] |
| Device | [phone model and Android version, if known] |
| App version | [installed version if visible; otherwise unknown] |
| Steps | 1. [action] 2. [action] 3. [visible result] |
| Expected / actual | [what you expected] / [what appeared] |
| Frequency | [once or observed count; no guess] |
| Request | Please advise how to resolve [specific problem]. |
Do not use the store’s update date as your installed version number. Leave an uncertain field marked “unknown”. A short accurate report is more useful than a complete-looking report filled with guesses.
Review the exact attachment you will send
If an image helps explain the screen, make a separate copy for sharing. Crop unrelated areas and cover private details with solid blocks. Open the saved copy again: check notification banners, email addresses, phone numbers, account identifiers and payment information at every edge. If you cannot safely separate the error from private material, describe the error in text.
Never include a password, one-time sign-in code or recovery code in the report. Keep the original evidence privately. Our account-protection guide covers suspicious replies and account recovery separately.
Check the draft before sending
EDIT THE REPORT
A draft says, “The update broke everything. Here is my login code. Fix it.” Which useful details are missing, and what must be removed?
Reveal the editing checklist
Remove the login code. Replace the unverified cause with the observed screen, action, time and exact error. Add a specific request and only a privacy-checked attachment if needed. Do not invent a version number or repeat count.
Keep a copy of the message, its sent time and any ticket reference. Sending a report does not prove delivery, a fix or account recovery. For a Google Play purchase issue, use the relevant purchase-support process; our purchase-verification guide explains preventive settings, not a refund guarantee.
Sources & scope
Checked on September 20, 2026. Contact details were read from the public Google Play listing on 20 September 2026. Google Help supplies the contact path; the worksheet and example are our editorial suggestions. We did not contact support or verify mailbox delivery.
- Google Play Help — contact an Android app developer ↗Official instructions for finding App support and describing an app problem.
- Tongits Go — developer listing on Google Play ↗App features, virtual-item policy and the update dated 28 August 2026.
This is an independently written educational guide, not an official rulebook or a promise of results. Illustrations are original examples, not screenshots from the game.
