A billing dispute is not the same as a product complaint. Nobody broke a promise about quality, a system charged you the wrong amount, charged you twice, kept billing after a cancellation, or added a fee nobody mentioned. The fastest way to get it fixed is to write it like a lookup request, not a grievance: give the billing team exactly what they need to find the transaction and act on it.
Lead with the charge, not the feeling
The first line should be the exact amount and the date it was charged. Whoever reads this message is going to search a system for a transaction, and a specific figure and date lets them find it in seconds. “I was charged incorrectly” sends them hunting through months of history and makes your message easy to set aside for later.
Say specifically why it is wrong
“This does not seem right” invites a form reply. “I cancelled this subscription on February 14th and have the confirmation email, so the March 3rd charge should not have happened” invites a refund. Name the exact kind of error: a wrong amount, a duplicate charge, a charge after cancellation, an undisclosed fee, or a meter reading that does not match actual use. Whatever facts you have, an account number, a confirmation email, a previous bill to compare against, mention them.
Ask for one thing, and name a deadline
State the exact correction you want once: a refund of a specific amount, a full reversal, a credit, or a corrected reading. Then add real leverage most people leave out: say plainly that you will dispute the charge with your bank or card provider if it is not resolved within a set window, around 14 days is reasonable. This is not a threat, it is simply true, and it is often the line that gets a slow queue moved to the top.
Common mistakes
- Leading with frustration instead of the amount and date, which slows down the lookup.
- Saying a charge “seems wrong” instead of stating specifically what should have happened.
- Asking for something vague, like “please look into this,” instead of one exact correction.
- Leaving out the escalation deadline, which is the one line that gets things actually moving.