Skip to main content
Open Configuration → Notifications to manage Quivly alerts. This page brings together your customer scope, news collection frequency, Slack destination, relevance filter, and delivery schedule. These settings control market updates. Play alerts, Meeting Prep delivery, and Slack agent replies have their own configuration.

​
Configure alerts

1

Turn on Quivly alerts

Enable the Quivly alerts switch. Complete your organization’s setup first if the page says it is not ready.
2

Choose what to monitor

Under Customers, choose all customers or a segment. All customers uses the default filters from your Customers page.Set Check for news to Daily, Every 3 days, Weekly, Every 2 weeks, or Monthly. This controls news collection, separately from alert delivery.
3

Connect Slack and choose a channel

Use Connect Slack or Reconnect Slack if prompted. Pick a channel under Where to send alerts. The Quivly bot needs access; invite it to the channel if necessary, especially for private channels.
4

Choose relevance and delivery

Select which relevance levels to include and when to send alerts, then choose Save changes. Wait for confirmation before leaving.

​
Relevance

Relevance uses your company context in Brain. Describe your users, buyers, ideal customers, and market priorities there so Quivly can assess why a development matters to your business.

​
Delivery schedule

Choose As updates arrive, Hourly digest, Daily digest, or Weekly digest. Daily and weekly digests require a time and timezone; weekly digests also require a day. Delivery frequency does not change how often Quivly collects news. For example, a daily digest summarizes available updates; it does not make a weekly collection schedule run daily.

​
Pause or troubleshoot

Turn Quivly alerts off and save to stop monitoring and scheduled alerts while retaining the configuration. Updates already being delivered may still arrive. You do not need to disconnect the Slack integration to pause these alerts. If channels are missing, check the Slack connection, invite the bot to the destination, and retry channel loading. A reconnect prompt preserves your saved preferences. If settings changed elsewhere, reload before saving so you do not overwrite another administrator’s changes.