Start with the right question
Start with a one-paragraph description of the problem and the transaction involved. Identify the business and product accurately, then explain the unresolved issue. A clear complaint is easier to route than a large folder of unexplained screenshots, but the supporting records should remain available.
Work through the checks
Define the unresolved issue
Describe the promised item or service, what occurred, and the specific mismatch. Separate several problems into numbered points. Avoid adding unrelated allegations that make it harder to understand the transaction you want reviewed.
Connect facts to documents
Attach or reference the relevant receipt, agreement, correspondence, and payment record. Label each document with its purpose. Use copies with unnecessary private details removed, while retaining complete originals locally.
State a concrete request
Explain the action you are asking for, such as an explanation, repair review, correction, or refund of a stated transaction. Do not describe a requested amount as already owed unless that conclusion is established through an appropriate process.
Track the response and result
Record the submission reference, response, promised action, and whether that action actually occurred. An acknowledgement or a 'resolved' portal label is not proof that a credit reached your account. Check the outcome before closing your file.
A record you can use
- Business, transaction, date, and reference.
- Problem statement with supporting document identifiers.
- Earlier contact attempts and responses.
- Specific requested resolution and reasons.
- Submission reference, promised action, and verified result.
Keep this record locally. Use document references rather than publishing account numbers or other people's personal details. An empty field means the information is still missing; it should not be filled with an AI guess.
Worked example
A customer requests a refund for an undelivered replacement part. The business responds that a credit was issued. The record retains the response but keeps the outcome open until the payment statement shows the credit. If the amount differs, the follow-up identifies that difference rather than submitting the entire original complaint again without explanation.
This example is fictional and illustrates the method, not a real case result.
Limits and next steps
Complaint systems have different scopes and do not all decide legal liability or provide individual representation. A complaint does not necessarily pause a court, contract, or payment-dispute deadline.
Use the business's verified channel first where appropriate, then identify a relevant regulator or dispute route. The CFPB handles eligible financial-product complaints; it is not a general forum for every retail dispute.
Official guidance to check
- FTC guidance on solving problems with businesses
- CFPB complaint process — for eligible consumer financial products and services