> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # When a champion leaves - Handbook Canonical URL: https://posthog.com/handbook/customer-success/champion-leaves > **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links). ## On this page - [How you find out](#how-you-find-out) - [1. Flag the account](#1-flag-the-account) - [2. Run the handover checklist](#2-run-the-handover-checklist) - [3. Find a new champion](#3-find-a-new-champion) - [4. Close the loop](#4-close-the-loop) Use this when a [champion](https://posthog.com/handbook/growth/sales/customer-journey.md#champions-and-coaches) leaves one of your accounts. To lower the risk before it happens, [multi-thread](https://posthog.com/handbook/growth/sales/risk-mitigation-and-churn-prevention.md#de-risking-common-churn-scenarios) your accounts. ## How you find out - The **People changes** [scout](https://posthog.com/handbook/customer-success/how-we-use-automation.md#managed-customer-scouts) sends you a weekly digest of the people who left your accounts. - The **Churn risk** scout creates a task when it finds a champion who left. - Your email bounces, or the champion goes quiet in your shared Slack channel. - They change their job on LinkedIn. Make sure you are connected to your champions on LinkedIn, so you see it. - They tell you. Do the handover checklist below with them before they leave, and ask them to introduce you to the person who takes over their work. ## 1\. Flag the account Do this as soon as you find out: - If no other champion is left at the customer, add the **Churn Risk** tag in [Customer Analytics](https://us.posthog.com/project/2/customer_analytics/accounts). Coaches do not count. See [when to flag an account as at risk](https://posthog.com/handbook/growth/sales/risk-mitigation-and-churn-prevention.md#when-to-flag-an-account-as-at-risk). - Add a note on the account that says who left and when, so that the next person on the account has the context. ## 2\. Run the handover checklist Things that are tied to one person break without a warning when that person leaves. Things often break on their last day, when the customer removes their accounts. Check each item below as soon as you can. You can see most of these items in Customer Analytics or in a read-only impersonation session. Follow our rules for [impersonating users](https://posthog.com/handbook/company/security.md#impersonating-users). Tell the customer what you find and let them make the changes. Do not change their setup without their consent. ### Organization owner - Check who is an owner in [**Settings** > **Organization** > **Members**](https://app.posthog.com/settings/organization-members). - An owner cannot leave an organization. Only an owner can transfer ownership or delete the organization. If the champion is the only owner, ask them to make someone else an owner before they leave. - If the only owner has already left, the customer must go through our [organization ownership transfer process](https://posthog.com/handbook/support/customer-support.md#how-should-i-handle-organization-ownership-transfers). This needs access to the old owner's email or proof that they own the domain, so it is slow. Start it early. ### Billing details in Stripe - Check the billing email in [billing admin](https://billing.posthog.com/admin/billing/customer/). If it is the champion's email, invoices and failed payment emails go to an inbox that nobody reads. - Ask the customer for the new billing contact and [update the billing email yourself](https://posthog.com/handbook/growth/sales/contracts.md#updating-the-billing-email-and-address). - Ask if the card on file is the champion's company card. Companies often cancel these cards when a person leaves. - We send billing emails to all owners and admins, so make sure that at least one owner or admin is still at the company. ### Personal API keys - Owners and admins can see every key with access to the organization in [**Settings** > **Organization** > **Security**](https://app.posthog.com/settings/organization-security#organization-personal-api-keys). Look for keys that the champion owns and that were used recently. - A [personal API key](https://posthog.com/docs/api/personal-api-keys.md) belongs to a user. When the customer removes the champion from the organization, any script or service that uses the champion's key stops working. - The most common example is [feature flag local evaluation](https://posthog.com/docs/feature-flags/local-evaluation.md). Move it to a [project secret API key](https://posthog.com/docs/api/project-secret-api-keys/overview.md), which does not belong to a person. For scopes that project secret API keys do not support yet, the customer must make a new personal API key with a person who stays. ### Integrations and data warehouse sources - Check the integrations in project settings (for example Slack) and the [data warehouse sources](https://posthog.com/docs/data-warehouse.md). - If the champion connected a tool with their own login in that tool, the connection can stop working when the customer turns off their account there. Syncs fail, and alerts stop arriving. - Ask the customer to connect it again with a service account or with a person who stays. ### Batch exports and destinations - Check the [batch exports](https://posthog.com/docs/data-pipelines/batch-exports.md) and destinations in **Data pipelines**. - If the credentials belong to the champion (for example their own Snowflake user), the exports fail when the customer removes that user. - Find out who uses the exported data. That team often depends on PostHog and is a good place to look for a new champion. ### Subscriptions and alerts - Check [subscriptions](https://posthog.com/docs/product-analytics/subscriptions.md) and [alerts](https://posthog.com/docs/alerts.md) that go to the champion's email. - If nobody gets these reports, the company stops seeing value from PostHog without anybody noticing. Ask the customer who must get them now, or move them to a team Slack channel. ### Shared Slack channel - If the champion was the only person from the customer in your [shared Slack channel](https://posthog.com/handbook/growth/sales/slack-channels.md), you have lost your main channel to the account. Add more people now. ## 3\. Find a new champion You need a champion, not a coach. The test is the same as always: when they say something must happen, it happens. A friendly power user who cannot make decisions is a coach. Where to look: - **The people who use PostHog now.** Customer Analytics shows the active users on the account. Look for the people who make insights and dashboards, own feature flags, or write SQL. - **New owners and admins.** The People changes scout creates a `New stakeholder:` task when one joins. - **The people who own the items from the checklist.** The new owner, the new billing contact, and the team that uses the exports all have a reason to talk to you. - **The person who takes over the champion's role.** A warm introduction from the champion is the best way in. Ask for it before they leave. - **Someone more senior.** If you cannot find anybody, email a senior person, even if they do not use PostHog. They can tell you who owns PostHog now. How to approach them: - Start with something useful, not "your champion left." The checklist gives you good reasons. For example, "Your feature flag local evaluation uses an API key that stops working when your previous admin's account is removed. Here is how to move it to a project secret API key." - Offer a call to walk through their setup. A new owner often does not know why the company chose PostHog. Show them what the team uses, what it costs, and what it replaced. A [health check](https://posthog.com/handbook/customer-success/health-checks.md) is a good structure for this call. - See [getting people to talk to you](https://posthog.com/handbook/account-management/getting-people-to-talk-to-you.md) for more tactics, especially [which channel and which person](https://posthog.com/handbook/account-management/getting-people-to-talk-to-you.md#which-channel-and-which-person) and [asking for introductions](https://posthog.com/handbook/account-management/getting-people-to-talk-to-you.md#asking-for-introductions). When you find them, record them as a champion or a coach, with what they can and cannot decide. Then build a second champion in a different team, so that the next departure does not put the account at risk again. ## 4\. Close the loop - Remove the **Churn Risk** tag when you have a relationship with a new champion, nothing from the checklist is still open, and no other reason on the [at-risk list](https://posthog.com/handbook/growth/sales/risk-mitigation-and-churn-prevention.md#when-to-flag-an-account-as-at-risk) applies. - If the account churns anyway, do a [churn retro](https://posthog.com/handbook/customer-success/customer-churn-retros.md) and record which part of this process came too late.