Skip to main content
Intempt
Coming soon

Revenue notifications in Slack

Posts revenue wins to one Slack channel and at-risk events to another through a configurable workflow. Notifications are static channel posts, with no dynamic owner mentions or DMs.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

Coming soon

3 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.

  1. 1

    Write the celebration posts

    Coming soon

    Blu builds a step

  2. 2

    Write the operational alerts

    Coming soon

    Blu builds a step

  3. 3

    Route wins and problems apart

    Coming soon

    Blu builds a step

About this recipe

When to use it

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.

What it delivers

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.

How you prompt this

Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.

Tell Blu Agent what you want

“Posts revenue wins to one Slack channel and at-risk events to another through a configurable workflow. Notifications are static channel posts, with no dynamic owner mentions or DMs.”

recipe.md preview

Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.

Sign up to read the full recipe.md and run it with Blu Agent.

Sign up to see the full recipe

Inputs & outputs

What the recipe needs before it runs, and what it leaves in your workspace.

Inputs

  1. Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.

Outputs

    How the recipe runs

    Blu follows the steps in order and shows you each one before anything goes live.

    1. 01Write the celebration postsGenerate 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 started (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.
    2. 02Write the operational alertsGenerate 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-Abandoned cart (B2C, single cart value > threshold). Tone: terse, action-oriented, who-needs-to-respond clear.
    3. 03Route wins and problems apartCreate 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). Use the result of "Write the celebration posts", "Write the operational alerts".

    Install Intempt and run it

    1. 1

      Sign up

      Create a free Intempt workspace.

    2. 2

      Connect your data

      Add the sources this recipe reads from.

    3. 3

      Ask Blu

      Type /slack-purchase-notifications in Blu once this recipe is live there.

    4. 4

      Review and approve

      Blu builds each step and waits for your OK before anything goes live.

    Related recipes

    Intempt TechnologiesDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Intempt TechnologiesPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Intempt TechnologiesReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe

    More recipes by Intempt Technologies

    Discovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Post demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Product swap in a sceneReplaces the product in a shot you already have with a different one, keeping the scene, lighting and shadow the same.View recipe

    Got a play worth sharing?

    Publish it to the Intempt Collective Marketplace and earn when other teams run it.

    Submit a recipe