Skip to main content

Notification Preferences

Take control of which kenbun alerts you receive in Slack. Every rep can mute specific event types, see whether they are connected to Slack, and turn off all notifications globally — all from one place.

Why This Matters​

Triggers exist so your team finds out about hot leads in real time. But not every rep wants every alert. An account executive may care deeply about surge alerts on their own leads while finding the milestone-exit alerts noisy. Notification preferences make those choices personal.

These settings only apply to direct messages sent to you by kenbun. Notifications routed to shared team channels (for example, a #sales-alerts Slack channel configured by your admin) are unaffected by your preferences.

Finding Your Notification Preferences​

Navigate to Settings > Notifications.

The page is scoped to your active Organizational Unit. If you switch Organizational Units, your preferences for the new one load automatically.

What You Can Control​

Master Toggle​

At the top of the page, a single switch enables or disables every kenbun direct message to you across all event types.

  • On (default): You receive direct messages based on each event type's individual mute setting below.
  • Off: All direct messages are muted. Helper text reads: "All kenbun notifications muted. You can re-enable at any time."

The master toggle is independent of your event-type mutes. Turning it back on restores your previous per-event-type choices — nothing is lost.

Slack Mapping Status​

A read-only row shows whether your kenbun account is connected to a Slack identity. Two states are possible:

  • Mapped: Displays a masked version of your Slack identifier (for example, U12•••XYZ). You will receive direct messages when triggers configured for owner routing fire on your leads.
  • Not yet mapped: Displays the message "Not yet mapped. Ask your admin to sync Slack identities in Settings > Integrations > Slack." Until you are mapped, kenbun cannot DM you.

If you see "Not yet mapped" and have already been using Slack at your company, the most likely cause is that your kenbun email is different from your Slack email. Your admin can resolve this with a manual override.

Event Type Mute Toggles​

Below the Slack mapping row, you will see four event types. Each one has its own switch. Turning a switch off mutes the DMs for that event type only — other event types still come through.

Event TypeWhat It Means
Milestone ReachedA lead you own crossed a score threshold upward
Milestone ExitedA lead you own dropped back below a score threshold
Sequence CompletedA lead you own completed a configured event sequence in order
Surge DetectedA lead you own had a sudden spike in activity within a rolling window

The default for new users is all event types active (none muted). Mute the ones that feel noisy and leave the rest on.

What Happens When You Mute Something​

Muting an event type is a silent, personal preference:

  • The trigger still fires normally on its schedule.
  • The shared team channel (if your admin configured one) still receives the notification.
  • You simply do not receive the direct message.
  • No failure is recorded — kenbun knows you chose not to be notified.

Muting only affects future fires. Any DMs already sent are unchanged.

What "Not Yet Mapped" Means and How to Fix It​

Owner-routed direct messages depend on kenbun knowing your Slack user identity. Mapping is set up by an admin in one of two ways:

  1. Bulk sync — an admin runs an identity sync from Settings > Integrations > Slack that matches every team member by email.
  2. Manual override — an admin enters your Slack identifier directly for cases where your email differs between systems.

If your status reads "Not yet mapped," let your admin know. Once you are mapped, owner notifications start flowing immediately — no further action on your part.

Examples​

Example 1: An Account Executive who only wants the high-signal alerts.

  • Master toggle: On
  • Milestone Reached: On
  • Milestone Exited: Off
  • Sequence Completed: On
  • Surge Detected: On

The AE gets a DM the moment a lead they own reaches a milestone or completes a buying-intent sequence, but does not get woken up when scores naturally decay back below thresholds.

Example 2: A Sales Development Representative on PTO.

  • Master toggle: Off

No DMs of any kind arrive during PTO. On return, flipping the master toggle back on restores every previous mute setting.

Example 3: A new rep who has not been synced yet.

  • Slack mapping status: Not yet mapped

The rep configures their event type toggles in advance. Once the admin runs the identity sync, DMs start arriving for the events the rep left active.

Notes​

  • Preferences are stored per rep, per Organizational Unit. If you have access to two Organizational Units, you can mute different event types in each.
  • Your preferences are private. Admins cannot read or change another rep's preferences.
  • Changes take effect immediately. There is no "Save" button — toggling a switch persists the change instantly.