Urgent.News

What's breaking now, across thousands of outlets.

Tech

Collections Calls Work on Businesses. Dunning Works on Subscribers.

A collections call works because the person answering owes you money and knows it. There is an invoice, a purchase order, a relationship with a credit limit attached. The call is awkward, but the obligation is not in dispute. Almost everything collections does well — the firm tone, the escalation ladder, the sense that this is now a formal matter — depends on that shared understanding. A…

A collections call succeeds when the individual being contacted owes you money and acknowledges it. There is documentation, such as an invoice or purchase order, indicating the debt. The interaction feels formal, but the debt remains undisputed. Collections excels in maintaining a stern tone, employing an escalation process, and conveying the seriousness of the situation.

However, when a customer faces a declined payment card, their relationship with the company is entirely different. They were unaware of the issue; the bank declined the transaction for reasons unrelated to the customer's financial standing. Introducing formal, escalating, and accusatory collection tactics at this point does not recover the payment.

Instead, it makes a satisfied customer realize that your company is not an enjoyable entity to owe money to and transforms a billing mistake into a cancelation decision they never intended. The boundary between dunning and collections blurs, and it is essential to draw a clear line between the two. Dunning encompasses all interactions while the relationship is intact and the failure is presumed accidental.

This includes retrying at the appropriate time, sending clear emails that enable swift card updates, and providing a grace period that aligns with the product's actual usage cycle. Collections commence when the failure is considered deliberate or the relationship ends. Regrettably, this presumption is inaccurate for subscription businesses often enough to make whole recovery strategies costly.

Three practical distinctions arise from drawing this line. First, the tone of dunning emails can be warm without appearing weak. For instance, "Your card was declined; here is the one-click fix. Your account remains active until Friday" is more effective than "FINAL NOTICE" language directed at debtors. Customers are not evading payment; they are customers encountering a logistical challenge.

Second, timing for escalation varies. Collections follow a schedule set by the creditor. Dunning should escalate based on the nature of the decline: insufficient funds waits for payday patterns, a generic decline requests a fresh review of the invoice before any retry, and an expired card warrants a message, not a retry. Lastly, the exit strategy differs.

Collections conclude with write-offs and agencies. Dunning should ideally end with a courteous pause. Customers who leave due to a billing issue and are treated well are likely to return, and their return rate surpasses any winback campaign targeting disgruntled former customers. Drawing a precise line between dunning and collections is crucial.

Being soft with money is not necessary; clarity in the dunning sequence is the key. The firmest aspect of a good dunning sequence is its clarity regarding what failed, the next steps, the exact timeline for access changes, and how customers can disregard the issue if they have already resolved it. Clarity conveys firmness without resorting to threats.

Companies that recover the most failed payments usually do so with the most considerate sequences rather than the most aggressive ones. They are the ones whose sequences are perceived as helpful by a reasonable person, sent at moments suggested by the bank's response, and halted once payment is received. If your current process originated from B2B collections or a template created by someone envisioning a debtor, reassessing it through the eyes of your best customer is beneficial.

Mid-workday, when a card declines due to an unseen reason, and the customer must decide in four seconds whether your email is help or hassle – that single decision determines whether recoverable payments come from that account.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

I built Plavio — a free streaming app for Android and Android TV

Hi everyone. I'm the developer of Plavio, a streaming app for Android phones and Android TV. The Plavio family Plavio is a small family of pieces that work together: Plavio app — the interface and…

  • Plavio is a free streaming app for Android and Android TV.
  • Developed with slow network connections in mind.
  • Clean interface with no ads, shared account and library across devices.

Africa's archives were burned. I built a laptop altar for the one that's left.

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine What I Built In January 2013, as militants fled Timbuktu, they set fire to 4,202 manuscripts at the…

  • 4,202 manuscripts burned in 2013 at Ahmed Baba Institute in Timbuktu
  • Family memories lost when grandparents and family members are forgotten
  • Oríkì, offline AI archive runs on laptop to preserve family history

I Forgot the Words, Not the Memory: Building Ghostlight

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine . What I Built I typed “music during a power cut.” The note I wanted used neither “music” nor “power…

  • Ghostlight project creates memory archive searchable by moments, not words
  • Utilizes open-source embedding model running in user's browser
  • Six fictional memories included for testing without sharing private stories

An Azure SAS needs a signing scope and a revocation path

An Azure SAS needs a signing scope and a revocation path Shared access signatures are convenient because they move a narrow permission into a URL. The convenience is also the risk.

  • Azure SAS requires both signing scope and revocation path for security.
  • Service SASes controlled server-side via stored access policies.
  • User delegation SASes use Microsoft Entra ID key with separate revocation.

More from Sunday 1 November →