DEV Community

Swipe Again for Swipe Again

Posted on

A Cadence Is a Promise Kept at Intervals

Ask a room of subscription operators how many times they contact a customer after a failed payment, and most will answer with a number. Ask when, and the room goes quieter. Yet customers do not experience a number. They experience intervals: a message the same evening, then silence for a week, then three messages in two days as a deadline approaches. That rhythm — not the count — is what teaches a subscriber whether your billing process is calm and deliberate or anxious and improvised. A cadence is a promise kept at intervals, and planning it means designing the rhythm on purpose.

That is the working idea behind recharge dunning planned as a cadence, not a retry count: lay the whole sequence out on one calendar, per failure type, before any of it fires. When the sequence exists as a picture rather than as settings scattered across a tool, its faults become visible at a glance. Gaps where a payday will pass unnoticed. Clusters where a retry and two emails land on the same morning. A final notice that arrives after the access it warns about has already ended, which is not a notice at all, just an apology with the wrong tense.

A useful way to build the calendar is to anchor it to the customer's life rather than to the failure timestamp. The failure happened when it happened — often at an hour chosen by a batch process, bearing no relation to when the subscriber is awake, paid, or able to act. The first contact can stay close to the failure; clarity early is kindness. But retries, especially for insufficient-funds cases, earn their keep by landing where money actually arrives: after common paydays, at hours when a person can respond to a bank prompt, never in a tight burst that spends attempts before conditions change.

Different failures also deserve different rhythms, and the planner is where that stops being a slogan. An expired or replaced card can be resolved the moment the customer acts, so its cadence should be short, clear, and built around prompt re-attempts once new details land. A soft decline needs spacing and variation. A case that will end in cancellation needs a rhythm that slows down, states dates honestly, and closes with dignity rather than accelerating into a wall of reminders in its final week. One cadence for every cause is not consistency; it is inattention, printed on a calendar.

Quiet days deserve the same deliberate design as contact days, because silence is also a message. A pause after a customer has promised to update a card on Friday tells them you believed them. A pause while a bank hold clears tells the issuer nothing frantic is coming. Even the gap before a final notice does work: it gives a busy person one last ordinary week in which to act before the tone changes. When teams plan only the touches and leave the gaps to accident, the gaps still communicate — they just communicate whatever the tool's defaults happened to produce, which is rarely patience and never gratitude.

Finally, a planned cadence can be tested, and an unplanned one can only be endured. With the sequence written down — attempt days, contact days, quiet days, closing day — a team can change one interval at a time and read the result honestly: did moving the second retry change recovery, or merely move it? Without the plan, every outcome is weather. With it, timing becomes what it should have been all along, a hypothesis the calendar lets you keep, test, and keep again.

Draw the calendar. Per cause, on one page, with the quiet days marked as deliberately as the loud ones. Your subscribers will never see the plan, but they will feel it, in the difference between a process that nags and a process that keeps its word.


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

Top comments (0)