Skip to main content
Sign up
Coming soon

Paying users going quiet early

Paying customers who have stopped logging in recently, nudged with a feature reminder and flagged to customer success before they slide into real churn risk.

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 low-engagement list

    Blu builds Segment

  2. 2

    Send a feature reminder

    Blu builds email html

  3. 3

    Flag to customer success

    Blu builds email html

Leaves behind Segment email_html email_plain

About this recipe

When to use it

Disengagement is the leading edge of churn, and it starts well before a cancellation event. This segment buckets paying customers by early disengagement signals so intervention can happen while they're still on the books.

What it delivers

Segments paying customers showing early disengagement signals, using bucketed engagement levels to isolate the cohort at risk before churn actually occurs.

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

“Paying customers who have stopped logging in recently, nudged with a feature reminder and flagged to customer success before they slide into real churn risk.”

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 html
  3. 03Email plain

How the recipe runs

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

  1. 01Build the low-engagement listBuild a segment of users named "Paid Users: Low Engagement". A user is in the segment only when all of these are true: - their Plan attribute is not "free" - their Plan attribute is not "trial" - they did not do the Session start event in the last 14 daysSegment
  2. 02Send a feature reminderGenerate a designed marketing email for the users in "Paid Users: Low Engagement" reminding them of one feature that made them sign up in the first place. Three sentences, friendly and low-pressure tone, no discount language, one button linking back into the product. Use the result of "Build the low-engagement list".Email content
  3. 03Flag to customer successGenerate a plain-text email to the customer success distribution list For each user in "Paid Users: Low Engagement", name their email address, so the team can check in before this turns into real churn risk. Use the result of "Build the low-engagement list".Email content

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 /paid-users-low-engagement 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 TechnologiesPaying accounts going quietLarge 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.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

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