Issue preparation and reporting routes
Contact and issue reporting
To report an Ome1on1Chat issue, prepare your UID, approximate time, conversation format and a concise description of what happened. Use the reporting entry available in the product. A support email will be added only after the domain mail process is configured; no placeholder address is provided.
Do not include passwords, full payment credentials or unrelated private material in an issue description. Share only information needed to explain the problem.
Issue preparation and reporting routes
A UID and approximate time are more useful than a broad description alone.
Choose the reporting route actually shown in your product interface.
A support email is listed only after domain mail is configured.
Choose the route that matches the immediate problem
For behavior during a conversation, end the interaction first. Use Block to prevent further contact where available, then Report to flag the conduct through the current product entry. Use those controls immediately rather than waiting to open a separate support conversation. Staying in a harmful call to gather more material can increase your exposure without making the report clearer.
For a technical or account issue, stop repeating the action if it could create more charges, claims or conflicting sessions. Note the screen you were using and what happened. The safety guide covers urgent conversation boundaries, while this page focuses on organizing a report. A general question about access may already be answered in the FAQ, which can save you from submitting an incomplete request.
Prepare a report someone can actually investigate
Begin with your UID if the interface provides one. Add the approximate date and time, including your time zone, the conversation format and the entry point you used. Then describe the sequence in plain language: what you selected, what you expected and what appeared instead. A short factual timeline is more useful than a long message that omits the account reference.
For a conduct report, include the other account's UID only if the product supplied it. Do not invent a name or claim to know a stranger's identity. For a display or access issue, record the exact wording of a relevant prompt when possible. If you no longer have a detail, say so rather than guessing. Clear uncertainty is easier to assess than confident but inaccurate information.
- Your UID, approximate time with time zone, and the relevant device or browser.
- The format and product area involved, such as text, voice, video or matching.
- A concise account of the action, expected result and actual result.
Keep sensitive material out of the description
A report rarely needs your password, complete payment credentials or unrelated personal files. Do not attach private images merely because they were mentioned in a dispute, and do not send identity documents through an unverified channel. If the available reporting form requests a specific item, read that request in context and provide only what is necessary for the stated issue.
For a coin or purchase question, record the current product label, the approximate time and the balance behavior you observed. Do not rely on a price copied from an old page or another user's screenshot. The coins guide explains which current details to check before buying and which facts to preserve if the displayed result differs from your expectation.
Understand the limits of match recovery and support
A random match can end without leaving a recoverable connection. Follow and Message are account features for supported connections; they do not guarantee that a closed random session can be reconstructed. A support description should therefore not promise that the other person can be found from a vague recollection of their appearance or opening line.
Reporting a problem also does not create a particular outcome or response-time guarantee. Use the route shown in the product and keep any confirmation or reference it provides. Avoid sending duplicate reports through multiple controls unless the interface asks you to add information. The how it works page explains the account boundary in more detail so a recovery expectation does not distract from the issue you are reporting.
Support email will be added after domain configuration
There is no invented support mailbox on this page. A support email address can be added after the domain email process is configured and the address is available for use. Until then, use the reporting entry available in the product for conduct, account, access or technical issues. Do not send sensitive information to an address supplied by a stranger in chat.
This limitation is intentional. Publishing an unconfigured address would create a false support channel and could leave a user's report unanswered. When a real address becomes available, it should appear here as a direct way to contact support. In the meantime, a well-prepared UID, approximate time and concise description remain the best starting point for any route the current interface provides.
One person is enough
Start with the facts and the available route
End any unsafe interaction first, preserve the relevant UID and timing, and submit a concise report through the entry provided in your session.