Mondays · 8:00
Check account health weekly
A weekly health score per customer, with the reason behind each.
Churn risk agentHear the warning while there is time.
Each weekday it looks for signs an account may leave: no reply, a drop in use, a complaint, a sponsor change. It tells the owner in Slack with the evidence.
Your first signup includes $50 in free credits.
Weekdays · 9:00
Spot churn risk early
- Reads
- Customer sheet, Gmail
- Grows
- A list of at-risk accounts
- Lands in
- Slack
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
Every weekday at 9, look for customers with warning signs: no reply in two weeks, a drop in use, or a complaint. Tell the account owner in Slack with the evidence.
TulipFarm
I made an agent called Churn watch and a weekday 9:00 schedule. It reads your sheet and Gmail. Posting to Slack asks you first. Activate it?
ActivateEdit first
One morning, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Weekdays at 9:00
Run startedStarted - Reads
Customer rows and usage columns in Sheets
30 accounts - Reads
Recent threads in Gmail
35 threads - Checks
Any account matching a warning sign?
3 flagged - Asks first
Post the flags to Slack
Approved - Posts
Message in Slack
Delivered 9:03Completed
What the owner sees in Slack.
Who, why, and one thing to do today.
#successChurn watch APP · 9:03
3 accounts need a look
Customer A · quiet
- No reply to 2 emails in 15 days.
- Do: call the main contact.
Customer B · use is down
- Active users fell by half this month.
- Do: ask what changed.
Customer C · complaint
- Email on Oct 15 mentions switching.
- Do: reply today.
What gets planted.
Three parts you own and can change at any time.
- Agent
Churn watch
Your list of warning signs.
- Table
Accounts
Usage and last-contact columns.
- Workflow
Weekdays 9:00
Runs with your own access.
Uses
- Google Sheets
- Gmail
- Slack
Add if you use it
- PostgresMCPPostgres
HubSpot- ZendeskMCPZendesk
It reads quietly. It asks before it acts.
Reads without asking
- Your customer sheet
- Recent customer emails
- Your warning-sign rules
Asks you first
- Posting to Slack
- Any email to a customer
It uses your own connections, so it never sees more than you can.
Grow it your way.
Add support tickets
Read open tickets from Zendesk through a Custom MCP connection.
Weekly only
Post one weekly list instead of daily alerts.
Draft the save
Draft a check-in email for each flagged account.
Questions, answered.
How does it decide a customer may leave?
By the signs you list, such as no reply, falling use or a complaint. It shows the evidence so you can judge.
Where does usage data come from?
Your sheet or table, or a database through a Custom MCP connection. You review each tool before an agent can use it.
Will it be wrong sometimes?
Yes. A flag is a prompt to look, not a verdict. Tell it when a flag was wrong and adjust the rules.
Mondays · 9:00
Check in on customers
Drafts a personal check-in for each customer who is due one.
60 days before renewal
Never miss a renewal
Spots renewals coming up and drafts the check-in before each one.
Tables
Catch it before they leave.
Public beta, open to everyone. Your first signup includes $50 in free credits.