Notifications & Alerts
How Kit notifies your team about outreach events. Email alerts, Slack integration, and notification preferences.
Overview
Kit proactively notifies your team when outreach events need attention. Notifications are delivered via three channels:
| Channel | Delivery | Setup Required |
|---|---|---|
| In-app | Real-time via ActionCable | None; always on |
| Per-event, gated by preferences | None; on by default | |
| Slack | Per-event, routed to channels | Connect Slack + assign purposes |
Email Alerts
Campaign notifications go to Outreach members who can access the campaign and subscribe to Outreach activity. Experiment notifications require access to every campaign in the experiment.
| Event | When It Fires | Why It Matters |
|---|---|---|
| Prospect replied | Prospect replies and sentiment is classified | Warm leads go cold fast; act while interest is fresh |
| Drafts ready | All AI research jobs in a batch complete | The human-in-the-loop gate; drafts need approval before sending |
| Bounce rate alert | Campaign exceeds 5% bounce rate (min 10 sent) | High bounces damage domain reputation; alert has 24-hour cooldown |
| Campaign completed | Campaign status changes to completed | Includes stats: sent, replies, bounced |
| Experiment ready | A/B experiment reaches sufficient sample size | Compare results before deciding whether to conclude the experiment |
| Connection recovered | SMTP/IMAP connection restored after failure | Symmetric with the existing degraded alert |
Managing Preferences
Team members control outreach email notifications from Account > Email preferences (/account/email_preferences). The Outreach activity category covers all events above. Unsubscribing stops email delivery only; in-app and Slack notifications continue.
Slack Integration
If your account has a Slack connection, outreach events can be routed to specific channels.
Available Purposes
| Purpose | Description |
|---|---|
| Prospect replied to outreach | Any actionable reply that is not classified as interested |
| Interested prospect replied - review now | Reply classified as interested; routed separately so you can watch it closely |
| Outreach drafts ready for review | AI drafts finished and are waiting for approval |
| Outreach bounce rate alert | Campaign crossed the bounce rate threshold |
| Outreach campaign completed | Campaign finished sending |
| Outreach experiment ready to conclude | A/B experiment reached its sample size |
Replies split across two purposes: interested replies go to Interested prospect replied - review now, and every other actionable sentiment goes to Prospect replied to outreach. Route them to the same channel if you don’t need the split.
Setup
- Go to Integrations > Slack and connect your workspace (if not already connected)
- Under Channel Routing, assign outreach purposes to the channels where you want alerts
- Use the All purpose to route every event to a single channel, or assign specific purposes to different channels
Slack messages include structured blocks with campaign/prospect details and a direct link to the relevant page in Kit.
Experiment Notifications
Kit checks running A/B experiments daily (9 AM). When all variants in an experiment have reached the configured minimum sample size, Kit:
- Stamps the experiment so it only notifies once
- Sends in-app notifications to eligible Outreach members and email according to their preferences
- Posts to Slack (if configured)
Review the results and decide whether to choose a variant or collect more data. Reaching the minimum sample size does not establish a significant difference.
See Running Experiments for setup, interpretation, and the separate Conclude and Apply winner actions.