Skip to main content
Intempt

Celebrate the wins and flag the risks in the same Slack channel

Revenue events deserve visibility, and at-risk events deserve urgency - most teams handle neither well without a dedicated workflow. This posts both, formatted for the moment.

Sellrevops-automatorB2BSaaSEcommerceStandard3 steps2 outputs
1
2
3
Content Asset Workflow
Run this recipe

What it does

Posts celebration-grade Slack messages on key revenue events (deal won, new subscription, expansion) and operational Slack messages on at-risk events (payment failed, churn), through a single configurable workflow.

You get

revenue wins and risk alerts posted to Slack as they happen

How it works

1

Build Celebration Slack Content

create_slack_content

Generate Slack message content for revenue celebrations. Variants: (a) deal_won โ€” include rep name, account, ARR, contract length, with a ๐ŸŽ‰ emoji and team @mention; (b) subscription_created (B2B) โ€” first paying customer of the month gets a fanfare message, subsequent ones get a compact one-liner; (c) order_placed (ecommerce) โ€” large-order threshold (top 5% of order values) gets celebration, normal orders silent; (d) expansion โ€” upsell amount, customer name, AE who closed. Tone: warm, brief, team-celebratory.

Produces:Content Asset
2

Build Operational Alert Content

create_slack_content

Generate Slack message content for operational alerts (different channel from celebrations). Variants: (a) payment_failed โ€” customer name, plan, MRR at risk, CSM owner @mention; (b) subscription_canceled with reason; (c) high-value-cart_abandoned (B2C, single cart value > threshold). Tone: terse, action-oriented, who-needs-to-respond clear.

Produces:Content Asset
3

Build Notification Workflow

Create Workflow

Create a workflow firing on revenue events. Step sequence: (1) classify event type โ€” celebration (won/created/expansion) vs. operational (failed/canceled/at-risk); (2) for celebrations, post celebration content to #wins channel with deal/account context; (3) for operational, post alert content to #revenue-ops with rep/CSM @mention; (4) for high-value events (top-quartile ARR), additionally DM the CEO/CRO and AE manager (configurable threshold); (5) suppress notifications during off-hours unless explicitly tagged urgent (don't ping the team at 2am for routine wins).

Produces:Workflow

Ready to run this recipe?

Tell Blu what you need. It builds the segment, content, journey, and dashboard in minutes.

Sign up free

Hire the team that reclaims what your GTM stack is leaking.

You set the strategy. Agents run the plays. Seven AI agents across design, marketing, sales, and analytics. One customer context, tracked from first pixel to final dollar.

Start for free
Slack Purchase and Risk Notifications | Intempt