Support & frequently asked questions

ARIA answers questions about what consumers are actually saying — trends in your category, how your brand is perceived versus the leader, which claims and hooks resonate, and what needs are going unmet.

Ask in plain language, the way you'd brief a researcher. You'll get the sharpest answer when you include a category, a market and a time window — for example: "What are consumers in India saying about acne-prone and oily skin in the last 3 months?"

From public social and web content — posts, comments, videos and engagement data published openly by their authors, plus content licensed from third-party providers. ARIA does not use private data, and it does not access your own social accounts.

Importantly, ARIA reads caption, audio and video — not just text. A creator who says an ingredient out loud but never types it is still found, which is why the insights are of more quality and depth.

It doesn't guess keywords. ARIA reads the intent of your question, then draws the category vocabulary from Convosight's knowledge graph — a human-curated map of how people actually talk about a category, built and corrected by our team over more than ten years.

Ambiguous terms are bound to context, so charcoal becomes charcoal AND teeth in an oral-care question rather than returning barbecue posts. Matched content is then ranked by relevance, and the strongest content goes into the analysis.

Change them. Filters are editable at any point in the chat — just tell ARIA what's off (for example, "drop the charcoal keyword") and it rebuilds the filter and re-runs the analysis.

A general AI averages everything ever written about a demographic and gives you a confident stereotype with no cohort behind it. A Persona stands on one cohort, one category, one market, recent — reconstructed from what those people actually said in public, unprompted, on video and in comments.

You can show it a claim, a pack or an ad, ask it questions, and push back on its answers. It responds in the cohort's own language, including regional and code-mixed speech.

You brief it the way you'd brief a recruiter — for example, "Gen Z women in the US with acne." That brief is decomposed into the filters that decide whose conversations count, and the cohort is then interrogated on eight consumer truths, asked twice: once of the cohort, once of the category.

Typically 2,000–4,000+ posts, videos and comments and 50–100 industry articles are read, and it takes roughly 40–60 minutes from brief to your first question. Volumes follow the cohort — a chatty cohort yields more, a narrow one less — and every Persona shows what it actually read.

No, and this matters. A Persona is not a real consumer and not a prediction of one — the name and photo are simply a handle. It's a model of how a defined cohort behaves and talks, reconstructed from public conversation.

Treat every answer as a well-evidenced view of what these people think, not as a fact about what any individual will do. A Persona is also not a statistical sample — it gives you no incidence, frequency or significance.

Narrowing many options to a few — and hearing exactly why the rest failed. It exists to take you from ten ideas to the two worth spending real money testing on real people.

Use it to pressure-test concepts, claims, packaging and messaging early and cheaply. Use surveys and focus groups when you need to measure — norms, incidence and statistical confidence.

Yes, by default and on purpose — branded and creator-paid content is a large part of what shapes category perception, so it belongs in the picture. If you want organic conversation only, tell us before the Persona is built and we'll build it on a smaller but cleaner corpus.

Yes. ARIA is a standard MCP server, so any MCP-compatible client can connect to it — a commercial AI assistant, a platform you're building, or an internal tool your team uses. There's no bespoke integration to write on our side.

To get started, contact us (reachus@convosight.com) and we'll provide the connection details for your environment: the server endpoint, the authentication setup, and a walkthrough with your engineers. New to ARIA? See the Get Started guide.

Three things:

• An active ARIA subscription for the users who will be asking questions.
• A client that supports MCP. We support the common transports; tell us which client you're using and we'll confirm the right endpoint for it.
• OAuth sign-in, so each of your users authenticates with their own Convosight account.

Setup is a configuration exercise, not a development project — most connections are made in a single session with our team.

Your client can ask ARIA a consumer-intelligence question, continue that conversation with follow-ups in the same session, and check service status and remaining usage.

What returns is a written answer, the key insights behind it, and the public posts and comments the answer is based on, with links to the originals. How richly that renders depends on your client — some display tables, cards and sources fully, others show text only. The substance of the answer is the same either way.

Each user signs in with their own Convosight account via OAuth. Connecting authenticates them; it does not by itself grant access. What they can ask, and how much, follows the subscription and permissions on their account — so a user only ever sees what they're entitled to.

A daily usage limit applies per user, or per team on business accounts, and it is shared across every client they connect through — connecting two tools doesn't create two allowances. Current usage and reset time can be checked at any time, and users are told when they reach the limit.

Data. We receive an account reference for the authenticated user, the question asked, and the session information needed to maintain the conversation and apply limits. What goes back is the answer and its sources — nothing beyond that is passed to the connected client. We do not use your questions or content to train AI models, and the connection is one-way: it lets your client call ARIA's tools and gives Convosight no access to your systems, accounts or other data. Full detail is in our Privacy Policy.

Embedding or reselling. A standard subscription covers use inside your own organisation. If you want to make ARIA available to your customers — embedded in a product, platform or service you sell — that's a partnership, and it needs commercial terms in place first. Get in touch (reachus@convosight.com) and we'll work through it with you.

Make sure ARIA is enabled in that conversation, and phrase the question so it clearly needs consumer or social data — include a category, a market and a time window. Questions ARIA can't help with (stock prices, writing copy, generating designs) are answered by the assistant directly, which is expected.

This usually means the client is pointed at the wrong endpoint for the transport it supports, or the OAuth sign-in hasn't completed. Refresh the tool list in your client first; if it's still empty, send us the client you're using (reachus@convosight.com) and we'll confirm the correct endpoint and check the connection from our side.

Signing in confirms who you are; access follows your subscription. If you've signed in successfully but can't run questions, your account may not have ARIA enabled — contact your Convosight account team or email us (reachus@convosight.com) and we'll check.