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.
1

Open the integration

Go to Settings → Integrations, click Salesforce or HubSpot, and open the Configure tab.
2

Connect

Complete the embedded connection flow — sign in to your CRM and approve read access. Quivly syncs customers, contacts, opportunities, and owners (plus contracts from Salesforce and meetings from HubSpot).
3

Watch the data arrive

Syncing is continuous — changes flow in via webhooks rather than on a fixed schedule. Check the integration’s Logs tab for activity.

​
Step 2: Invite your team

Go to Settings → Members, click Invite Member, enter an email, and pick a role (roles come from your organization’s setup — typically Admin and Member; only Admins can change settings and integrations). 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 Settings → 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.
3

Save

Click Save Mappings. Mapping changes apply to future syncs.
Once saved, an object’s integration source is locked — contact support to change it.

​
Step 4: Connect billing

Connect Stripe the same way as your CRM (Settings → Integrations → Stripe → Configure). Quivly syncs billing customers, subscriptions, invoices, and products — powering MRR, renewal dates, and revenue-based health scoring. Stripe records match to your CRM customers automatically; see cross-system linking.

​
Step 5: Configure health scores

1

Start the wizard

Go to Settings → 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. Edit them as plain text.
5

Test and publish

Test the config on a specific customer, then Publish. Scores calculate on the next daily run, and every publish is saved to version history.

​
Step 6: Turn on Slack notifications

  1. Install the Quivly Slack app under Settings → Integrations → Slack (this also enables the Ask Quivly bot and conversation tracking for mapped channels).
  2. Go to Settings → Signals → Notifications: pick a channel, choose which insight relevance levels to send (all, high, medium, or low), and set the delivery schedule (immediate, hourly, daily, or weekly).

​
Step 7: Verify

  • Settings → 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, changes stream in continuously via webhooks. 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).