Skip to main content
Sign up
Coming soon

Paying accounts going quiet

Large paying accounts where nobody has logged in for a month, the clearest detectable churn signal, checked in on personally and flagged to the retention team before it's too late.

Authored by Intempt Technologies

Recipe curators

Agentic workflow

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

  1. 1

    Build the at-risk account list

    Blu builds Segment

  2. 2

    Draft a personal check-in

    Blu builds email html

  3. 3

    Alert the retention team

    Blu builds slack

Leaves behind Segment email_plain slack

About this recipe

When to use it

By the time a churn risk shows up on a renewal call, it's already too late to fix. This segment flags active accounts whose health is already deteriorating, while there's still time for a CSM to step in.

What it delivers

Builds a live segment of active accounts showing measurable health deterioration, so CSMs get a standing intervention list instead of finding out at renewal time.

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

“Large paying accounts where nobody has logged in for a month, the clearest detectable churn signal, checked in on personally and flagged to the retention team before it's too late.”

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

  1. 01Segment
  2. 02Email plain
  3. 03Slack

How the recipe runs

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

  1. 01Build the at-risk account listBuild a segment of accounts named "Accounts At Churn Risk". An account is in the segment only when all of these are true: - its employees attribute is 100 or more - the users in the account together did not do the Session start event in the last 30 daysSegment
  2. 02Draft a personal check-inGenerate a plain-text email for the accounts in "Accounts At Churn Risk" written as a personal note from their customer success manager, asking how things are going and offering a quick call. Three sentences, warm and personal tone, no product pitch, no discount language. Use the result of "Build the at-risk account list".Email content
  3. 03Alert the retention teamGenerate a Slack message to the retention team channel For each account in "Accounts At Churn Risk", name the account and its employees count, so the team can prioritize outreach before renewal conversations start. Use the result of "Build the at-risk account list".Slack message

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 /accounts-at-churn-risk 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 TechnologiesFirst-Day High-Intent VisitorsBrand-new visitors already clicking around heavily on their first day, surfaced to sales as a hot-lead draft with a ready-to-send push nudge back to the site.View recipe Intempt TechnologiesQuiet Returning VisitorsVisitors who keep coming back without ever clicking anything, with a push nudge drafted and a note drafted for the content team about a possible low-interaction signal.View recipe Intempt TechnologiesExpansion whitespace accountsEstablished accounts whose users log in constantly, checked in on by email and flagged to account executives to review for expansion whitespace.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 Recipe Marketplace and earn when other teams run it.

Submit a recipe