Your receipt exists, but the purchase is missing. The useful next step is a support request that identifies the order, describes the missing result, and gives staff enough context to investigate. A screenshot of your entire inbox or bank account adds exposure without necessarily adding evidence.
Think of the ticket as a small case file. Someone who was not present at checkout should be able to understand what you bought, where you expected it, and what you have already checked. Keep private details inside the appropriate support channel and keep the explanation readable.
Describe what is missing before collecting attachments
Missing can mean several different things. You may have no confirmation email, a confirmed purchase with no download, a resource available to download that fails to start, or an in-game benefit that has not appeared. Those are different observations, so use the one that matches what you can actually see.
For example: “I have a receipt for the named package, but the download link is unavailable” is clearer than “payment broken.” If the package contains multiple components, say which arrived and which did not. Partial delivery is valuable information; do not hide it inside a general complaint.
Check the account and delivery instructions shown for your order. Tebex's buyer support page recommends checking that you are signed into the correct game account and allowing at least thirty minutes for possible delivery delays before contacting its support team. That is guidance for reaching that team, not a guarantee that every product uses identical delivery timing. Tebex buyer support.
Record your checks without repeating them indefinitely. If the seller asks for a particular additional step, you can add its result to the same timeline.
Identify the order with the reference it actually has
Copy the order or transaction reference accurately from the receipt. Keep its prefix and punctuation. If your receipt contains several references, label them as they appear instead of guessing that they are interchangeable.
Tebex's customer support form explicitly asks for a transaction, invoice, or reference ID along with contact details and a description. That is a much better starting point than trying to prove a purchase through a large collection of unrelated screenshots. Tebex customer support form.
Include the store address, product name, purchase date, and the account or character context relevant to delivery. If a staff member requests an account identifier, ask which identifier they need and provide it through the private ticket. A character name alone may not explain which account received an entitlement.
Treat the reference as private support information even though it is not a password. Publicly posting it alongside your email and account details creates a more complete record of your purchase than strangers need.
Build a short timeline with a time zone
Write the sequence as observations: order completed, receipt received, first delivery check, later check, ticket opened. Include the time zone when giving clock times. “Nothing arrived at nine” becomes much more useful when staff can place that nine o'clock beside their own records.
There is no need to produce a second-by-second diary. A compact example might say that checkout completed at 19:10 UTC, the receipt arrived shortly afterwards, and the expected download was still unavailable at 19:45 UTC. Label an estimated time as approximate.
Distinguish a displayed status from your conclusion. “The receipt says completed” is an observation. “Your delivery system is broken” is a diagnosis that the evidence may not support. Giving staff the observation lets them compare the order and delivery records without first undoing an assumption.
If the problem changes, add a timestamped update. A download appearing later is useful evidence even if another part of the package still fails.
Crop screenshots around the question being answered
Every attachment should have a purpose. A screenshot may show the exact error, the package name, or the missing download area. Crop away unrelated conversations, other purchases, full account details, and browser tabs that are irrelevant to the issue.
Use solid, permanent redaction on a copy when something must be hidden. Then reopen the exported image and inspect what is actually visible. A decorative blur or an editable shape in a document is a poor way to prepare a private support attachment.
Never include passwords, recovery codes, complete card details, session cookies, or server secret keys. If a log includes a credential inside a URL or connection string, remove the secret while preserving the surrounding error text. Note that you redacted it so the reader understands the gap.
For resource startup errors, a short text excerpt is often easier to read and search than a photograph of a monitor. Include the relevant error and nearby context, with the resource name and time. Avoid uploading an entire configuration or database just because the ticket accepts attachments.
Send one request through a channel you deliberately opened
For an order from this store, start from the store contact page. Describe the issue there and follow the instructions associated with your actual order. A person who sends an unsolicited private message after seeing your public complaint has not established that they handle your purchase.
If the purchase was processed by Tebex and the issue needs its buyer support, use the support route on Tebex's own website. The store team and the payment support team can have different records and responsibilities. Name the existing ticket when moving between them so the context travels with the issue.
When Tebex has opened a shared support email thread involving a seller, its seller guidance says communication should stay in that original thread. Keeping the investigation together helps everyone see the same evidence and the same proposed next step. Tebex seller support guidance.
Opening several fresh tickets with slightly different descriptions can leave separate people investigating different versions of the problem. Update the original case unless the support team directs you elsewhere.
Use a compact request that can survive a handover
Your message can follow this simple structure:
- Order: the product, store, purchase date, and receipt reference.
- Expected result: the download, entitlement, or in-game benefit described for the order.
- Actual result: what is visible now, including any exact error.
- Checks completed: relevant account and delivery checks, with approximate times.
- Evidence: a short log excerpt or carefully cropped screenshot.
End with the help you need, such as confirming the delivery destination or investigating an unavailable download. Avoid demanding a particular technical fix before anyone has identified the cause.
When a reply arrives, answer its questions in the same order and say which suggested action you completed. If the issue is resolved, confirm what changed and whether the entire package is now accessible. That closes the loop for you and gives the next staff member a usable record. A good ticket does not need to be long. It needs to keep the right facts together and leave everything else out.
