Perplexity Pro Quota Plummets to 10 Queries a Day: User's Complaints Met With Customer Support Silence

Perplexity Pro user sees premium quota crash to 10 queries a day, with support going silent.
A user who obtained Perplexity Pro through the Revolut Metal plan found their premium query quota slashed from the promised hundreds per day to just 10, with official support going silent after promising a 48-hour response. The case exposes AI subscription quota opacity, inference cost pressures, and the rights struggles of third-party channel users.
Article
Recently, a user who obtained a free Perplexity Pro subscription through the Revolut Metal plan aired a public grievance on Reddit: their premium query quota had been drastically slashed, dropping from the officially advertised "hundreds per day" to just 10 premium queries to the Claude Sonnet model. Even more frustrating, after seeking help from official support, the chatbot promised to escalate the matter to a human within 48 hours — only for the response to never materialize. This case reflects a deep-seated malaise in current AI subscription services when it comes to quota transparency and user support.
The Full Story: The Gap Between "Hundreds" and "10"
According to this user, their Perplexity Pro subscription came as a perk bundled with the Revolut Metal bank card plan. Revolut is a UK-headquartered fintech company founded in 2015 and one of Europe's most highly valued fintech unicorns, with a valuation of around $33 billion in 2023. Its Metal plan is a flagship banking card product aimed at high-net-worth users, with monthly fees ranging from roughly €13 to €45 (depending on region). Beyond AI subscriptions, it bundles perks such as airport lounge access, travel insurance, and cryptocurrency trading discounts — a classic "super app" ecosystem strategy.
In recent years, bundling perks between fintech companies and AI service providers has become an emerging user acquisition strategy. For AI companies, it allows rapid subscription growth by leveraging banks' massive user bases; for financial products, it's a differentiating factor to boost the appeal of premium plans. However, this B2B2C (Business-to-Business-to-Consumer) distribution model inherently suffers from blurred service tiers: AI providers typically supply subscriptions to financial institutions at wholesale prices, and since the marginal cost of AI services grows linearly with usage — unlike the fixed content cost of streaming — the "guaranteed usage" clauses in wholesale pricing agreements become especially critical. The end user's service agreement often falls into a gray area — neither a standard retail user nor an enterprise user — resulting in unclear accountability when problems arise.
During use, the system popped up a notice reading "Only 3 premium AI model uses left this week," while in reality the user could only make about 10 premium queries to the Claude Sonnet model per day.
This stands in stark contrast to the official messaging. Perplexity's support chatbot explicitly stated that "Pro subscribers can enjoy hundreds of Pro searches per day," yet the actual available quota had shrunk to single digits. The user put it bluntly: "They say you're supposed to get hundreds of Pro searches a day. It's obviously either a bug or an absurd money grab."
The Gray Zone of Official Quota Policy
Intriguingly, even Perplexity's own support chatbot couldn't provide an exact figure when pressed on specific quotas. Based on the bot's responses, the following key information can be pieced together:
How Premium Queries Are Counted
- Queries to "premium AI models" count toward the total Pro search quota;
- The default "Best" model doesn't consume Pro quota — only by actively switching to premium models like Claude or GPT does it consume premium query counts;
- Quota resets follow a rolling weekly basis, rather than resetting all at once at a fixed point in time.
It's worth noting that a "rolling weekly window" is far less user-friendly than it sounds. The Rolling Window is a metering mechanism originating from the field of data stream processing, widely used in API Rate Limiting scenarios. Compared to a Fixed Window, a rolling window can smooth out request loads more evenly, preventing users from bursting requests at reset time and overloading servers — which benefits the service provider. However, from a user experience standpoint, this mechanism introduces significant cognitive burden: users would need to track the precise timestamp of every premium query over the past 168 hours to predict when the next batch of quota will free up — a nearly impossible task. Unlike the familiar "reset at midnight," users can't precisely predict when the "next quota release" will happen, nor can they plan their usage clearly. More critically, from the user's perspective, "my quota was quietly cut" and "I used too much last week" are almost indistinguishable, which provides natural ambiguity for quota disputes.
Comparing Plan Quotas
The bot listed some publicly disclosed plan limits:
- Pro subscription: hundreds of Pro searches per day, but with a daily cap on premium models;
- Enterprise Pro: 400 Pro searches per week;
- Enterprise Max: 4,000 Pro searches per week;
- Max: unlimited Pro searches.
The bot admitted that "existing documentation does not provide a fixed number that can be cited as a guaranteed weekly quota, because limits may vary by subscription details and can change over time." In other words, even the official AI can't promise users exactly how many times they can use it per week — the opacity of quota policy is the very heart of this controversy.
The Deeper Problem: The "Invisible Downgrade" Phenomenon in AI Subscriptions
This case is not an isolated incident but a microcosm of structural problems in the AI subscription industry.
The "Black Box" of Quota Policy and the Hidden Pressure of Inference Costs
Many AI providers habitually use vague phrasing like "hundreds of times" or "ample usage" in their marketing, while reserving disclaimer language such as "limits may change at any time" in their terms of service. This practice makes it difficult for users to assess the real value before subscribing and lays the groundwork for subsequent "Silent Downgrades."
"Silent Downgrade" is a much-criticized practice in the SaaS industry: providers unilaterally lower promised service standards or feature permissions without clearly notifying users. In the traditional software industry, such behavior is often subject to consumer protection regulations. The EU's Digital Services Act (DSA), which came into full effect in 2023, primarily targets platform content governance and algorithmic transparency; the EU's Consumer Rights Directive requires merchants to notify consumers in advance of significant changes to contract terms, and in theory applies to quota reductions in AI subscriptions. The UK's Competition and Markets Authority (CMA) launched an investigation into the AI foundation model market in 2024, and the revised version of the US FTC's Negative Option Rule has strengthened disclosure requirements for changes to subscription services. However, enforcement of these regulations typically lags behind industry practice, and there is no clear precedent for characterizing emerging concepts like "quotas." The "limits may change at any time" clause remains a common legal shield for providers.
The business logic behind this also warrants attention: Claude Sonnet is a mid-to-high-end large language model launched by Anthropic, positioned at the balance point between capability and cost, supporting a 200K token context window and visual understanding, with reasoning capabilities approaching the flagship Opus model. Take Claude 3.5 Sonnet, for example: its API is priced at roughly $3 per million input tokens and $15 per million output tokens — far higher than base models, but about one-fifth the price of the flagship version. This cost structure creates dual pressure for Perplexity: on one hand, it needs the promise of "premium models available" to attract paying Pro users; on the other hand, as the user base grows, a small number of high-frequency "whale users" consume service resources disproportionate to their subscription fees. Every Claude query has a real compute bill ticking away behind it, forcing providers to tighten high-cost model quotas to control marginal costs.
The Rights Struggle of Third-Party Channel Subscriptions and the Systemic Limits of AI Support
What makes this case special is that the user obtained the subscription through the third-party channel Revolut, rather than paying Perplexity directly. Such "bundled giveaway" perks often rank low in service priority and support: when problems arise, users can neither get a direct response from Perplexity nor hold Revolut accountable for service quality, ultimately falling into the awkward no-man's-land where neither party takes responsibility.
Meanwhile, Perplexity's use of an AI bot to handle first-tier support requests exposes another layer of deep contradiction: an AI support system is essentially a conversational system fine-tuned on a large language model, with its knowledge derived from a static snapshot of training data and an internal knowledge base — not real-time database queries. This means that when pricing strategies change, there's a time lag between the support bot's "knowledge" and the actual situation. The more fundamental issue lies in system permission design: for security and privacy reasons, AI support typically can only access a limited view of the user's account and cannot access the complete backend usage statistics and rate-limiting rules. This leaves the bot unable to diagnose whether "this is a global downgrade or an individual account issue," able only to give generic answers that faithfully reflect the system's boundaries, such as "the documentation doesn't provide a fixed number." Combining AI support with real-time tool calls (Function Calling) to give it the ability to query account systems is the industry-recognized path forward, but it requires complex permission management and security auditing — many companies are still in the exploratory phase. The deeper problem is that the promise of "escalation to a human within 48 hours," absent an enforcement mechanism, can easily become meaningless during high-traffic periods. This reveals the common dilemma AI companies face as their own products scale: they tend to prioritize R&D resources while relegating Customer Success infrastructure to a secondary concern.
Practical Advice for AI Subscription Users
When facing similar situations, ordinary users can take the following steps to protect their rights:
- Preserve evidence: Screenshot quota notices, support conversations, and promised response times to keep records for future appeals;
- Allocate model usage wisely: Understand that the default "Best" model doesn't consume premium quota, and reserve premium models like Claude for complex tasks that genuinely require deep reasoning;
- Apply pressure through multiple channels: If official support doesn't respond, provide public feedback via social platforms like Reddit and X — this often draws more attention from vendors than ticket systems;
- Be cautious about bundled perks: AI subscriptions given away with other products should be treated as "bonus perks" rather than "stable services" — critical workflows shouldn't over-rely on them.
Conclusion
This Perplexity Pro quota dispute reminds us: as AI subscription services rapidly expand, quota transparency and user support quality are becoming important yardsticks for measuring a provider's integrity. When the official support bot can't explain the specific quota, and when the 48-hour response promise evaporates, it's not just an individual user's experience that suffers — it's the foundation of trust for the entire AI service industry. For providers, a clear, stable, and predictable quota policy earns far more lasting user trust than flashy marketing rhetoric.
Note: This article is based on public feedback from a single Reddit user. For specific quota policies, please refer to Perplexity's latest official terms.
Key Takeaways
Related articles

LLaMA-Factory in Practice: A Complete No-Code Guide to Fine-Tuning Large Models
An introduction to LLaMA-Factory, the open-source fine-tuning tool: its 60.1K-star background, supported models and algorithms, local vs. cloud deployment, and CUDA setup steps.

Zeng Ming's Deep Retrospective: Why OpenAI May Not Be the Ultimate Winner — and Why the Corporate System Will Disappear
Zeng Ming's deep retrospective on the AI endgame: model companies are just infrastructure, OpenAI and Anthropic won't be the final winners; the next battle is the Agent entry point standard; the corporate system will disappear as AI restructures collaboration, and only mission-driven companies can survive the cycle.

OpenHands v1.28.0: OpenCode and PI Added as Built-in Agents, API Keys Requestable In-Conversation
OpenHands ships 5 releases in 21 days: v1.27.0 adds OpenCode and PI as built-in agents, v1.28.0 enables in-chat key requests. ACP integration, credential reuse, model list changes, and upgrade advice.