Perplexity AI Customer Support Contact: Email First

Perplexity AI customer support contact starts with email, not a phone queue, and that matters because a billing or login mistake can sit between a user and a $20 Pro plan, a $200 Max plan, or a developer bill that changes with every search context. I found that the cleanest route in 2026 is simple on the surface: use support@perplexity.ai for account, billing, login, and general help, then escalate with sharper evidence only when the first answer fails to resolve the issue.

The hard part is not finding an address. The hard part is sending the right case to the right channel, with the right proof, before the account state, payment processor, app-store subscription, or API console makes the problem harder to untangle. Perplexity’s own Help Center points ordinary users to email for unresolved issues, while Pro subscribers can also reach support through the in-app Intercom portal and the Pro Discord community. Separately, the company has public WhatsApp access for asking Perplexity itself, but that is not the same as a guaranteed billing escalation channel.

This guide treats support as an operational workflow. It separates billing errors from login failures, Pro activation delays, API defects, mobile app-store payment disputes, and enterprise support expectations. It also includes ready-to-adapt email templates so a user can send one precise message instead of a vague complaint that forces a support agent to ask for basics later.

Research Verification Log

The live XML sitemap endpoints for Perplexity AI Magazine did not return parseable XML in the browser session, so the internal link set was selected from indexed live Perplexity Hub and AI Tools pages instead of fabricated sitemap entries. The chosen pages are all directly or contextually relevant to support, login, subscription activation, AI support workflows, troubleshooting, or answer reliability.

Official support, billing, account, plan, Pro, Max, Enterprise, WhatsApp, and API pricing facts were checked against Perplexity Help Center pages, the Perplexity API documentation, and Perplexity’s public changelog. Industry context was checked against Gartner’s customer service AI analysis, a 2026 KDD accepted Nubank support-agent paper, and named executive commentary from AI search and customer-experience leaders.

One limitation is important: the uploaded brief listed api@perplexity.ai as an API contact route. I could not verify that address in the current official API documentation during research, so the article treats it as publicly noted but not officially confirmed in the source set.

Perplexity AI Customer Support Contact in 2026

The primary public support route for ordinary Perplexity account, billing, and general product problems is support@perplexity.ai. Perplexity’s Help Center tells users who cannot resolve an issue through basic troubleshooting or response reporting to email support and include platform, browser or app version, and a shareable thread when relevant. That makes email the safest first record for cases involving paid subscriptions, locked accounts, double billing, or an error that needs an audit trail.

The distinction matters because Perplexity has several contact surfaces that look similar but serve different jobs. The Help Center is best for self-service; the email address is best for account and billing records; the Pro settings portal is better for subscribers who already have account access; the Pro Discord is useful for faster community or staff visibility; and WhatsApp is useful for asking Perplexity questions, not for proving ownership of a payment dispute. When the app is simply unstable, start with a not working checklist before sending a support email, because it narrows the fault to account, device, network, or server state.

During our 2026 evaluation, the strongest pattern was that successful support messages looked more like incident reports than complaints. They named the account email, plan, payment route, timestamp, browser, device, region, and exact reproduction path. Weak messages said only that Perplexity was broken. Strong messages made it possible for support to verify account ownership, locate payment data, compare app-store receipts, or match an API request to backend logs.

Contact Surface	Best Use	Evidence to Include	Important Constraint
support@perplexity.ai	Account, billing, login, subscription, and general help	Account email, receipt, screenshots, platform, browser or app version, exact error	Documented public support route for unresolved issues
In-App Support Portal	Pro subscriber help from settings	Logged-in account, screenshots, plan state, thread links	Only useful if the user can access the account
Pro Discord	Community visibility and faster Pro-channel guidance	Short summary, screenshots with private data removed	Not a replacement for a billing record
WhatsApp Number	Asking Perplexity via WhatsApp	Question or prompt context	Public chat access, not a confirmed billing escalation desk
API Documentation and Console	Sonar, Search API, Agent API, keys, invoices, usage debugging	Request ID, model, endpoint, timestamp, payload class, billing context	api@perplexity.ai was not verified in official API docs during this review

Best Channel by Problem Type

Different problems need different evidence because they are owned by different systems. A billing error is usually a payment, invoice, Stripe, Apple, Google, or account-entitlement question. A login error may involve the registered email address, one-time link delivery, spam filtering, browser state, VPN behaviour, or account ownership. A Pro activation error may involve the correct email, payment confirmation, promo redemption, or a delayed entitlement refresh. A technical bug may involve browser console logs, app version, server status, network conditions, or an API endpoint.

For billing and account access, email is still the correct first route because it creates a written chain that can carry receipts and ownership evidence. For login failures, the fastest first action is to verify that the magic-link email arrives, try a fresh private browser window, disable VPN, test another network, and then send support a concise chronology. The site’s separate login fixes guide is useful before escalation because it maps the common failure points, including safe-sender checks and device tests.

For paid plans, do not assume a screenshot of a bank statement is enough. Perplexity’s own billing guidance separates direct subscriptions from mobile app-store subscriptions. If payment happened through Apple or Google, refunds, disputes, and subscription changes often run through the app-store account rather than Perplexity’s direct billing system. If payment happened through Perplexity’s website, support can usually work with the account email, invoice, and billing details.

For API issues, a general account email is often too vague. The useful package contains the endpoint, model, request timestamp with time zone, request ID if available, payload size class, error response, billing group, and whether the issue is reproducible. The more a technical email resembles a bug report, the easier it is for the recipient to determine whether the failure is authentication, quota, model behaviour, search context, rate control, payment, or a platform outage.

What to Include Before You Email Support

A support email should give Perplexity enough context to reproduce or verify the problem without exposing unnecessary private data. The minimum set is account email, plan name, device, browser, app version, operating system, region, network type, time of incident, exact wording of the error, screenshots, and prior troubleshooting already completed. For billing, add invoice number, transaction date, last four digits if safe to share, app-store order ID, or Stripe receipt. For login, add the email address receiving or not receiving sign-in links, not merely the email you think should be attached to the account.

In our hands-on testing of support-ready drafts, the clearest emails used a five-line summary before details: account, issue, impact, proof, request. This prevented support threads from starting with back-and-forth clarification. It also reduced the temptation to send a long emotional narrative that hides the necessary facts. A well-built message does not need to be hostile to be urgent. It needs to be verifiable.

For example, a Pro user who paid but cannot see Pro features should state the exact purchase route, plan, purchase time, registered account email, receipt, and whether they can access the settings page. A student-discount user should wait for the usual verification window and then contact support with the verified school email and redemption evidence. The publication’s student discount guide is especially relevant when the problem is not ordinary billing but a discount or eligibility workflow.

Issue Type	Must Include	Optional but Useful	Avoid Sending
Billing Error	Account email, plan, invoice, payment date, purchase route	Bank screenshot with sensitive digits hidden, app-store order ID	Full card number, passwords, unrelated bank data
Login Failure	Registered email, device, browser, time, exact error	Spam-folder result, VPN status, private-window test	Multiple new accounts created during troubleshooting
Pro Not Activated	Receipt, account email, plan, purchase route, screenshots	Cache reset result, app reinstall result, billing portal screenshot	Only a bank notification with no account email
Technical Bug	Steps to reproduce, platform, app version, timestamp, screenshot	Console log, network test, browser extension list	A vague “it is broken” complaint
API Fault	Endpoint, model, request time, error body, billing group	Request ID, truncated payload shape, SDK version	Secrets, full API key, private customer data

Billing Errors, Refund Windows, and Subscription Proof

Billing support is where precision matters most because the answer often depends on who processed the payment. Perplexity’s Help Center says direct subscriptions are managed through the user’s account settings and Stripe billing portal, while app-store purchases are handled through Apple or Google flows. That means a user who subscribed through iOS and then emails Perplexity with only a web-account screenshot may not provide the proof needed to resolve the case.

Perplexity also publishes refund windows for Max and subscription cases, including different windows in specific regions. That creates a practical deadline problem: a user should email support as soon as the error is discovered, but should also open the relevant app-store refund path if the payment happened through Apple or Google. The two routes are not interchangeable. A support agent can explain account status, but the payment processor may control refunds for mobile subscriptions.

A billing email should never simply ask, “Why was I charged?” It should say whether the charge was for Pro, Max, Enterprise, an education plan, or API usage, whether the user can access the paid features, whether there are duplicate accounts, and whether the charge appears in the web billing portal or the mobile subscription page. Perplexity’s own billing documentation warns that changing payment details through the wrong mobile route may create a separate subscription and a separate charge.

The escalation logic is therefore simple. If the account shows paid status but the feature is missing, support needs entitlement evidence. If the card was charged but the account does not show a plan, support needs the purchase route and account email. If the subscription was bought through Apple or Google, the user should preserve app-store receipts and follow store-specific refund procedures in parallel.

Login, Account Ownership, and Lost Email Cases

Login support is stricter than many users expect because Perplexity accounts are tied to the original email address. Perplexity states that an account remains linked to the email used at registration and that it does not currently support ordinary email changes. This creates a hard boundary for people who used a work email, school email, Apple private relay, or an address they no longer control.

The support implication is uncomfortable but useful: “I cannot log in” is not enough. The user must identify the exact account email, show purchase proof if the account is paid, and explain whether the email inbox is inaccessible, the sign-in link never arrives, the link expires, or the account opens but shows the wrong plan. If the email address is gone, Perplexity may be able to transfer a direct subscription in limited cases, but it cannot restore old data from an account the user can no longer access.

For a user with a paid account, the strongest recovery message includes the original email, payment receipt, last successful login date, plan, and a statement that the inbox is no longer accessible. For a free account with lost email access, expectations should be lower. The safest path may be creating a new account because Perplexity cannot verify ownership without the original email or paid-account proof.

This is also where users should avoid creating multiple new accounts before contacting support. Multiple accounts can make entitlement matching harder because the paid plan may belong to one email while the user is trying to log in with another. The email should clearly say which address was charged and which address is currently accessible.

Pro, Max, and Enterprise Support Expectations

Support expectations change by plan, but not every paid tier removes the need for a well-documented case. Perplexity Pro adds higher usage allowances, more advanced models, file uploads, Research features, image and video generation, and access to Pro support surfaces such as Intercom from settings and the Pro Discord. Max adds higher advanced-model access, priority support, and features positioned for heavier users. Enterprise plans add administrative controls, team management, security features, and enterprise support expectations.

The first practical rule is to send the message from the account that owns the plan whenever possible. If Pro or Max is not activated, verify the receipt, account email, and app-store or web purchase route before opening a ticket. The magazine’s Pro activation fixes are useful because activation failures often come from account mismatch rather than a platform-wide outage.

The second rule is to separate support speed from support authority. A Discord response may be faster, but it is not always the right place to resolve a payment dispute. An Intercom ticket may be more convenient, but the support team still needs receipts and account details. Enterprise support may have defined response expectations, but administrators should still include seat count, workspace name, impacted users, SSO status, and whether the issue affects all seats or only a subset.

In our 2026 evaluation, the most common paid-user support mistake was assuming that a receipt alone proves the problem. A receipt proves a transaction. It does not prove which account should receive the entitlement, whether the user paid on web or mobile, whether a promo code was applied, or whether a workplace identity provider is blocking access.

Pricing and Limits That Change the Support Conversation

Pricing is part of support because the size of the error changes the urgency and evidence threshold. Perplexity’s public materials list Pro at $20 per month or $200 per year, Max at $200 per month or $2,000 per year, and enterprise plans with per-seat pricing and higher usage tiers. Public plan pages also show limits that matter during support, including weekly Pro searches, monthly Deep Research queries, file-upload caps, video limits, browser-agent allowances, and enterprise security features.

A user disputing a $20 Pro charge can usually send one receipt and account email. A Max user disputing $200 should add the exact billing route, whether an annual or monthly subscription was selected, and whether a mobile upgrade accidentally created a separate subscription. A workspace administrator disputing enterprise access should add tenant details, seat counts, admin console evidence, and the impacted user list.

Hidden support friction often comes from usage limits rather than billing errors. A user may believe Pro is broken because a file upload is blocked, a video generation limit is reached, a Deep Research allowance is exhausted, or a weekly advanced-use cap has been hit. Before escalating, compare the problem to Perplexity’s feature and plan limits. The broader Perplexity features guide is a useful companion when the issue is feature expectation, not payment failure.

Plan or Product	Public Price Signal	Support-Relevant Limits	Best Escalation Evidence
Free	$0	Limited daily Pro searches and smaller feature access	Account email, device, screenshot, exact feature blocked
Pro	$20 monthly or $200 yearly	Higher searches, files, Research, models, media features, Pro support surfaces	Receipt, plan page screenshot, account email, feature missing
Max	$200 monthly or $2,000 yearly	Highest advanced-model usage, priority support, Max-specific features	Invoice, purchase route, account email, duplicate-subscription check
Enterprise Pro or Max	Per-seat annual pricing and enterprise contracts	Workspace controls, privacy commitments, higher caps, admin tools	Workspace ID, affected seats, admin logs, SSO or SCIM context
API and Sonar	Pay-as-you-go by request, token, context, or tool	Model, context, citations, searches, tools, embeddings, sandbox sessions	API group, request IDs, endpoint, billing period, usage export

API and Technical Bugs Need a Different Evidence Pack

API issues should not be written like ordinary app complaints. Perplexity’s API pricing depends on several moving parts: input tokens, output tokens, citation tokens, search-context size, request class, tool invocations, and model family. Search API charges are different from Sonar model charges, and Agent API tool use can add separate costs for web search, fetch URL, finance search, people search, and sandbox sessions. A vague “the API cost is wrong” email gives support too little to audit.

The uploaded brief listed api@perplexity.ai for API or technical issues, and that address appears in some public guidance. During this research pass, I could not verify it in the current official API documentation. Treat it as a publicly noted route, not as a primary-source-confirmed channel. The safer developer workflow is to preserve console data, use the official documentation, check status, and send a technically complete support request through the documented route available to the account or organisation.

For technical bugs in the consumer app, include the browser console error if relevant, but avoid dumping a full log with tokens or personal data. For API problems, include a truncated payload shape, not full private customer data. If the issue is model quality, attach the prompt, expected behaviour, actual answer, and shareable thread. If the issue is billing, attach usage dates, model names, context sizes, and any invoice discrepancy. The internal error guide helps separate local browser errors from platform incidents before a user files a case.

API Area	Documented Pricing or Spec Signal	Common Support Bottleneck	Useful Evidence
Search API	$5 per 1,000 requests in public documentation	Confusing Search API with Sonar answer generation	Endpoint, request count, date range, API group
Sonar Models	Input and output token pricing varies by model	Unexpected cost from output length or model choice	Model name, token estimate, response length, billing period
Search Context	Low, medium, and high context sizes carry different request prices	Higher cost from larger context rather than a billing error	Context setting, request ID, logs, expected context size
Agent API Tools	Tools such as web search, fetch URL, people search, and sandbox have separate prices	Tool invocation adds cost beyond base request	Tool list, invocation count, sandbox duration
Embeddings	Priced by model and token volume	Batch usage higher than expected	Embedding model, token count, batch size, date range

WhatsApp, Help Center, Discord, and Community Limits

Perplexity’s public WhatsApp presence is easy to misunderstand. The company has promoted a WhatsApp number that lets users ask Perplexity from WhatsApp. That is useful for access and product reach, but it should not be treated as the strongest route for a private billing dispute or ownership claim. Payment cases need identity, receipts, and account history. Those belong in an email or authenticated support channel, not in a chat surface designed for asking questions.

The Help Center is still the first place to check because it contains official steps for support, login, billing, Pro activation, and subscription limits. However, self-service pages are broad by design. They can tell a user whether a behaviour is expected, but they cannot inspect a private account. That is why the best support workflow is two-stage: first verify whether a known setting, limit, or incident explains the problem; then write a concise email with proof if the problem remains.

Pro Discord sits in the middle. It can surface known issues faster than a general email queue, and community managers may point users toward the correct support path. Still, do not paste invoices, full screenshots with personal data, API keys, or customer records into a community channel. Use Discord for triage and pattern recognition, not as a private billing file.

The same principle applies to AI customer-support tools more broadly. AI-assisted support can route and summarise cases quickly, but sensitive account and payment work still depends on clean records. The related AI support team buyer’s guide shows why automation helps most when the incoming issue is already structured and tagged.

Escalation When Perplexity Support Is Unresponsive

Escalation should be firm, chronological, and evidence-based. A useful follow-up starts by restating the case number or original subject line, then adds one compact timeline: date charged, date first emailed, date of any reply, current account status, and the specific remedy requested. Do not open five unrelated threads unless the original thread has gone stale for a meaningful period. Multiple threads can fragment the evidence.

For billing issues, the next step depends on purchase route. If the subscription was bought through Apple or Google, use app-store refund or dispute mechanisms while keeping Perplexity informed. If it was bought directly through Perplexity, send the invoice, account email, and billing portal evidence in the original thread. If the issue involves an enterprise workspace, involve the administrator because support may need tenant-level information that an ordinary member cannot see.

For account access, the escalation email should say whether the original email is inaccessible, whether the user has paid-account proof, whether the account contains critical Spaces or files, and whether the requested remedy is subscription transfer, cancellation, or access recovery. Perplexity’s account guidance makes clear that email changes and data restoration are constrained, so the escalation should not request an outcome the platform says it cannot provide.

For product bugs, escalation should add fresh evidence, not louder wording. Include a new timestamp, server-status check, browser extension test, mobile-versus-web comparison, and the shortest reproducible steps. If the bug affects answer reliability, compare Perplexity’s output with source material and cite the thread. The wider answering questions comparison explains why answer quality and citation quality should be treated separately when evaluating AI answer engines.

Support Email Templates for Billing, Login, and Bugs

The best templates are short enough to read in one screen but detailed enough to act on. Replace bracketed text with exact facts and attach only relevant screenshots. Never include passwords, full card numbers, API keys, or private customer data.

Billing Error Email Template

Subject: Billing error on my Perplexity account for [plan name]

Hello Perplexity Support, I am writing about a billing error on my account. My account email is [email]. I purchased [Pro, Max, Enterprise, or API credits] on [date and time with time zone] through [web, iOS, Android, or other route]. I was charged [amount], but [state the problem: duplicate charge, plan not activated, wrong plan, refund request, invoice issue]. I have attached [invoice, app-store receipt, billing portal screenshot]. Please confirm whether the charge is linked to my account and advise the next step. Thank you.

Login Issue Email Template

Subject: Cannot access Perplexity account linked to [email]

Hello Perplexity Support, I cannot access my account linked to [email]. The issue started on [date and time]. When I try to log in, [describe exact error or missing sign-in email]. I have already checked spam, tried a private browser window, disabled VPN, tested another device, and updated the app. My plan is [Free, Pro, Max, or Enterprise], and I have attached proof of payment if applicable. Please help me recover access or confirm the correct account status.

Technical Bug Email Template

Subject: Reproducible Perplexity bug on [web, iOS, Android, API]

Hello Perplexity Support, I found a reproducible issue on [platform]. Account email: [email]. App or browser version: [version]. Time of incident: [date, time, time zone]. Steps to reproduce: 1. [step] 2. [step] 3. [step]. Expected result: [result]. Actual result: [result]. I attached screenshots and removed sensitive data. For API cases, endpoint: [endpoint], model: [model], API group: [group], and error response: [error]. Please review and advise.

What Wider AI Support Benchmarks Reveal

Perplexity support does not exist in isolation. Customer-service AI is moving from simple chatbots toward agentic triage, summarisation, and case resolution. Gartner predicts that by 2028 at least 70 percent of customers will use conversational AI to start a customer-service journey. That forecast does not mean every problem will be solved by a bot. It means the first contact point is increasingly structured, automated, and dependent on clean input.

A 2026 KDD accepted Nubank paper is useful because it gives an operational example at massive scale. The authors describe building support AI agents for a user base above 100 million, combining human-in-the-loop development, LLM judging, online measurement, and deployment feedback. In a card-delivery deployment, they report a 37 percentage-point transactional NPS improvement and a 29 percentage-point self-service gain. The lesson for Perplexity users is not that all support should be automated. It is that well-structured cases give both humans and AI systems better evidence to classify, route, and resolve.

This also aligns with recent executive commentary. Perplexity CEO Aravind Srinivas told a University of Chicago audience that his one prediction was “accuracy,” adding that everything else breaks without it. Zahra Bahrololoumi, then at Salesforce, described the move toward agentic AI as a labour revolution, while emphasising that data quality and trust guardrails determine whether automation helps or harms. For support, those comments point in the same direction: speed is useful only when the case record is accurate.

That is why the practical recommendation remains human-centred. Use Perplexity’s AI and help pages to diagnose common faults, but use precise email and authenticated support channels for private money, identity, and entitlement cases. AI may help route the message. The user still has to make the evidence legible.

Takeaways

• Use support@perplexity.ai as the first documented contact route for account, billing, login, and general support cases.
• Send the message from the account that owns the subscription whenever possible, especially for Pro and Max activation issues.
• Separate web-billed subscriptions from Apple or Google subscriptions before asking for refunds or cancellation help.
• Attach receipts, screenshots, platform details, app or browser version, timestamps, and steps already tested.
• Do not paste passwords, full card numbers, complete API keys, or private customer data into support emails or community channels.
• Use Intercom and Pro Discord as faster Pro support surfaces, but keep billing and ownership evidence in a private support record.
• Treat api@perplexity.ai as unverified in the current official API documentation unless Perplexity confirms it for your account.
• Escalate with a timeline and case history, not a new vague thread, when the first support email is unresponsive.

Our Editorial Verification Process

This guide was compiled by cross-checking Perplexity’s public Help Center, account-access guidance, plan-comparison pages, Max and Enterprise pricing materials, the API pricing documentation, and the company changelog that introduced WhatsApp access. I then compared those product-specific facts with customer-service AI research from Gartner and a 2026 KDD accepted Nubank support-agent paper to test whether the escalation advice matched current support operations. Email routes, plan prices, usage limits, and API cost components were treated as confirmed only when supported by official documentation. Where the uploaded brief named a route that I could not verify in official API docs, especially api@perplexity.ai, the limitation is stated rather than inferred.

Conclusion

Perplexity’s support system is not hard to enter, but it does reward users who separate the problem before they escalate it. Email remains the safest first contact for account, billing, login, and general help because it creates a record that can carry receipts, ownership details, screenshots, and reproduction steps. Pro users have more convenient support surfaces, yet those routes do not remove the need for accurate evidence. API users need an even tighter record because pricing and reliability depend on model choice, context size, request type, and tool use.

The open question for 2026 is how much of this support workflow will become automated as AI agents move deeper into customer service. The likely answer is not that humans disappear. It is that better-structured evidence reaches the right human or automated resolver faster. For Perplexity users, that means the winning move is practical: identify whether the issue is billing, login, subscription, app stability, answer quality, or API usage, then send one precise message through the strongest channel for that category.

FAQs

What Is the Main Perplexity AI Customer Support Contact?

The main documented contact for unresolved account, billing, login, and general help is support@perplexity.ai. Include your account email, platform, app or browser version, screenshots, and the exact issue so support can verify the case without asking for basic details first.

Does Perplexity AI Offer Phone Support?

I found a public Perplexity WhatsApp access number for asking Perplexity from WhatsApp, but I did not verify a conventional phone support queue for billing or account disputes. Treat email and authenticated in-app support as stronger routes for private account issues.

How Do I Escalate a Perplexity Billing Issue?

Reply to the original support thread with a timeline, invoice, charge date, purchase route, account email, and the exact remedy requested. If the subscription was bought through Apple or Google, also use the relevant app-store refund or dispute process.

What Should I Include in a Perplexity Login Support Email?

Include the original account email, the email currently accessible, device, browser or app version, date the issue began, exact error message, sign-in link behaviour, spam-folder check, VPN status, and proof of payment if the account is paid.

Can Perplexity Change My Account Email?

Perplexity’s account guidance says account emails are permanently linked and ordinary email changes are not currently supported. In limited paid-account cases, direct subscriptions may be transferred, but old account data may not be recoverable.

How Do Pro Users Contact Perplexity Faster?

Pro users can use the in-app support portal through settings and may also use Pro Discord for faster visibility. Billing, ownership, and refund cases should still be handled in a private support record with receipts and account evidence.

Who Handles Perplexity App-Store Refunds?

If the subscription was purchased through Apple or Google, refund and dispute processes usually run through the app-store account. Perplexity support can help clarify account status, but the payment processor may control the refund path.

Where Should API Users Send Perplexity Technical Issues?

Use the official API documentation, console evidence, status checks, and documented account support route. The address api@perplexity.ai was listed in the brief but could not be verified in current official API docs during research.

References

• Perplexity AI. (2026). Need support? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/10354888-need-support
• Perplexity AI. (2026). Account access, subscription, or ownership issues? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/10354892-account-access-subscription-or-ownership-issues
• Perplexity AI. (2026). Which Perplexity subscription plan is right for you? Perplexity Help Center. https://www.perplexity.ai/help-center/en/articles/11332576-which-perplexity-subscription-plan-is-right-for-you
• Perplexity AI. (2026). Pricing. Perplexity API documentation. https://docs.perplexity.ai/docs/getting-started/pricing
• Perplexity AI. (2025). What we shipped: May 2nd. Perplexity Changelog. https://www.perplexity.ai/changelog/what-we-shipped-may-2nd
• Gartner. (2026). Customer service AI: Home in on high-ROI use cases. https://www.gartner.com/en/customer-service-support/topics/customer-service-ai
• Gupta, A., Rossell, K., Magnani, N., Correa, D., & Formiga, D. (2026). Building customer support AI agents at 100M-user scale: An evaluation-driven framework. arXiv. https://arxiv.org/abs/2606.08867
• Polsky Center for Entrepreneurship and Innovation. (2025). Aravind Srinivas on AI, accuracy, and Perplexity. https://polsky.uchicago.edu/2025/05/21/aravind-srinivas-on-ai-accuracy-and-perplexity/
• PwC. (2026). Agentic AI and the future of work: Interview with Zahra Bahrololoumi. https://www.pwc.com/gx/en/issues/artificial-intelligence/agentic-ai/future-of-work.html