Price change alerts in Slack that nobody mutes

Connect your Slack workspace once, then decide which alerts go to which channel and which ones are urgent enough to interrupt someone. A below-MAP listing can post to a channel the moment it is detected, while ordinary competitor moves collect into a 9am digest. The routing is the whole point: an alert channel that fires 300 times a day gets muted within a week, and then nobody sees the one that mattered.

The arithmetic that kills most alert channels

Work it out before you configure anything. Take 2,500 monitored products with six competitor listings each. That is 15,000 observations per refresh cycle, and on twice-daily refresh, 30,000 a day. If two percent of those observations are a price change, that is 600 changes a day. Post each one and you have made a firehose. Post nothing and you have bought a dashboard nobody opens.

The workable middle is a severity model. Interrupt for the small number of events where a human should act inside the hour. Batch everything else into a digest people read with coffee. A sensible target is interrupting on a small fraction of your daily events and batching the rest.

How to route price change alerts in Slack by severity

How to connect Slack

1. 1

   Install the app in your workspace

   From Integrations, choose Slack and approve the install. Slack shows exactly what the app can do. A workspace admin may need to approve it depending on your workspace settings.

2. 2

   Pick your channels

   Choose a default channel, then add others. A common setup is three: pricing, MAP violations, and an operations channel for data health. Private channels work once the app is invited to them.

3. 3

   Set thresholds

   Define what counts as a price move worth reporting, in percent or dollars, and set it per product group. A 2 percent move on a 900 dollar item deserves more attention than 2 percent on a 9 dollar one.

4. 4

   Write routing rules

   Route by alert type, severity, product group, brand or competitor. A rule can send Voltbay moves to one channel and everything else to another, because the person watching your closest competitor is often not the person watching the rest.

5. 5

   Schedule the digests

   Choose a time and a day for each digest, per channel. Digests summarise the batched alerts with counts and the biggest movers first, and link into the app for the detail.

What data flows in each direction

Keeping the signal high over time

• Group related alerts. Twelve variants of one product moving together post as one message, not twelve.
• Set thresholds per product group. One global percentage always over-reports cheap items and under-reports expensive ones.
• Suppress repeats. A competitor that toggles a promotional price on and off should not generate an alert every cycle.
• Separate operations from pricing. Data health belongs with whoever fixes it, not with whoever prices.
• Review the channel monthly. If nobody has acted on an alert type in a month, move it to the digest. Muting is what happens when you skip this.

What the Slack integration does not do

• It does not read your workspace messages, files or channel history.
• It does not post to direct messages unless a user opts in for their own alerts.
• It does not let anyone approve or push a price change from Slack. Price changes happen in the review queue, with the guardrails described in repricing.
• It does not replace email alerts. Both run at once, and the weekly digest is available on either.
• It does not carry evidence screenshots into Slack for MAP alerts. The message links to the evidence record instead, so the audit trail stays in one place.

If you would rather route alerts into your own systems, webhooks and the REST API deliver the same events with the full payload, on every plan.