Skip to main content

Owner Notifications

Send trigger alerts straight to the rep who owns the lead — as a Slack DM — instead of (or in addition to) a shared team channel. Owner notifications turn the firehose of trigger fires into individually relevant pings that land where your reps already work.

Why This Matters​

A shared #hot-leads channel works for small teams. It breaks down the moment one rep owns 40 accounts and has to scan a busy channel looking for their leads. Owner notifications solve that by routing each trigger fire to the specific person responsible for the lead.

Typical scenarios:

  • Per-rep ownership — Account executives only want alerts about their own pipeline. DMs deliver that, the channel does not.
  • High-volume teams — A surge trigger that fires 50 times a day across 50 reps becomes 50 quiet, personal DMs instead of 50 messages in a single channel.
  • Mixed routing — Send the alert to a manager-visible channel and DM the rep who owns the lead. Both happen automatically.

How Owner Notifications Work​

When a trigger fires, kenbun reads the lead's current owner and sends a Slack DM to that owner. The behavior is identical for all three trigger types — Milestone, Sequence, and Surge.

The four canonical event types covered by owner notifications are:

Event TypeFires When
Milestone ReachedA lead's score crosses a milestone threshold upward
Milestone ExitedA lead's score drops back below a milestone threshold
Sequence CompletedA lead completes the configured event sequence in order
Surge DetectedA lead's activity rate spikes within the rolling window

Reps can mute any of these four event types individually from their own Notification Preferences page. Owner notifications respect those personal preferences automatically.

Enabling Owner Notifications on a Trigger​

  1. Navigate to Configure > Triggers and open the trigger type you want to edit (Milestone, Sequence, or Surge).
  2. Open an existing trigger or click Create Trigger.
  3. In the Notification Settings section, check the box labeled Notify the Lead Owner.
  4. Save the trigger.

Helper text under the checkbox reads: "DMs the lead's owner in Slack. They can mute event types in their notification preferences."

You can enable owner notifications by themselves or alongside a regular destination (Slack channel, Teams channel, webhook, email). When both are configured, kenbun dispatches to both. A failure on one path never blocks the other.

Slack Identity Mapping​

Each rep needs to be linked to a Slack user before owner notifications can reach them. kenbun matches reps to Slack users by their email address.

The Mapping Status Pill​

When you check Notify the Lead Owner on a trigger form, a status pill appears next to the checkbox showing how many members in the current Organizational Unit are mapped to Slack:

7 of 10 members have Slack mapped

The pill is a quick sanity check before you save. If the count is below 100 percent, the pill also shows a Resync identities link to the Slack integration page.

Syncing Identities​

To bring the mapped count up to date:

  1. Navigate to Settings > Integrations > Slack.
  2. Click Resync Identities.
  3. kenbun looks up each confirmed team member by email in your connected Slack workspace and stores the match.

After a sync, refresh the trigger form to see the updated pill.

Manual Override​

If a rep's kenbun email differs from their Slack workspace email, the email lookup will not find them. Admins can manually link the right Slack identity from Settings > Integrations > Slack by selecting the member and entering their Slack user identifier.

What Happens When an Owner Cannot Be Reached​

Owner notifications fail loudly and explicitly. kenbun never silently re-routes a missed owner DM to a team channel — that would defeat the purpose of choosing owner routing in the first place.

The table below summarizes every routing outcome:

SituationWhat kenbun DoesVisible Where
Owner is mapped and notifications enabledDM is sentAudit log + dispatch counters
Lead has no owner assignedDispatch is skipped, failure recordedTrigger failures log
Owner is mapped but rep muted this event typeDM is suppressed; no failure recordedRep's preferences only
Owner is mapped but rep turned off all notificationsDM is suppressed; no failure recordedRep's preferences only
Owner has no Slack identity mappedDispatch fails; failure recordedTrigger failures log
Owner record has been deletedDispatch is skipped, failure recordedTrigger failures log

The two "suppressed silently" cases (muted event type, master toggle off) are intentional user choices, so they do not show up as failures. Every other miss writes a row to the trigger failures log so admins can investigate.

Reviewing Failures​

When a dispatch fails, the failure row includes:

  • The trigger that fired
  • The lead it fired on
  • The owner kenbun tried to reach
  • The reason (no_owner, owner_not_mapped, slack_api, etc.)
  • The timestamp

If you see a pattern of owner_not_mapped failures, the fix is almost always to run a Slack identity resync or add a manual override for the missing rep.

Owner Routing Alongside Team Channels​

The Notify the Lead Owner checkbox is independent of every other destination on the trigger form. A trigger can route to any combination of:

  • A saved Notification Channel
  • An ad-hoc Slack channel, Teams channel, webhook, or email address
  • The lead owner via DM

When more than one destination is configured, kenbun dispatches them in parallel. Notification failures on one path are logged independently and do not affect the others.

A common pattern:

AudienceDestination
Manager visibilitySlack channel #sales-hot-leads
Rep who owns the leadDM via owner notification

Both fire on every threshold crossing. Reps act on their lead; managers see the full pipeline.

Behavior on Owner Reassignment​

kenbun reads the lead's owner_id at the moment the trigger fires, not when the trigger was created. If a lead is reassigned, the next fire goes to the new owner automatically. No reconfiguration needed.

If the owner field is cleared while the trigger is still active, future fires will record a no_owner failure until the lead is reassigned.

Prerequisites​

Before enabling owner notifications, confirm:

  1. Slack is connected for the Organizational Unit. See Slack Integration for setup steps.
  2. Reps have been mapped to Slack identities. Run the identity sync from Settings > Integrations > Slack at least once.
  3. Leads have owners assigned. Owner assignment can happen via HubSpot sync, manual assignment, or the Lead Owner Assignment API.

Triggers with Notify the Lead Owner checked will be rejected at save time if the Organizational Unit is not connected to Slack.

Best Practices​

  • Pair owner DMs with a manager-visible channel for the highest-value triggers so leadership has signal too.
  • Resync Slack identities after onboarding new reps so they get DMs from day one.
  • Encourage reps to set their notification preferences early so the high-volume event types they do not want do not arrive as DMs.
  • Audit the failures log monthly — owner_not_mapped failures usually mean a new hire has not been synced.

Troubleshooting​

Reps Are Not Getting DMs​

Walk through this checklist:

  1. Is the trigger active and not paused?
  2. Is Notify the Lead Owner checked on the trigger?
  3. Does the lead have an owner assigned? Open the lead detail page to confirm.
  4. Is the owner mapped to a Slack user? Open Settings > Integrations > Slack and check the member's row.
  5. Has the rep muted that event type in their own preferences?
  6. Is the rep's master notification toggle off?
  7. Has the Slack integration disconnected for that Organizational Unit?

The trigger failures log will tell you exactly which step is failing for any specific dispatch.

The Mapping Status Pill Shows the Wrong Count​

The pill counts confirmed members in the current Organizational Unit only. Pending invitations and members in other Organizational Units are not included. To refresh the count, run a Slack identity resync.

A Rep's Email Differs Between kenbun and Slack​

Use the manual override on Settings > Integrations > Slack to enter the correct Slack identifier directly. Manual overrides survive future identity syncs.