Treat the Account as a Product
When an account does not match what was agreed, a clear record can help you explain the problem to the seller or, if needed, to a marketplace’s dispute team. Treat the account as a product and a working tool: describe what was offered, what was delivered, what is wrong, and what outcome you are requesting. Keep the account’s use within the relevant platform’s terms. A complaint should address a genuine mismatch or defect, not seek a way around platform checks or restrictions.
Start by reviewing the listing, order details, and any written messages exchanged before delivery. Identify the specific promise that matters to your claim. It might concern the account type, access to an associated mailbox, a stated setup condition, or another feature described by the seller. Avoid relying on assumptions about what an account should include. If a detail was not stated or agreed, present it as a question or context rather than as a definite seller commitment.
Make a working note before writing to the seller. Separate what you can document from what you suspect. For example, you can report that a listed access method is unavailable if you can show the listing and the current access screen. Do not claim to know why it is unavailable unless you have evidence. A factual account of the problem is easier to assess than a theory about its cause.
Save the Description and Delivery Record
Preserve the original listing or offer before its wording changes or becomes unavailable. Save a screenshot or other permitted copy showing the description, the account type, the stated inclusions or conditions, and any relevant seller disclosures. Include enough of the page to make its context clear. A cropped line without the surrounding description may be difficult to interpret later.
Keep the order confirmation and delivery record as well. These may include marketplace messages, an order page, a delivery notification, or the seller’s instructions. Retain the original files where possible, rather than relying only on notes or a rewritten summary. If the delivery was made through a marketplace, keep the record in that system and do not move the discussion elsewhere unless there is a good reason. A single traceable conversation makes it easier to follow what was promised, delivered, and reported.
Be careful with credentials and personal information. Evidence should show the relevant issue without unnecessarily exposing passwords, recovery details, private messages unrelated to the claim, or sensitive account data. Do not post credentials in a public review or send them to an unrelated party. If a screenshot includes information that is not needed to assess the problem, use a safe way to conceal it while preserving the parts that establish the claim. Keep an unaltered copy for your own records when appropriate.
Record the Condition Before Changing It
When you discover a problem, document the account’s condition before changing settings or attempting a fix. Capture dated screenshots that show the relevant page, message, warning, missing feature, or access result. Make sure the image gives enough context to identify what it shows, and keep the original file if possible. Note the time of discovery in your own record, using the date and time displayed on your device or the marketplace where relevant. Do not present a screenshot’s file date as proof of when the underlying issue began; it only helps establish when that image was saved.
Avoid changing account settings, removing recovery options, replacing contact details, or making other consequential adjustments before recording the initial state. Those actions can make it harder to show what was present at delivery or when the issue first appeared. If a change is necessary to protect the account or comply with platform guidance, prioritize that obligation, document the condition first if it is safe and practical, and record what you changed and why.
Do not repeatedly test access in ways that could trigger security checks or affect the account’s status. Follow the platform’s ordinary security guidance. The purpose of evidence gathering is to preserve an accurate account of the problem, not to probe restrictions or bypass verification.
Describe the Exact Mismatch
A useful claim connects the saved description to the observed condition. State the relevant promise in plain language, then say what you found instead. Be precise about the feature and the point at which it fails. “The account is defective” is a conclusion; “the listing says mailbox access is included, but the delivered instructions do not provide that access” describes a mismatch that can be checked.
Include the time of discovery and the steps you took to observe the issue, but keep the account brief. Explain whether you checked the delivered details, opened the relevant page, or received a displayed message. If the issue is intermittent or you cannot confirm its cause, say so. Do not turn a single observation into a wider claim about the account’s history, security, or future performance.
Distinguish between a product defect and a platform decision. An account may be affected by a platform notice or verification request, but that alone may not establish that the seller misrepresented it. Save the notice and explain what it says without guessing at the reason. If you believe the account’s delivered condition conflicts with a specific listing statement, identify both pieces of evidence. This keeps the complaint focused on what can be reviewed.
Write a Short, Factual Message
A first message to the seller can be concise while still including the essentials: the order or listing reference, the promised feature, the observed mismatch, when you discovered it, and the remedy you are requesting. Attach only the evidence needed to establish those points. Use neutral wording such as, “The listing describes access to the associated mailbox as included. After delivery, I could not access it using the provided instructions. I recorded the screen and discovered the issue during setup. Please let me know whether you can provide the missing access or arrange a replacement or refund.”
Choose the remedy that fits the problem and state it clearly. A replacement may be appropriate if the seller can deliver an account matching the description and the marketplace permits that resolution. A refund may be the suitable request when the mismatch cannot be corrected or the delivered product is not what was agreed. Do not ask for several incompatible outcomes without explaining your preference. If you are open to either remedy, say which one you would prefer and under what condition you would accept the other.
Stay polite and specific, even if the situation is frustrating. Avoid accusations, insults, threats, repeated messages, or claims you cannot support. A calm message does not weaken a valid complaint; it helps keep attention on the evidence and the requested resolution. Give the seller a reasonable opportunity to respond through the normal process, while observing any deadlines or instructions shown by the marketplace.
Keep the Conversation Traceable
Keep communication in one traceable place, preferably the marketplace’s order or dispute thread when the purchase was made there. This preserves context and can help a reviewer see both sides of the exchange. If the seller asks to switch to another channel, consider whether doing so would leave important messages outside the marketplace record. Do not share sensitive credentials in chat merely to prove a point.
After each response, update your record with what was offered, what you accepted or declined, and any new evidence. If the seller proposes a fix, ask for the steps and expected outcome in writing before making changes that could affect the account. Do not mark a matter resolved until the agreed remedy has actually been completed and you have checked the relevant condition, within the platform’s normal guidance.
If a conversation becomes confusing, send one short summary in the same thread. Restate the original mismatch, the evidence already provided, and the unresolved request. This is more useful than opening multiple parallel conversations, which can scatter the record and create uncertainty about which message is current.
Escalate Through the Marketplace Process
If the seller does not resolve the issue, or the response does not address the documented mismatch, use the marketplace’s dispute or support process. Read the instructions shown in your order or account and submit the claim through the designated channel. Procedures vary, so do not assume that a particular form, deadline, or outcome applies across marketplaces.
Organize the submission so a reviewer can follow it without reconstructing the story. Begin with a brief summary, then provide the saved listing description, delivery record, dated evidence, discovery time, seller correspondence, and the remedy requested. Label files descriptively and explain what each one demonstrates. Keep the explanation focused; extra screenshots or unrelated account history can distract from the central issue.
Be accurate about what has and has not happened. If you changed a setting after documenting the initial condition, disclose that and explain why. If the seller has offered a partial fix, include it. Do not alter evidence, omit relevant context, or submit private information that is not needed. The marketplace’s process is the appropriate route for a review; do not try to pressure the seller through public exposure or contact platform staff through unrelated channels.
Avoid Common Claim-Weakening Mistakes
Certain habits can make a valid issue harder to assess:
- Changing settings before recording the original condition, unless an urgent security or platform instruction requires it.
- Sending only a broad conclusion, such as “the account is bad,” without identifying the exact mismatch.
- Relying on undated or heavily cropped screenshots that do not show what page or condition they capture.
- Mixing confirmed observations with guesses about the seller’s intent or the platform’s reason for a notice.
- Writing in anger, sending repeated messages, or making threats instead of stating the evidence and requested remedy.
- Moving the conversation away from the marketplace and losing a clear record of what was said.
- Sharing credentials or unnecessary personal information to support the complaint.
- Continuing to change or test the account in ways that could alter its condition or conflict with platform guidance.
A strong claim is not necessarily a long one. It is a consistent record linking the offer, the delivery, the observed problem, the time it was discovered, and a reasonable request. Preserve the evidence, communicate through a traceable channel, and follow the marketplace’s process. This approach helps keep the review grounded in the product that was offered and the condition that was actually delivered.