Slack Alerts
Overview
Slack alerts notify your team the moment an account is worth acting on — a lead's score jumps to Hot, an account's buying likelihood rises, or a promising account goes quiet. Connect your Slack workspace once, then choose which moments should post an alert and where each one should land.
Prerequisites
- A Slack workspace you can add apps to
- Admin or Owner role in TrailSpark
Connecting Slack
Go to Settings > Integrations > Slack. On the Connection tab, select Add to Slack and authorize TrailSpark for the workspace you want alerts posted to. Once connected, the page shows the connected workspace name; use Reconnect if you ever need to re-authorize (for example, after removing and re-adding the TrailSpark app in Slack).
The Alerts tab unlocks once a workspace is connected.
When to Send an Alert
On the Alerts tab, the When to send an alert card lists the moments TrailSpark can post about. Turn on any combination:
| Alert | Fires when |
|---|---|
| Lead score changes | A person's score changes to a level you select (Hot, Warm, or Cold) |
| Account propensity changes | An account's buying likelihood changes to a level you select (High, Medium, or Low) |
| Newly eligible accounts | An account is first scored under a new ICP and lands at a selected buying likelihood |
| A promising account goes quiet | Activity stalls at a high-potential account |
| Buying group comes together | More of the group involved in the decision gets engaged (only shown for workspaces tracking buying groups) |
Each alert has its own channel picker, so you can send, for example, Hot lead-score alerts to one channel and buying-group alerts to another.
Routing Alerts to the Right Channel
TrailSpark decides where an alert posts using three settings, checked in this order:
- Route by ICP — a channel chosen for the account's ICP
- The alert's own channel — a channel chosen for that specific alert (in the When to send an alert card)
- Default channel — the channel you set in What the alerts look like
The first one of these that has a real channel selected wins. Anything left on its default option falls through to the next setting.
Route by ICP
If your workspace has two or more active ICPs, a Route by ICP card appears between When to send an alert and What the alerts look like. It lists every active ICP with a channel picker of its own, so you can send each ICP's alerts to its own channel — for example, an Acquisition ICP's alerts to a #trials channel and an Upsell ICP's alerts to an #upsell channel, while every other ICP keeps using the channel settings above.
Each ICP's channel picker defaults to Default routing — meaning that ICP has no override, and its alerts follow the alert-type and default channel settings instead. Pick a real channel for an ICP to route all of that ICP's alerts there, regardless of which alert type fired or what the default channel is set to.
The Route by ICP card only appears with two or more active ICPs. With a single active ICP, there's nothing to route between — alerts use the alert-type and default channel settings only.
What the Alerts Look Like
The What the alerts look like card covers the rest of the message:
| Setting | What it does |
|---|---|
| Default channel | Where alerts land unless a moment above (or an ICP) is pointed somewhere else |
| Quiet period (days) | The minimum gap between alerts for the same account, so one account can't flood the channel |
| Attributes | The account and product details included in each alert message, grouped by Account and Product |
A live Preview below the attribute picker shows exactly how the Slack message will look with your current settings and sample data.
Sending a Test Alert
Once you've saved a configuration, use Save Slack alerts followed by the test-send option at the bottom of the Alerts tab to post a sample message to Slack. You can send the built-in sample data, or pick a real account from your workspace so the test message reflects that account's actual details.
Troubleshooting
| Issue | Resolution |
|---|---|
| No Alerts tab available | Connect Slack on the Connection tab first |
| Route by ICP card is missing | Your workspace needs two or more active ICPs for the card to appear |
| Alert landed in the wrong channel | Check Route by ICP first (it wins), then the alert type's own channel, then the default channel |
| Test alert not appearing in Slack | Confirm the connected workspace is still authorized on the Connection tab, and that the channel you're checking matches the one selected in your settings |
Next Steps
- Managing Multiple ICPs — how ICPs are ordered and assigned
- Destinations Overview