- Newest
- Most votes
- Most comments
I understand your frustration with the unassigned billing support case regarding the unexpected QuickSight charge. Here's what I can advise:
For billing support cases, AWS Support typically responds based on your support plan tier. If you have a Basic Support plan (the default free tier), billing and account support cases are handled through AWS Support Center, but response times can vary. Developer, Business, and Enterprise Support plans have faster response times with defined SLAs.
To help move your case forward:
- Check your Support Center - Log into the AWS Support Center to verify the case status and ensure all required information was provided
- Avoid duplicate cases - Multiple cases on the same issue can sometimes cause delays rather than expedite resolution
- Consider upgrading temporarily - If you need faster response times, you might consider temporarily upgrading your support plan, though this comes with its own costs
Regarding refund requests: AWS does evaluate requests for courtesy adjustments on a case-by-case basis, particularly for situations like accidental charges from forgotten trial expirations. However, these decisions are made by the billing support team and aren't guaranteed.
Since your cases have been open for 7 and 3 days respectively, I'd recommend being patient for a bit longer while avoiding creating additional duplicate cases. The billing team will review your request when they reach your case in the queue. Make sure you've clearly documented that the service wasn't used and was deleted immediately upon discovery of the charge.
Unfortunately, I cannot directly escalate cases or provide specific timeframes, as case handling is managed by AWS Support teams based on your support plan level.
Hi there.
I located your case and shared your feedback internally.
If you have additional questions, respond to your case, as we cannot share case details through this platform.
— Roman Z.
Relevant content
- asked 3 months ago
- asked 3 months ago
- asked a month ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 3 years ago
