If you’re building production bots on Anthropic’s infrastructure, you need to know that their support might ghost you for over a month on billing issues.
I’m not talking about a complex technical problem or an edge case bug. I’m talking about money—specifically, about $180 in unexpected charges that appeared on my Anthropic account in early March. Today is April 9th, 2026. I’m still waiting for a response.
What Actually Happened
Between March 3rd and 5th, my account got hit with charges I wasn’t expecting. I’m a Claude Max subscriber, so I already have a billing relationship with Anthropic. This wasn’t about understanding the pricing model or questioning legitimate usage. These were charges that didn’t match my activity.
I did what any reasonable developer would do: I contacted support. Then I waited. And waited. Over a month later, radio silence.
Why This Matters for Bot Builders
When you’re building bots for clients or running your own AI-powered services, billing predictability isn’t a nice-to-have—it’s fundamental. You need to know what you’re paying for, and when something goes wrong, you need answers fast.
Here’s the reality: if you’re running a bot that serves customers, unexpected charges can cascade. You might be passing costs through to clients. You might be operating on tight margins. A $180 discrepancy might not sound like much, but multiply that across multiple projects or scale it up to enterprise usage, and you’re looking at real money with no explanation.
The bigger issue is trust. If I can’t get a response about billing, what happens when I have a critical API issue? What if my production bot goes down and I need urgent support? The silence on a straightforward billing question doesn’t inspire confidence.
The Timing Is Awkward
This is happening while Anthropic is pushing hard to position Claude as more than a chatbot. Their 2026 strategy focuses on turning Claude into a system that can complete real work—the kind of work that bot builders like us are already trying to do.
But you can’t build reliable automation on top of unreliable support. The technology might be solid, but if the business relationship breaks down over something as basic as billing communication, that’s a problem.
What I’m Doing About It
I’m documenting everything. Every support ticket, every follow-up, every day without a response. Not because I enjoy complaining, but because other developers need to know what they’re signing up for.
I’m also evaluating alternatives. When you’re building bots, you need a provider you can count on. That means responsive support, transparent billing, and clear communication. If Anthropic can’t deliver on those basics, there are other options.
A Message to Anthropic
I get it—you’re scaling fast, you’re dealing with massive demand, and support is hard. But a month of silence on a billing issue is unacceptable. This isn’t a feature request or a philosophical debate about AI safety. This is basic customer service.
If you want developers to build serious applications on your platform, you need to treat billing issues seriously. Respond to tickets. Acknowledge problems. Give timelines. Do the boring, unglamorous work of actually supporting your customers.
For Other Bot Builders
If you’re using Anthropic’s APIs, keep detailed records of your usage and charges. Set up alerts for unexpected billing. Have a backup plan. And maybe most importantly, factor support responsiveness into your vendor decisions.
The AI space moves fast, but good customer service is timeless. A provider that can’t handle a simple billing inquiry in over a month isn’t ready for your production workloads.
I’ll update this if Anthropic ever responds. But after 35 days and counting, I’m not holding my breath.
đź•’ Published: