Retention
Live in Churnkey
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.
Routing dunning to the billing owner outperforms end-user delivery in B2B recovery
B2B recovery campaign outcomes across the platform
Repeated observed effect; controlled validation in progress.
How we grade evidence →Event trigger · Edition 1 · June 2026
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 this for your business
Want to run Bill the Right Person for your business? Connect the Churnkey MCP to your favorite AI agent. It reads your own usage and billing data and recommends the growth and retention plays most likely to move your LTV—starting with whether this one fits.
npm install -g @churnkey/mcpThis tactic maps to a Churnkey feature—the same play, running in production.
See it in action in ChurnkeyMore in Retention
All tactics →
Dunning SMS
Add SMS to the dunning sequence—a failed payment is time-boxed, and a text reaches the subscriber inside the window in a way email increasingly does not, with the gap widest at consumer membership orgs.
View tactic
First-Screen Save Offer
Put the best save offer on the first screen of the Cancel Flow, not after the exit survey—every screen before the offer sheds the very subscribers the offer could save.
View tactic
Hidden Rescue Plan
An unlisted, cheaper plan offered only inside the Cancel Flow—right-size the subscriber to a plan their usage justifies instead of discounting the one it no longer does.
View tactic
Put the evidence to work.
The same dataset behind these tactics powers Churnkey's retention products. See what it finds in your subscription data.
