Paid users going quiet
Paying users who used to log in regularly and have not shown up for a month, so you can reach them before they cancel.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Install now1 step Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Build the silent paid-user list
Install nowBlu builds Segment
About this recipe
When to use it
Silence is the leading indicator of churn, and it shows up weeks before the cancellation does. This segment flags previously active paid users who've gone silent in the last month, while there's still a window to win them back.
What it delivers
Segments previously active paid users who have gone silent over the last month, isolating the earliest reliable churn signal for proactive outreach.
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 users who used to log in regularly and have not shown up for a month, so you can reach them before they cancel.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
- 01Segment
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Build the silent paid-user listBuild a segment of users named "Churn Risk Users". A user is in the segment only when all of these are true: - they did the Session start event 5 or more times between 60 and 90 days ago - they did not do the Session start event in the last 30 days - their Plan attribute is not "free"Segment
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /churn-risk-users in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyAccounts at churn riskPaying accounts the health score has flagged as at risk, with no renewal deal in flight, so your CSMs can step in before they leave.View recipe Sid ChaudharyHealthy accounts with no open dealCustomer accounts with no open deal and account-level health attributes, plus per-user recent session activity, so AEs can review expansion whitespace.View recipe Sid ChaudharyDiscount-only buyersCustomers who have never bought anything without a discount code, so you can keep them out of full-price campaigns and protect your margin.View recipe 