DEV Community

Swipe Again for Swipe Again

Posted on

Two Desks, One Overdue Account: Where Dunning Ends and Collections Begins

Imagine two desks in the same small office, both looking at the same overdue account on the same morning. On the first desk sits a subscriber who has paid happily for fourteen months, whose card was replaced after a bank merger, and who has not yet noticed anything is wrong. On the second desk sits an account that signed up, consumed a month of service, disputed the first charge, and vanished. Treating those two files with the same voice, the same urgency, and the same threats is not firmness. It is a category error, and customers can feel it immediately.

That category error is the subject of a field guide to separating dunning from collections in practice, and its central claim is simple enough to tape above a monitor: dunning is a service conversation with someone who intends to stay, while collections is a debt conversation with someone who has already left in every way that matters. The tools overlap — email, reminders, deadlines — but the relationship underneath them does not, and the relationship is what decides tone, timing, and how much pressure is honest.

Start with intent. A dunning case begins with a failed payment, not a refusal to pay. The overwhelming majority of subscription failures are accidents of timing, expiry, replacement cards, or bank caution. The customer has made no decision about you at all. A collections case, by contrast, begins after a decision, or after silence so prolonged that the decision can fairly be inferred. Mixing the two means the accidental case receives language written for the deliberate one, which is how loyal subscribers end up reading words like delinquency in the first email after a bank quietly reissued their card.

Timing tells the same story. Dunning works in days, close to the failure, while the service relationship is still warm and the fix is still small: update a card, confirm a charge, wait for payday. Collections works in weeks and months, after the service has ended, when the question is no longer continuity but settlement. A team that starts collections language on day two has nowhere left to escalate, and a team still sending gentle dunning notes on day ninety is spending goodwill and compute on an account that needed a different process entirely.

There is a practical test any operator can run this week. Pull the last fifty payment-failure messages your system sent and sort them into two piles by a single question: does this message assume the reader wants to keep the subscription? If the answer is unclear, the message belongs to neither desk — it is a template doing two jobs badly. Rewrite it twice, once for each pile, shorter both times. The dunning version names what happened, offers one clear action, and states a calm, honest date. The collections version, reserved for genuinely ended accounts, can be firmer because firmer is truthful there.

None of this is softness for its own sake. Sorting correctly is also how the numbers stay honest. Recovery rates mean little when accidental failures and ended accounts are averaged together; a team can look excellent at dunning simply because its queue is full of easy credential fixes, or look terrible because dead accounts were never handed over. Two desks means two scoreboards, and two scoreboards mean you finally know which problem you actually have.

Keep the desks separate, in language, in timing, and in counting. The subscriber on the first desk will repay the courtesy with years of renewals. The account on the second desk deserves a clear, dignified process too — just not the same one.


Published by Swipe Again — failed payment recovery at a flat $179/mo.

Top comments (0)