How we handle GDPR data-subject requests on a deadline
Legal
A daily cron scores accounts on leading churn signals across product usage, support, and billing, then posts a ranked at-risk list to Slack with a reason and a suggested next step for each.

Churn is usually visible before it happens. Usage tapers off, support threads get more frequent and more frustrated, a payment fails, a renewal approaches. The signals are there, but they sit in different systems, and no one is watching all of them at once. By the time an account cancels, the warning signs had been accumulating for weeks.
We run a churn-risk agent on Kortix that reads those signals every day and posts a ranked at-risk list to our customer-success Slack channel. It only reads customer data; the single output is the Slack post. This is how we watch our own accounts.
The signals that predict churn live in separate systems: product usage in Postgres, support friction in Plain, payment health in Stripe, renewal dates in billing. Each one is a partial view. An account with declining usage might be fine; an account with declining usage, a rising support load, and a renewal next month is not.
The common approaches don't combine them. A usage dashboard shows one signal and leaves the reader to correlate the rest. A health score baked into one tool only sees that tool's data. Manual account reviews are thorough but happen quarterly, long after the signals first appeared, and depend on someone remembering to look.
On Kortix, a daily cron triggers an agent. It spawns an isolated session (a cloud sandbox) with read-only access to Postgres, Plain, and Stripe, scores every account on leading churn signals — declining usage, rising support friction, missed or failed payments, an upcoming renewal — and posts a ranked at-risk list to the customer-success Slack channel, with the reason for each account and a suggested next step. It writes nothing back to customer systems.
Open your Kortix workspace, start a new session, paste this prompt and send it. The agent writes the agent file, the churn-signals skill and the daily trigger, and opens a change request for you to review. Prefer clicks? Choose Use this template instead.
Set up a daily churn-risk agent in this workspace.
Create the agent agents/churn-risk.md. Its job is to score every account for churn risk and post a ranked list. It may use the Postgres, Stripe and Slack connectors and the Plain API key. It only reads Postgres, Plain and Stripe.
Create the skill skills/churn-signals/SKILL.md with these rules:
Add a cron trigger daily-churn-scan to kortix.yaml. It runs the churn-risk agent every day at 06:00 UTC with the prompt "Load the churn-signals skill and run one complete churn-risk scan."
Tell me which of these connectors are not connected yet.
Open a change request with all of it. Do not merge it.
Open Connectors in your workspace and connect your product database, Stripe and Slack, and add your Plain API key as a secret. Credentials are brokered server-side and never enter the agent's machine.
Reads product usage trends, read-only.
Reads support thread volume and tone, read-only.
Reads payment status and renewal dates, read-only.
Posts the ranked at-risk list with a next step each.
Merge the change request, then start a session with the churn-risk agent and send this prompt. Check the ranking against what your team knows before you let the schedule take over.
Run one churn-risk scan. Read only.
The change request added this trigger to kortix.yaml. From now on the agent
runs every day at 06:00 UTC, each run in a new session on its own cloud computer. To change the time, edit the cron line, or open
Triggers in the workspace.
triggers:- slug: daily-churn-scan name: Daily churn-risk scan on: cron: "0 0 6 * * *" run: agent: churn-risk prompt: Load the churn-signals skill and run one complete churn-risk scan.The agent reads Postgres, Plain and Stripe and writes only the Slack post. It sends no email, replies to no ticket and changes no subscription. A person on customer success decides what to do with each account.
Each run ends with one message in the channel. This is what a run looks like in the session:
Flagged 8 accounts. 2 are highest risk: usage down 34% in 30 days, an escalated support thread, and a renewal in the next 30 days. For both, the suggested next step is a renewal conversation this week.
Once it works, paste any of these into the same session.
Send each flagged account CSM a Slack DM with the reason and the next step, in addition to the channel post.
For each account that renews in the next 30 days, add its usage trend and open support threads to the post.
Once a month, list the accounts that churned and show which signals fired for them in the weeks before, so we can tune the rules.
The agent reads across every customer system, so its access is scoped and one-directional:
Churn signals that used to sit in four separate systems now arrive as one ranked list in the channel where the team already works, each account carrying the reason it surfaced and a suggested next step. The agent only reads; the people decide what to do about each account.