> ## 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.
# Customer 360 Review
> Run an account review or QBR from the customer overview, supporting tabs, and an AI notebook written from live data.
## Overview
A customer 360 in Quivly is the profile itself: one account, with health, revenue, usage, calls, support, market signals, opportunities, and projects on the same page. You do not export a separate briefing pack unless you want one — [notebooks](/product/notebooks) write that document from the same data.
Use this workflow to:
* Set the [Overview tab](/customer-views/account-tab) layout your team uses for every review
* Walk the tabs in a fixed order so you do not miss a source
* Generate a QBR, EBR, or handoff notebook and accept or edit the draft
* Ask follow-up questions in [Ask Quivly](/product/ask-quivly) without leaving the account
***
## What you need connected
The review is only as complete as the integrations behind it. Each missing source blanks a section, not the whole profile.
| Tab / object | Typical source |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Overview, contacts, opportunities | [Salesforce](/integrations/crm/salesforce) or [HubSpot](/integrations/crm/hubspot) |
| Revenue | [Stripe](/integrations/billing/stripe) |
| Usage | [Warehouse](/integrations/warehouses/overview), [PostHog](/integrations/product-usage/posthog), or [Push API](/integrations/product-usage/api-overview) |
| Calls | [Fireflies](/integrations/call-recordings/fireflies), [Fathom](/integrations/call-recordings/fathom), or [Granola](/integrations/call-recordings/granola) |
| Support | [Pylon](/integrations/support/pylon) |
| Slack | [Slack](/integrations/communication/slack) |
| Health | A published [health score config](/health-scores/configuration) |
| Market signals | [Market signals](/market-signals/introduction) enabled for the org |
***
## Customize the Overview tab once
The Overview tab is the default view when you open a customer. The layout is shared across customers.
Click **Customers**, then a row. You land on **Overview**.
The header shows name, domain, and LinkedIn, plus quick-edit fields (defaults: **Segment**, **Service Tier**, **Lifecycle Stage**). Use the header customize control to show up to 8 fields. CRM-synced, AI-computed, and read-only fields render as locked pills.
The picker (7d / 30d / 90d / MTD / QTD / YTD / custom / all) scopes every metric section on the canvas. Use **90d** or **QTD** for a quarterly review.
Click **Customize**: drag to reorder, hide sections you do not use, and use each section's gear to pick metrics. Click **Done**. Sections available:
| Section | Contents |
| ------------------ | --------------------------------------------------------------- |
| **Health Score** | Current score, trend, risk badge, history chart (pinned at top) |
| **AI Insights** | AI-written account summary |
| **Revenue** | MRR, ARR, outstanding, days to renewal (warning at ≤30 days) |
| **Usage** | The usage metrics you select, each with value and trend |
| **Support** | Total and open tickets, average resolution and first response |
| **Calls** | Total calls, average duration, average gap, last call |
| **Market Signals** | Three most recent signals with sentiment |
| **Projects** | Active project status |
The collapsible **Account Info** sidebar holds the editable record (owner, domain, custom fields) and read-only CRM / AI fields. Search filters the field list.
***
## Walk the profile
After the overview, open the tabs that still have questions. Stay on one customer until the notebook is done.
| Order | Tab | What to confirm |
| ----- | ---------------------------------------------------- | ----------------------------------------------------------------------------------- |
| 1 | [Health Score](/customer-views/health-score-tab) | Overall score, category breakdown, trend, whether a drop is a config version change |
| 2 | [Revenue](/customer-views/revenue-tab) | MRR, outstanding invoices, days to renewal, cancel-at-period-end notices |
| 3 | [Usage](/customer-views/usage-tab) | Direction of core metrics over the same window as the overview |
| 4 | [Calls](/customer-views/calls-tab) | Last call, sentiment, action items, risk/growth signals in the transcript |
| 5 | [Support](/customer-views/support-tab) | Open tickets, age, escalations, resolution time |
| 6 | [Market Signals](/customer-views/market-signals-tab) | Recent external news (funding, hiring, layoffs) |
| 7 | [Opportunities](/product/opportunities) | Open expansion or renewal deals from the CRM |
| 8 | [Projects](/product/projects) | Onboarding or success-plan status, overdue milestones |
Do not treat the AI Insights blurb or a notebook draft as the system of record. Accept notebook text only after you have checked the tabs the draft cites. Every AI surface in Quivly is scoped to this customer and this org — still verify numbers before a customer meeting.
***
## Write the review document
Notebooks live on the customer. The AI reads that customer's calls, revenue, tickets, usage, and health. It cannot pull other customers.
Open **Notebooks** on the customer. Start empty, or run **Write with AI**.
Use a saved [skill](/product/skills) (templates include **QBR Prep** and **Sales Handoff Brief**), a free-form prompt, or both. In the editor, `/` inserts at the cursor.
Streamed text stays highlighted until you **Accept**, **Discard**, or **Retry**. Accepted blocks get a **Sources** line for the platforms the model actually queried.
The rest is a normal rich-text editor (headings, lists, tables). Edits autosave. Generation can run up to about 2.5 minutes.
An [agent](/product/agents) can create a notebook on a schedule (template **Renewal prep brief**) or on a health change. Add a Review step if a human should see it before the meeting. External tools can call `create_notebook` on the [MCP server](/developers/mcp-server).
***
## Ask follow-ups
[Ask Quivly](/product/ask-quivly) is org-wide chat, not limited to the open customer. For questions about *this* account, name the customer in the prompt, or stay in the notebook. Ask Quivly is read-only.
Useful prompts during prep:
* Category drivers for this customer's latest health score
* Open tickets older than N days
* Themes from calls in the review window
* MRR and outstanding invoices vs last quarter
***
## After the meeting
| Follow-up | Where |
| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Send the recap or schedule the next QBR | [Actions](/product/actions) (review the draft) or an [agent](/product/agents) App Action (Gmail / Calendar) behind a Review gate |
| Capture commitments as delivery work | [Projects](/product/projects) tasks and milestones |
| Change CRM stage or close a deal | Your CRM — Quivly does not write back |
| Recurring reviews | Agent on a **Schedule** trigger for a segment, creating a notebook each cycle |
***
## FAQ
No. Customizing Overview applies across customers for the organization layout you save. Header field choices and section order are shared.
No. Each notebook is scoped to one customer, enforced server-side. For a book-of-business view, use the [customer list](/customer-views/customer-list), a [dashboard](/dashboards/introduction), or Ask Quivly.
The score breakdown includes **Recommended Actions** generated from that calculation. They are suggestions. Signal-rule items in [Actions](/product/actions) are the inbox you work.
***
## Related guides
When the 360 is a save motion, not a QBR
Renewals, invoices, and pipeline
Usage trends and health usage scoring
Header fields, sections, and customize mode