Quota Increase rejected due to low account usage

Quota increase requests can be approved, denied, or partially approved by AWS Support, and this is a normal part of the process. However, the situation you're describing seems unusual. When requesting a quota increase, AWS typically evaluates the request based on the specific service and your usage patterns for that service, not necessarily your overall AWS account usage across unrelated services.

For quotas that start at 0 (like your Concurrent active calls for outbound campaigns), it's understandable that you wouldn't have existing usage to demonstrate, especially when you're trying to set up a proof of concept. The requirement to use 90% of a quota that's set to 0 creates a logical impossibility.

I'd recommend the following approaches:

1. Clarify the request: Reach out to AWS Support again and explain that this is for a POC and that the current quota of 0 makes it impossible to demonstrate usage. Ask if there's a minimum quota they can approve to allow you to begin testing.

2. Use the Service Quotas console: If you haven't already, try requesting the increase through the Service Quotas console directly rather than through a support case, as this is the recommended method for services available in Service Quotas.

3. Provide business justification: When making your request, include detailed information about your use case, expected usage patterns, and why you need the increase for your POC. This context can help support your case.

If you continue to face challenges, you might consider escalating within the support case or requesting clarification on the specific criteria being used to evaluate your request.
Sources
AWS service quotas - AWS General Reference
Requesting a quota increase - Service Quotas