Daily Kajabi churn-rescue briefing with Gmail save drafts

Every weekday at 8am in my timezone, build a Kajabi churn-rescue briefing for my retention team. The goal: surface every customer who churned or whose subscription payment is failing in the last 24 hours, draft a save email for each one in Gmail, and post a single triage thread to Slack so a CSM can review and send.

Step 1: Pull at-risk purchases from Kajabi. Call Kajabi List Purchases filtered to purchases that were deactivated, cancelled, refunded, or have a failing/past-due payment status in the last 24 hours. Deduplicate by customer (one entry per customer, keeping the highest-severity reason).

Step 2: Enrich each at-risk customer. For every customer in the list, call Kajabi Get Customer Details to fetch their name, email, and lifetime offers, and call Kajabi Get Offer Details for the specific offer tied to the failing or cancelled purchase. Estimate lifetime value from their past purchases (sum of paid amounts across their offers).

Step 3: For each at-risk customer, use Gmail Create a Draft to draft a personalized save email from me, addressed to the customer. The email should be short and warm, never discount-led. Name the specific offer they're losing access to, acknowledge what happened (failed payment vs. cancellation vs. refund), ask what changed, and offer two concrete paths: update their payment method, or pause instead of cancel. Sign it from me. Do not send the email — leave it as a draft.

Step 4: Post one Slack Bot Send a Message to a configurable retention channel (default #retention). Format:

• A header line with totals broken out by reason: failed payments, cancellations, refunds.

• One bullet per customer, grouped by reason, sorted highest lifetime value first. Each bullet shows: customer name, offer they're walking away from, lifetime value, suspected reason in plain English (for example, "card declined, 2nd retry"), and a link to the Gmail draft so the CSM can open it, edit, and hit send.

• A closing line with what to do next (review the drafts and send the ones that look right).

Deduping rule: keep a record of which customers were surfaced in yesterday's briefing and skip them in today's. Do not create a duplicate Gmail draft for a customer already drafted in the last 48 hours.

Edge case: if there are zero at-risk customers, still post a short Slack message confirming the check ran and the count is zero, so the team knows the workflow is healthy.

Configurable inputs: the retention Slack channel, the sender name/signature on the email, the at-risk lookback window (default 24 hours), and the timezone for the 8am trigger.