How Quivly Works

Data flows in from your connected systems, gets unified into one customer model, and AI features work on top of that model.

Quivly has three layers. Data comes in, gets organized around customers, and AI acts on it.

1. Data in

You connect the systems you already use:

• CRM (Salesforce, HubSpot, Attio, Lightfield, Monaco, Octolane) — supported customer, contact, opportunity, and owner records
• Billing (Stripe) — subscriptions, invoices, MRR
• Support (Pylon, Intercom) — tickets and available response metrics
• Calls (Fireflies, Fathom, Granola, Circleback, Sybill) — available transcripts and summaries
• Communication — mapped Slack channels, customer-linked Gmail threads, and Google Calendar meetings
• Product usage — from your warehouse (Snowflake, BigQuery, Redshift), PostHog, or pushed directly via the Usage API

Quivly reads from these systems. It never writes back to your CRM, billing, or support tools on its own — outbound messages (like a Slack message or email from an agent) only happen through steps you configure and approve. See security and compliance.

Brain adds the knowledge that may not live in a connected system: your company’s context, terminology, customer guidance, and reference documents. Keep its company-wide knowledge separate from customer-specific sources.

2. One customer model

Records from different systems are matched to a single customer — a Stripe customer, a HubSpot company, and a Slack channel all land on the same profile. You control how fields map through field mappings, and you can extend the model with custom fields and objects.

Think of it like a filing system that files every new document under the right customer automatically.

3. AI on top

Every AI feature reads from the same unified model:

Feature	What it does
Health scores	Scores each customer across revenue, usage, engagement, support, and market signals
Ask Quivly	Answers questions across all connected data, in-app or in Slack
Agents	Runs automated workflows on triggers like record changes or health drops
Plays	Monitors customer outcomes and prepares recommendations and changes for review
Actions	Drafts next steps for you to review and send
Notebooks	Writes customer documents (QBR prep, handoffs) from live data
AI fields	Computes field values from each customer’s data on a schedule
Skills	Your reusable instructions that steer all of the above

Developers can also point external AI tools (Claude, Cursor, ChatGPT) at the same data through the Quivly MCP server.

FAQ

Does Quivly modify data in my CRM or billing system?

Data ingestion reads from connected systems. Supported AI actions can separately propose changes for review, and published workflows run the steps your team configures. Connecting a source alone does not authorize changes. See security and compliance.

How do records from different systems get matched to one customer?

Quivly links records across systems using identifiers like domains and external IDs, and you can review and adjust the linking. See cross-system linking.

Do I need every integration for AI features to work?

No. Each feature works with whatever data you’ve connected — more sources just make answers and scores richer. Health score categories with no connected source are simply disabled.