> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quivly.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently Asked Questions

> Common questions about what Quivly is, what it connects to, how its AI works, and how data is handled.

## About Quivly

<AccordionGroup>
  <Accordion title="What is Quivly?">
    Quivly is an AI-native customer intelligence platform for revenue and customer success teams. It unifies CRM, billing, support, call, Slack, and product usage data into one customer view, then layers AI on top: health scores, a research assistant (Ask Quivly), automated agents, drafted actions, AI-written notebooks, and AI-computed fields.
  </Accordion>

  <Accordion title="Who is Quivly for?">
    Customer success and revenue teams that want one place to see customer health and act on it — and revenue operations teams who set up the data. Developers get an MCP server and APIs on top of the same data.
  </Accordion>

  <Accordion title="What systems does Quivly connect to?">
    Salesforce, HubSpot (CRM); Stripe (billing); Pylon (support); Fireflies, Fathom, Granola (calls); Slack; Snowflake, BigQuery, PostHog, and a Push API (product usage); Gmail, Google Calendar, Calendly (agent tools); GitHub (skill import); plus any third-party MCP server. See [integrations](/integrations/introduction).
  </Accordion>

  <Accordion title="Does Quivly have an MCP server?">
    Yes — a hosted MCP server at `https://mcp.quivly.ai/connect` that connects Claude, ChatGPT, Cursor, and other AI tools to your Quivly data with per-user OAuth sign-in. See [MCP server](/developers/mcp-server).
  </Accordion>
</AccordionGroup>

## AI

<AccordionGroup>
  <Accordion title="Can Quivly's AI change data in my CRM or billing system?">
    No. Data integrations are read-only. Outbound activity — a Slack message, an email, a calendar invite — only happens through agent steps and actions that your team configures, and you can require human review before anything sends.
  </Accordion>

  <Accordion title="How do I control what the AI does automatically?">
    Agents only act when you build and publish them, and any step can sit behind a Review gate that pauses for human approval. Recommendations from signal rules are always drafts — a person reviews and sends them.
  </Accordion>

  <Accordion title="How does Quivly calculate health scores?">
    Each customer is scored across up to five weighted categories — revenue, product usage, engagement, support, and market signals — using thresholds you configure, with AI-generated risk and growth signals. See [health scores](/health-scores/introduction).
  </Accordion>
</AccordionGroup>

## Data

<AccordionGroup>
  <Accordion title="Is my data isolated from other Quivly customers?">
    Yes — all data is scoped to your organization, and every surface (app, Slack bot, MCP server) only answers from your own org's data.
  </Accordion>

  <Accordion title="How does data get matched to the right customer?">
    Records from different systems are linked by identifiers like email domains and external IDs into one customer profile. See [cross-system linking](/field-mappings/cross-system-linking).
  </Accordion>
</AccordionGroup>

## Getting started

<AccordionGroup>
  <Accordion title="What should I set up first?">
    Connect your CRM, then billing, then whatever else you have — each source makes scores and answers richer. The [quick start guide](/quickstart-admin) walks through it.
  </Accordion>

  <Accordion title="How do I get help?">
    Email [support@quivly.ai](mailto:support@quivly.ai) or [book time with the team](https://cal.com/chandrika).
  </Accordion>
</AccordionGroup>