Revel Roots

what apps actually cost

Complaining Effectively

Most subscription complaints fail for the same reason: they describe an experience when they should state a fact and make a request.

The version that works is shorter than the version that does not, and it takes about four minutes to write. In the workplace-software market, learn more provides a contrasting example for examining how monitoring features, defaults, and disclosure are presented.

The structure

Five lines, in this order.

What happened, with dates. I cancelled on 3 June. I was charged $14.99 on 8 June. For wider consumer-protection and interface-design context, Consumer Reports provides an outside reference point.

The evidence, attached. Screenshot of the confirmation, or the confirmation email.

What you want. Please refund the charge. One request, stated plainly.

A deadline. Please confirm within seven days.

And what you will do otherwise. Otherwise I will raise a chargeback with my card issuer. Not a threat — a statement of the next ordinary step.

That is the whole message. No history of the relationship, no description of how it felt, no rhetorical questions.

Why short works

It is actionable by the person reading it. A support agent has a limited set of things they can do. A message that names one of them can be resolved; a message describing frustration has to be interpreted first.

It is cheaper to grant than to argue with. A documented refund request costs less to process than a dispute, and the person reading it knows that.

And it is escalation-ready. If it goes to a chargeback or a regulator, you forward the same message and its evidence rather than reconstructing the case.

Where to send it

In writing, to a channel that keeps a record. Email or a support ticket. Not a phone call, and not a chat that disappears when the window closes.

If the only route is chat, screenshot it and ask for email confirmation of whatever was agreed.

And keep it to one channel. Complaints raised in three places simultaneously get merged, delayed, or answered by whoever is fastest rather than by whoever can resolve it.

The escalation order

One. The company, as above. A week.

Two. The platform, if bought through an app store. Both major stores have a refund process, and it is frequently faster than the developer.

Three. The card issuer. A chargeback with documentation is straightforward. Do this after contacting the merchant, because issuers ask.

Four. A regulator. In the US the FTC's consumer reporting site; the specific cancellation rule was vacated in July 2025 and enforcement under general authority continues, so complaints still inform priorities. State attorneys general handle automatic-renewal statutes, which in several states are stricter.

Five. Public. A factual, dated post. It works occasionally and it is the last step rather than the first, because it forecloses the quiet resolution.

What weakens a complaint

Anger. It makes the message longer and the request harder to find.

Multiple grievances at once. One request per message. A refund request plus a complaint about the interface plus a question about the roadmap will be answered on the easiest of the three.

Vague dates. "A few weeks ago" cannot be checked against a record.

And no evidence. Which is why the screenshot habit matters more than any of this.

The template

Subject: Refund request — charge of $14.99 on 8 June

I cancelled my subscription on 3 June (confirmation attached).
I was charged $14.99 on 8 June.

Please refund this charge and confirm within seven days.
Otherwise I will raise a chargeback with my card issuer.

Account: [email]

Four lines and an attachment. It works considerably more often than people expect, because it is easier to grant than to refuse.

The short version