The signal in Stripe

A high-value invoice failed, and Chaser, the Stripe-native failed-payment recovery tool, held it back from every automated sequence by design via routing rules held it back from every automated sequence by design. The VIP flag, set by invoice value or by a customer attribute you define, means no template touches this account.

Why it happens

Enterprise and anchor accounts fail payments for boring reasons: procurement reissued a card, a finance contact left, a credit limit moved. What they do not forgive is being dunned like a free-tier signup. The relationship is worth more than the invoice, so the play optimizes for the relationship.

What happens if you do nothing

Two failure modes, equally bad. 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.

The play, step by step

The case routes straight to the attention queue with everything an operator needs: live Stripe state, invoice history, the account's attributes, and a drafted personal note in your voice via the composer. A human decides whether to email, to ping the account's owner in your team, or to wait. The 48-hour stagnation safeguard guarantees the case cannot rot unseen: if nobody acts, it escalates to the workspace owner.

The email that works

Written by a person, signed by a person. The composer drafts it Founder-style and a human approves the send. "Saw the renewal hiccup on our side. No action needed if procurement is already on it; otherwise here is a one-click fix." Peer to peer, never collector to debtor.