--- title: "Bill the Right Person — Retention Growth Tactic" description: "In B2B subscriptions the person who sees the dunning email is often not the person who owns the card—declare a billing contact and route recovery there, instead of letting payment-failure messages die in an end user’s inbox." canonical: "https://churnkey.co/growth/library/bill-the-right-person" category: "growth" related: - /growth/library/index.html.md - /growth/library/methodology.html.md - /feature/payment-recovery/index.html.md last_updated: "2026-06-09" --- # Bill the Right Person In B2B subscriptions the person who sees the dunning email is often not the person who owns the card—declare a billing contact and route recovery there, instead of letting payment-failure messages die in an end user’s inbox. - **Stage:** Retention - **Evidence grade:** moderate (directional, still in validation) - **Evidence:** Routing dunning to the billing owner outperforms end-user delivery in B2B recovery - **Trigger type:** Event - **Channels:** email ## What is it? In a B2B subscription, the account belongs to a team and the card belongs to one person on it—often someone in finance or operations who never logs into the product. Default dunning goes to the account email, which usually means an end user: someone who sees a payment-failure notice they have no authority and no card to act on. The message dies in that inbox, and the subscription dies with it. This tactic separates the two roles. A billing-contact API lets the org declare who actually holds the budget, and recovery campaigns route to that person. The end user keeps using the product; the person who can fix the payment is the one asked to fix it. ## What the evidence shows Across B2B recovery campaign outcomes on the platform, recovery improves when dunning reaches a billing owner rather than an end user. The mechanism is unsurprising—a payment-failure email is only actionable by someone with the card—but the data bears it out, and the effect concentrates where the role split is sharpest: B2B orgs on seat-based plans, where the payer and the users are almost never the same person. The grade is moderate for an honest reason. The direction is consistent, but orgs that adopt billing-contact routing often tune campaign timing in the same motion, and the routing effect has not yet been fully isolated from those timing changes. The finding to act on is directional: reaching the budget owner beats reaching the end user. ## How it runs In production, the org sets the billing contact explicitly through the API—an affirmative declaration, never an inference from email domains or job titles. When a payment fails, the recovery campaign routes to that contact: the dunning sequence, the payment-update link, the receipts of resolution. When no billing contact is declared, the campaign falls back to the subscriber of record, so no account goes unmailed. The end user is not cut out of the loop entirely—they receive one courtesy notice that billing was contacted, so a sudden suspension never arrives as a surprise. The billing contact’s details are used for recovery and nothing else; the address the org handed over to fix payments does not become a marketing list. ## Run it with the Churnkey MCP This tactic runs via the Churnkey MCP. Connect it to your favorite AI agent and it reads your own usage and billing data, then recommends and runs the plays most likely to move your LTV — starting with whether this one fits. **Trigger:** A subscription payment fails for an account with a declared billing contact. **Surface:** Recovery email sequence delivered to the declared billing contact, with a payment-update link. **Guardrails:** - Declaration: the billing contact is set explicitly by the org via the API—never inferred from email domains or titles. - Transparency: the end user receives one courtesy notice that billing was contacted, so suspension never arrives unannounced. - Scope: billing-contact data is used for recovery messaging only, never for marketing or other outreach. - Fallback: when no billing contact is declared, recovery routes to the subscriber of record so no failure goes unmailed. **Evidence:** Routing dunning to the billing owner outperforms end-user delivery in B2B recovery, measured on recovery campaign outcomes across the platform. The effect concentrates in B2B orgs with seat-based plans, where payer and user are rarely the same person. Directionally consistent, though not yet isolated from campaign timing effects. **How to run it:** 1. Add a billing-contact field to the subscription record, settable only through an explicit API call from the org. 2. Route the dunning sequence and payment-update link to the billing contact whenever one is declared. 3. Send the end user a single courtesy notice that billing was contacted about the failed payment. 4. Fall back to the subscriber of record for any account without a declared billing contact. 5. Compare recovery rates for billing-contact-routed accounts against subscriber-of-record accounts, holding campaign timing constant. Install the MCP server: ```bash npm install -g @churnkey/mcp ``` The full reference is in the [Churnkey MCP docs](https://docs.churnkey.co/data-integrations/mcp). ## Related - [Growth Tactics Library](/growth/library/index.html.md) — The full register of graded growth plays. - [How Tactics Are Graded](/growth/library/methodology.html.md) — The four-grade evidence ladder behind this grade. - [Payment Recovery](/feature/payment-recovery/index.html.md) — The Churnkey feature this tactic maps to in production.