Slack Notifications
Set up internal Slack alerts in LostChurn — webhook configuration, event routing, and channel-based notifications for your recovery operations.
Slack notifications keep your team informed about recovery activity without requiring anyone to watch the dashboard. Configure alerts for critical events like high-value payment failures, successful recoveries, and campaign completions, routed to the right Slack channels.
How It Works
LostChurn sends notifications to Slack when configured events occur. Notifications are delivered via either an incoming webhook or an OAuth app connection, depending on your setup. Each notification includes structured details about the event — payment amounts, customer info, recovery status, and direct links to the relevant record in the LostChurn dashboard.
Setting Up Slack
Option 1: Incoming Webhook (Simpler)
Best for teams that want a quick setup with notifications going to a single channel.
- Navigate to Settings > Integrations > Slack
- Select Webhook as the connection type
- Create an incoming webhook in your Slack workspace:
- Go to api.slack.com/apps and create a new app (or use an existing one)
- Under Incoming Webhooks, activate webhooks and click Add New Webhook to Workspace
- Select the channel where you want notifications to appear
- Copy the webhook URL
- Paste the webhook URL in LostChurn and click Connect
- LostChurn sends a test message to confirm the connection
Option 2: OAuth App (More Flexible)
Best for teams that want notifications routed to multiple channels or direct messages.
- Navigate to Settings > Integrations > Slack
- Select OAuth as the connection type
- Click Connect to Slack and authorize LostChurn in your Slack workspace
- LostChurn stores the OAuth token and syncs your workspace's channel list
- Set a default channel for notifications
The OAuth connection allows LostChurn to send messages to any public channel in your workspace and to specific team members via direct message.
Configuring Notification Rules
After connecting Slack, set up rules that determine which events trigger notifications and where they are delivered.
Navigate to Settings > Integrations > Slack > Notification Rules and click Add Rule.
Each rule specifies:
| Field | Description |
|---|---|
| Event type | The LostChurn event that triggers the notification |
| Target type | Channel or Direct Message |
| Target | Channel name (e.g., #revenue-alerts) or Slack user ID |
| Enabled | Toggle the rule on or off without deleting it |
Recommended Events
Here are the most commonly configured Slack notifications:
| Event | Description | Suggested Channel |
|---|---|---|
| Payment Recovered | A failed payment was successfully recovered | #revenue-wins |
| Payment Failed | A new payment failure was received | #payment-alerts |
| Recovery Terminal | A payment was declared unrecoverable | #payment-alerts |
| High Value Churn | A high-value subscription payment failed | #urgent-alerts |
| Campaign Step Queued | A dunning message is about to be sent | #campaign-activity |
| A/B Test Evaluation | An A/B test reached statistical significance | #growth-team |
| A/B Test Winner Promoted | A winning variant was promoted | #growth-team |
| Card Expiring Soon | A customer's card is about to expire | #proactive-recovery |
You can create multiple rules for the same event type to send notifications to different channels. For example, send all PaymentFailed events to #payment-alerts but also send high-value failures to #urgent-alerts using a separate rule with the HighValueChurn event type.
Channel Routing
Route different notification types to different channels based on your team structure:
| Channel | Purpose | Event Types |
|---|---|---|
#revenue-wins | Celebrate recoveries | Payment Recovered |
#payment-alerts | Monitor failures in real time | Payment Failed, Recovery Terminal |
#urgent-alerts | High-priority escalation | High Value Churn |
#campaign-activity | Campaign operations | Campaign Step Queued |
#growth-team | Experimentation results | A/B Test Evaluation, A/B Test Winner Promoted |
Direct Messages
For high-priority events, you can route notifications directly to specific team members. Use the DM target type and enter the Slack user ID of the person who should receive the alert. This is useful for:
- Notifying a revenue manager when a payment above a threshold fails
- Alerting an on-call engineer when webhook delivery fails
- Sending campaign completion summaries to the marketing lead
Rate Limiting
To prevent notification floods during high-volume events (e.g., a payment processor outage causing hundreds of simultaneous failures), LostChurn applies rate limiting per event type per merchant. If the rate limit is reached, notifications are batched into a summary message.
Rate limit state is tracked per event type and only sends one notification per event type within the configured cooldown window.
Notification Format
Slack notifications are sent as structured messages with:
- Event title — What happened (e.g., "Payment Recovered")
- Amount — The payment amount (when applicable)
- Customer — Customer name or email
- Details — Event-specific context (decline reason, recovery method, campaign step, etc.)
- Dashboard link — Direct link to the relevant record in LostChurn
Message Threading
When using the OAuth connection, LostChurn supports Slack message threading. Related notifications (e.g., multiple events for the same payment recovery) are threaded under the original notification to keep channels organized. Thread references are tracked via the Slack message timestamp (slack_ts).
Troubleshooting
Notifications Not Arriving
- Verify the connection status in Settings > Integrations > Slack
- Check that notification rules are enabled for the event type
- For webhooks: verify the webhook URL is still active in your Slack app settings
- For OAuth: re-authorize if the token has expired
- Check the Slack message log in Settings > Integrations > Slack > Message Log for delivery errors
Rate-Limited Notifications
If you see batched summary messages instead of individual notifications, your event volume exceeded the rate limit. This is normal during high-volume periods. Adjust the rate limit threshold in Settings > Integrations > Slack > Advanced if needed.
What's Next
- Creating Campaigns — Build campaigns that trigger Slack notifications at key moments
- A/B Testing — Get notified when your experiments reach significance
- Campaigns Overview — Return to the campaign documentation hub
Custom Sender Domain
Send recovery emails from your own domain for better deliverability and brand recognition — CNAME setup, DNS verification, and domain warmup.
What Are Cancel Flows?
Understand how cancel flows intercept voluntary churn by guiding subscribers through surveys and personalized retention offers before they leave.