What you will have at the end
Every Monday, one message. The two or three customers who went quiet, failed a payment, or are waiting on you, each with the likely stall and a draft in your voice. Nothing goes out until you say so.
1. Add the integrations
Stripe and PostHog are not first-class connectors yet, so add each one as a custom integration: open /dashboard/integrations, choose Add integration, and paste the service's MCP endpoint.
- Stripe, with read scopes. June reads subscriptions, failed payments and cancellations. It never touches a charge.
- Your analytics (PostHog today). June reads last-seen per customer. That is the only property it needs.
Each integration is listed on the same page with a tool count; its own page lists the tools. Remove one and June loses access to it, saved tools included.
2. Tell June what "stuck" means here
Say it in plain words, once. For most small product businesses it is something like:
A paying customer counts as quiet after 21 days without a login. A failed payment counts after the second retry.
June says back how it will read them. Change a number any time by saying so.
3. Choose the mandate
June drafts, you send. Payment-failed nudges and cancellation win-backs both come to you first; nothing goes out on its own.
4. First run
Ask June for a Monday schedule and to turn on its integrations toolset; without it the run cannot read Stripe or PostHog. The first readout arrives the next Monday at the time you pick. It covers the last 30 days so you start with the current picture, not an empty one.
5. Adjust
The two most common tweaks: shorten the quiet window for a product people use daily, and exclude trial accounts so the list is only people who have paid.