Support case id: *************** unassigned for - $193 refund request for unused QuickSight/Amazon Q charges

Two things likely caused this, both documented by AWS.

First, closing your AWS account does not automatically cancel a QuickSight subscription. You have to explicitly delete it via Manage QuickSight first. If that step was skipped, the subscription was still active when the account closed, and AWS bills pre-closure usage at the start of the following month.

Second, QuickSight cancellations are not prorated. AWS's stated policy is that cancellations apply starting the next calendar month, so if you cancelled mid-month, you owe the full month regardless.

The $193 is likely a mix of per-user charges plus possibly the $250/month infrastructure fee that triggers automatically whenever a Pro user or Q Topics is enabled. That fee catches a lot of people off guard.

The KC article covering post-closure billing is here: https://repost.aws/knowledge-center/closed-account-bill. The proration policy is documented on the QuickSight pricing page: https://aws.amazon.com/quick/quicksight/pricing/

For your support case, the most important thing is pulling the exact line items from the Billing Console (Bills page, filter by month and service) before you write to AWS billing. A vague "I got charged after closing my account" request goes nowhere. A message that says "line item X for Y usage type on date Z, policy states cancellation was effective on date W" gets taken seriously.

Quick question before I dig in further: did you go through Manage QuickSight and explicitly delete the account/subscription there before closing the parent AWS account, or did you close the AWS account directly? That one answer changes whether you have a refund argument or not.

I'll take a look at the specific line items with you and put together a short written breakdown of which charges are refundable and a draft message you can paste into your support case. No charge for this given the amount in dispute. Reply here or DM me.

I understand your frustration with unexpected charges and waiting for a response on your support case. Let me address your situation:

Regarding your support case, AWS Support cases are typically assigned and responded to based on your AWS Support plan level. Response times vary by plan - Basic Support provides account and billing support during business hours, while Developer, Business, and Enterprise Support plans offer faster response times and 24/7 availability for technical issues. You can check your current support plan and consider upgrading if you need faster responses for future issues.

For your specific billing concern about QuickSight and Amazon Q charges, it's important to understand that simply destroying or deleting resources may not immediately stop all charges. Some AWS services have specific cancellation or unsubscription processes. For QuickSight specifically, you need to unsubscribe from the service through the QuickSight console, not just delete dashboards or analyses. Similarly, Amazon Q may have its own subscription management requirements.

To address your immediate concern, I recommend adding detailed correspondence to your existing case through the AWS Support Center at https://console.aws.amazon.com/support/. Include information about when you created the resources, when you attempted to delete them, and the specific steps you took. This will help the support team investigate your billing issue more efficiently.

For billing disputes and refund requests, AWS Support will review your usage patterns and account activity. They can help identify if charges continued due to resources that weren't fully terminated or subscriptions that remained active. The support team has the tools to investigate your specific situation and determine what resolution may be appropriate.

You can also review your detailed billing information in the AWS Billing Console to see exactly which services are generating charges and verify that all resources have been properly terminated.

Hi there.

I apologize for the inconvenience caused by the unexpected charges on your account after attending the Amazon Summit.

Your case is with the correct team and your sentiments have been shared internally. Correspondence will be shared via our Support Center once the review is complete: http://go.aws/support-center.

— Roman Z.