Skip to main content
This guide is for administrators and revenue operations setting up Quivly for their organization. If you need onboarding help, book time with the team.

​
Step 1: Connect your CRM

Your CRM brings in the core customer list that everything else links to. Teams starting from billing can also use a reviewed Stripe customer import. Confirm the intended account scope and business-domain matching with your Quivly onboarding team before importing.
1

Open the integration

Go to Data → Integrations, choose your CRM, and open the Configure tab. Salesforce and HubSpot are common starting points; Attio, Lightfield, Monaco, and Octolane are also supported.
2

Connect

Complete the CRM’s connection flow with the required workspace access or API key, then select the data to import. Supported objects vary by provider; the integration guide explains what syncs.
3

Watch the data arrive

Check the integration’s Logs tab for activity. Initial imports take time, and subsequent updates use the provider’s sync schedule or webhooks. See its integration guide for the cadence.

​
Step 2: Invite your team

Go to General → Members, click Invite Member, enter an email, and pick a role. Admins manage team access and organization configuration; Members can collaborate on supported customer workflows. Invitations expire after 7 days and can be revoked. You can also deactivate and reactivate members later.

​
Step 3: Review field mappings

1

Open the mapping editor

Go to Data → Objects → Customers → Configuration. Pick your integration and the object type (e.g. HubSpot Companies).
2

Review defaults, add custom fields

Default mappings cover the common fields. To track a CRM custom field, map it to an existing Quivly field or create a new custom field inline. See field mappings.For an initial Monaco or Octolane import, have the Quivly onboarding team save your account import scope before completing the mappings. The scope can include all accounts or reviewed conditions; it is separate from choosing fields in the editor.
3

Save

Choose Save changes, or Save & start import for an initial CRM mapping. Saved mappings are used as records are processed.
Once saved, an object’s integration source is locked — contact support to change it.

​
Step 4: Connect billing

Connect Stripe under Data → Integrations → Stripe → Configure. Review its initial customer mapping and import scope before starting. Import all Stripe business contacts includes contacts without payments or subscriptions; ask your Quivly team to configure a selected cohort if needed. Quivly links billing customers, subscriptions, and invoices through verified customer identities and business domains. See Stripe setup and cross-system linking.

​
Step 5: Configure health scores

1

Start the wizard

Go to Configuration → Health Score and create a config. The wizard has three steps.
2

Choose customers

Score all customers, or a specific segment (you can add one config per segment later with different weights and thresholds).
3

Set scores & categories

Drag the boundaries between the four score buckets (Critical, At Risk, Medium, Healthy), then enable the categories that matter — revenue, product usage, engagement, support, market signals — and set their weights. Weights must total 100%. Categories with no connected integration are marked so you know what data is missing.
4

Add scoring intelligence

Click Auto-configure — AI generates risk and growth signals tailored to your organization and connected tools. Review and edit their instructions, including any usage windows and thresholds. See health-score configuration.
5

Test and publish

Test the config on a specific customer, then Publish. Publishing in the app starts recalculation for the scoped customers, and every publish is saved to version history. Allow the background calculation to finish before checking the new scores.

​
Step 6: Turn on Slack notifications

  1. Install the Quivly Slack app under Data → Integrations → Slack (this also enables the Ask Quivly bot and conversation tracking for mapped channels).
  2. Add your company context under Configuration → Brain so Quivly understands your users, buyers, and market priorities. See Brain.
  3. Go to Configuration → Notifications: enable Quivly alerts, choose the customers to monitor, set how often to check for news, and select a Slack channel, relevance filter, and delivery schedule. See Notifications.

​
Step 7: Verify

  • Data → Integrations shows each integration’s status: Healthy, Unhealthy, Not Connected, or Not Set Up. Open a data-source integration’s Logs tab to inspect sync activity.
  • Open Customers and spot-check a few profiles: fields mapped correctly, revenue present, contacts linked.

​
Where to next

Add more data sources

Support, call recordings, and product usage make scores and AI answers richer.

Put AI to work

Ask Quivly, agents, actions, and notebooks all run on the data you just connected.

​
FAQ

The initial sync depends on data volume; after that, the provider’s schedule or webhooks keep it current. Check the integration’s Logs tab if something looks stale.
Open the integration and review its logs — most issues are authentication-related and fixed by reconnecting.
Yes — mappings are editable anytime and apply to future syncs. The integration source for an object, however, is locked after first save (contact support to change it).