Writing a vendor complaint that gets results

The difference between a complaint that gets resolved quickly and one that goes in circles is almost entirely in how it's written. Here's what works based on my own experience and watching how vendors respond to others on forums.

The structure that works

Three parts: what happened, what you expected, what you want. That's it. Everything else is noise that dilutes the core message and makes it easier for support to deflect.

What happened: Order #XXXX placed on [date]. Received on [date]. Card has [specific issue — not "wrong card," but "the expiration date reads 2031 but the correct expiration for the information I provided should be 2029 based on your stated rules"].

What you expected: Based on your listed product description and the proof I approved on [date], the card should have [correct element]. I've attached the approved proof screenshot and a photo of the received card for comparison.

What you want: A replacement with the correct expiration date, shipped using [same or expedited] shipping to [same address].

What to leave out

Emotion and backstory. How frustrated you are, how long you've been a customer, what you paid — all of this slows down the resolution without helping it. The vendor's support team needs to understand the problem and the solution, not your feelings about it.

Threats belong in escalation messages after you've tried the direct approach twice. Leading with "I'll file a dispute" eliminates the vendor's incentive to cooperate voluntarily, which is usually faster than any formal dispute process.

Response time expectations

A well-written complaint with documentation usually gets an acknowledgment within 24-48 hours. Resolution — either a replacement confirmed or a clear explanation — typically follows within another 48 hours. Total: 4 days is a reasonable expectation for an unambiguous production error. Anything faster is a bonus; anything longer warrants a single follow-up message.