The two equally bad default outcomes
Automated dunning fires, and a champion at your biggest account forwards a robotic payment demand to their team. Or nothing fires, and the invoice ages silently until renewal review, when it surfaces as a surprise. VIP handling exists to prevent both.
What a VIP failed payment needs instead
- Hold automated sequences by design, set by invoice value or a customer attribute you define
- Route straight to a human with live payment state and account history attached
- A personal note from a named person (founder or account owner), not a template
- Reference the relationship; offer a call before mentioning the invoice
- A safeguard so "handle it personally" never becomes "forgot about it"
The email that works for a VIP
Written by a person, signed by a person, peer to peer rather than collector to debtor. Something like: "Saw the renewal hiccup on our side. No action needed if procurement is already on it; otherwise here is a one-click fix." Short, human, and it protects the account.
How Chaser handles VIP accounts
Chaser, the Stripe-native failed-payment recovery tool, can hold any high-value or VIP-flagged invoice back from every automated sequence and send it straight to the command center, where an operator gets a blank composer (not a template) with full context and an AI draft in your voice that a human approves. If nobody acts within the snooze window, it escalates to the account owner. See the full play at /playbooks/untouched-vip. Also read human-in-the-loop dunning for the broader approach.
