Notifications: Digests, Channels & Preferences

Fluint Notifications give you a single place to control how and when Olli tells you about things that matter — meeting recaps, stalled deals, discovery gaps, upcoming call prep, and more. Instead of a firehose, you get batched digests on your schedule, plus immediate alerts for the moments you don't want to miss.

Notifications work across two dimensions:

Every setting is per-channel, so email and Slack DM can be configured completely independently.

Go to Settings > Notifications (Bell icon in the settings sidebar).

If you don't see a Notifications page in your settings, the feature may not yet be enabled for your organization. Your preferences save automatically — there is no Save button. After you make a change, Fluint waits about a second and then persists it in the background. A small "Saving…" indicator appears while the change is in flight.

Fluint currently supports two notification channels:

Turn a channel on or off with its toggle. Each channel has its own digest cadence and its own per-category delivery modes.

If you turn both channels off, you won't receive any notifications — Fluint will show a warning that reads "All channels are off. Notifications won't be delivered."

To receive notifications as direct messages from Olli in Slack, you need two things:

If Slack DM isn't available yet, the toggle will be greyed out and you'll see one of these messages underneath:

For full setup details, see the Slack <> Olli Integration guide.

Each notification category can be delivered in one of three modes on each channel:

Because delivery mode is set per-category per-channel, you have fine-grained control. For example, you might set Deal health to Immediate on email but Off on Slack DM, while Meeting insights go into the Digest on both.

Your digest cadence controls how often batched notifications are grouped and delivered. Each channel has its own cadence, so email can digest three times a day while Slack DM is off — or the other way around.

Turning cadence to Off only disables the batched digest on that channel. Any category you've set to Immediate will still be delivered in real time. To fully silence a channel, use the channel toggle.

Fluint groups notifications into eight categories. For each category, you choose how it's delivered on each of your enabled channels (Digest / Immediate / Off).

To silence a whole category, set it to Off on every channel you have enabled.

Digests are scheduled based on your local time. Fluint automatically detects your timezone, but you can override it in Settings > Notifications if you travel or want to use a different timezone than your device reports.

The timezone control only appears when at least one channel has a digest cadence other than Off.

If you're an admin, Settings > Notifications has a second tab labeled Organization. This is where you set org-wide defaults and guardrails for your team. It has three sections.

Set the default channels, cadence, and per-category delivery modes that apply to every user in your organization. Users inherit these defaults when they first use Fluint, and can still override them in their own preferences — unless the setting is locked (see below).

Some notifications are valuable for the whole team, not just individual reps. In this section, you can broadcast org-wide events to a shared Slack channel and/or email every user in the organization:

For each event, toggle Slack on and enter a channel name (e.g., #sales-signals), and/or toggle Email all to send to every user in the organization. The Slack toggle is disabled if your organization hasn't connected the Olli Slack app yet.

Lock a setting to prevent individual users from overriding it. Locked settings always use the value from Organization Defaults.

You can lock:

When a user views a locked setting in their own preferences, it appears with a lock icon and the tooltip "This setting is managed by your admin."

Important: Locking a setting does not change its current value — it only prevents users from editing it. Configure your Organization Defaults first, then lock the settings you want to enforce.