IT7 Game — Building a clear query about a game or event result

Name the problem before collecting screenshots

Decide whether the question concerns access, an accepted action, the rules, a recorded result or an account movement. Those are different problems. A collection of screenshots can be large while still omitting the one identifier needed to connect them. Begin with a one-sentence description of what is unclear.

For example, “the accepted entry names this event, but the result page shows another reference” identifies a concrete mismatch. “The game did not work” does not. Precision at this stage helps determine whether the relevant evidence is a round history, a ticket, an event listing or a payment record.

Keep the identifier with the evidence

A screenshot of cards, numbers or a live feed can lose its meaning when cropped away from the title and reference. Include the relevant room, draw or event identifier in the evidence available to the service. If the image cannot show all of it, write the missing identifier in the accompanying description.

For event categories, including cockfighting where the service supplies it, consecutive listings can be visually similar. The named match and its recorded status are essential context. The presence or absence of a stream does not replace the event identifier or establish the settlement rule that was applied.

Reconstruct a short timeline

List the accepted action, the observed interruption or change, and the result or status seen afterward. Use the displayed time zone if known. Keep observations separate from conclusions. “The video stopped” is an observation; “the event was cancelled” is a conclusion that needs a recorded status or rule to support it.

A timeline does not need every click from the visit. Include the steps that connect the relevant entry to the disputed display. Mark anything unknown rather than filling it with a guess. The II7 history article explains how to distinguish a session from the individual rounds within it.

Quote the rule or label being questioned

If the issue is interpretation, identify the exact rule or screen label that seems inconsistent with the outcome. A main result and an additional selection may follow different definitions. A ticket can depend on a matching condition that is not visible in a cropped result image. Naming that condition makes the question specific.

If the rule is unavailable, say that the definition is missing rather than inventing it. The service needs to supply the applicable terms before the outcome can be evaluated against them. The directory's general format explanations cannot substitute for an unverified table's or event's settlement policy.

Keep unrelated transactions out of the same claim

A successful deposit does not prove that a later game action was accepted. A game result does not establish that a withdrawal reached its receiving destination. These events may share an account, but their references answer different questions. Including them without explanation can obscure the issue being raised.

If a balance movement is relevant, connect it to the affected record explicitly. State the transaction type and the relationship you are asking the service to explain. The IB7 balance guide helps separate game outcomes, payments and promotional entries before they are combined into a timeline.

Write a query that can be followed

A compact structure is enough: identify the account through the service's normal support process, name the affected title or event, supply its reference, describe the expected rule and state the observed result. Add the relevant times and evidence. Avoid supplying a password, one-time code or unrelated private information in the message.

After sending the query through the destination's stated support route, retain its reference if one is supplied. Follow that existing case rather than opening several descriptions with different details. This guide cannot promise a response time or outcome; its purpose is to make the underlying question clear and consistent.

IT7 query questions

Is a frozen live feed enough to prove an event was void?

No. It shows a display interruption. The event's recorded status and applicable terms are needed to determine whether the event was cancelled or treated as void.

What if I cannot find the rule that explains the result?

Ask the service for the applicable definition and identify the affected record. Keep the uncertainty explicit rather than using a rule from a different game or event.