#billing

auapwllc help me for this frustration

Amy Egan Hey Greg. The support team let me know they've been in contact through your support case. Please follow up with them if you have any more questions so they can help

Amy Egan Hey @jennie369. It looks like you've been working with a support engineer on your case. Please continue to follow up with them to get this solved 🙏

Jenniec Hi Amy, thanks for checking in. I have been working with the support engineer, but the case isn’t resolved. They closed it with a 25% goodwill refund ($134.64) and said that’s the maximum. $489.52 is still unrefunded. The issue is consent. My projects were explicitly set to fixed Basic/Standard machines, and the system overwrote that choice the minute I upgraded (isSystemInitiated: true, “because your team’s plan changed”). The upgrade screen said nothing about changing build machines or adding on-demand Build CPU charges. On Oct 3 it also auto-upgraded yinyang-web to 8 CPUs without asking. At best, the changelog wording (“default for new Pro teams” vs. “enable in your team settings”) is ambiguous about upgraded teams. An ambiguous term shouldn’t override a setting I chose explicitly. Budget emails that report usage “already incurred” aren’t consent to a machine I never selected. Could someone on the billing side please take another look at case CSE_01RxdvwtOfqTrLfo? I’d like the remaining $489.52 for the unauthorized Elastic overage refunded. Happy to share details privately.

Amy Egan Hey @paulmain79. Do you have a support case open? The community isn't able to issue refunds. That kind of thing is limited to the support team. If you don't have a case yet, please open one at vercel.com/help so the support team can assist!

Amy Egan Please open a case at vercel.com/help so the support team can help 🙏

Amy Egan Hey @scottgriffinm-5994. New Pro and Enterprise accounts use Elastic machines by default. They auto-scale based on your recent build durations, so some projects can end up on Turbo if their builds are very demanding. You can switch to a fixed build machine option in settings for your project or whole team. And the support team should be able to offer some help with the bill if you ask at vercel.com/help

Bostonsqelll 8232 Still unresolved — the team is showing "Overdue" with a shutdown warning. @amyegan, would you be able to route this to billing like the case above? Thank you!