|
|
|
|
|
by greg-m
5 days ago
|
|
Hey there - I partially disagree! We issue an invoice because the customer did consume the services - a lot of folks appreciate that, since it gives their AP team a real cost to work from instead of a ballpark of us vs. GitHub. My "we never pursue these" comment wasn't about us knowing the charge was shady - it was to clarify we have no strategy of chasing people/litigating over invoices they weren't aware of, which came up a bunch in the thread. I do agree that pushing surprised customers through a support ticket is wrong, and that our in-product language compounded that issue. Controlling this belongs in the product so we can hit the mark on trust - we're building that now. This isn't shady for most folks, since they're typically comparing us to known, expensive alternative. For those who are surprised by their spend (which given GHA's upper-bound pricing has been a minority) our reconciliation flow was for them to contact support, and my comment was to clarify that we don't have an intentional strategy to pursue folks for invoices they weren't aware of. It's clear to me that controlling this behavior belongs in the product so we can hit the mark on trust - we're working on adding that now. |
|
Invoices are legally binding documents in many countries, and even if that might not be the case in your country, not everyone might be aware of that fact.
> since it gives their AP team a real cost to work from instead of a ballpark of us vs. GitHub
Same could be achieved by showing the real cost in the web app and/or sending a report via email, without scaring them away, and possibly _extorting_ them.