Call your credit card company

You are right. The big company is wrong. The only thing between you and setting the record straight is a phone call that may take all day.

Recently I bought a new TV. In my most consumerist moment, I took them up on a deal that lets me pay over time without any interest. It’s a no-brainer, right?

Until my first statement had an interest charge.

I made a note to call the company. I ignored my own note. Another statement came, another interest charge. I’m more likely to pay off the full balance than make that call.

Plenty of customers do reach out in these situations. Maybe it’s not a billing issue, but a technical one. Your developer product gets these queries all the time.

On the other side of support requests may be frustrated developers. But more importantly for you, these are content ideas.

Developer problems are the key to great content. When you find the use case within a problem, you can show you understand it—and provide your product as one of many potential solutions.

If you have a developer relations team, they bump into these problems in all sorts of places:

• Support tickets
• Stack Overflow
• Twitter

I highlight these and other locations where you may already have your content in my latest blog post, Writing for Developer Relations.