Security

A consumer complaint file: dates, numbers and screenshots

A complaint that is clear, dated and backed by evidence gets answered. A single file, started on the day of the problem, supplies all three.

Editorial illustration for A consumer complaint file: dates, numbers and screenshots

Why a file helps

When a purchase goes wrong, you end up with many pieces of information scattered across emails, chats, calls, photos and statements. If the matter drags on, you may have to repeat the story to different people. A single file lets you give the facts quickly, consistently and with proof.

What the file holds

Start a folder or note for each complaint, named by seller and date. Inside, keep:

  • A one-paragraph summary of what happened.
  • A timeline with dates.
  • The order confirmation and payment proof.
  • Screenshots of listings and policies at the time.
  • Photos of the item or damage.
  • A log of every contact: date, method, person, reference, outcome.
  • The remedy you asked for.

Add to it as the case develops.

Write the timeline

A short list of dates and events is the backbone. For example: ordered on the 3rd, delivered on the 9th, defect noticed on the 9th, seller contacted on the 10th, no reply by the 15th. Keep it factual. Avoid opinion and blame. A neutral timeline is easier for others to act on.

Keep a contact log

Each time you speak or write to someone, note it. A phone call without a note is a call nobody can verify. Where possible, follow up calls with a short message summarising what was said, so that there is a written record.

Use plain language

When you write the complaint, state the facts, the problem and the outcome you want. Quote the order number. Attach the evidence. Say what you will do if there is no answer by a certain date, such as raising it with your bank or an official complaint body. Avoid threats and strong language. Clarity wins.

Protect your information

Share only what is necessary. Do not send full card numbers, PINs or passwords. When attaching statements, hide unrelated transactions. Be careful with messages that claim to be from a seller or helpline and ask for payment or codes; contact them through the official channels you find yourself.

An example entry

A sample log line: 12 October, phone call, spoke to support agent, reference 4821, promised callback within two days. Next line: 15 October, no callback, sent email with order number and timeline. Short lines like these, kept over a few weeks, show a pattern of delay or avoidance that a single complaint cannot. They also help you stay calm, since the record shows you have acted reasonably.

Know what outcome you want

Before writing, decide what would settle the matter: a refund, a replacement, a repair, an apology or a correction. State it plainly. A vague complaint invites a vague reply. A clear request gives the seller something to agree to. If you would accept two outcomes, say so. Being specific shortens the conversation and makes it likelier that both sides leave satisfied.

Staying safe while you complain

Be careful with the details you share. Do not send passwords, PINs or one-time codes. Be wary of people who contact you offering to recover your money for a fee or asking for remote access to your phone. Use only the official contact details for a seller or bank, which you find yourself. A genuine resolution never requires you to hand over access to your accounts.

Close the file properly

When the matter is resolved, record the outcome and the date. Keep the file for a sensible period in case it reopens. Then note any lessons: the seller’s behaviour, the clues you missed, the habits that helped. These notes feed into future choices about where you shop. A clean file closes the case and starts the next purchase on firmer ground.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports