Phone calls are the most expensive touch in payment recovery and the easiest to misuse. An email costs fractions of a cent and can be ignored politely. A call costs a person's time, interrupts a subscriber's day, and — handled badly — turns a routine card problem into a dispute. Handled well, it fixes in four minutes what a week of emails could not: the business account where your contact is not the person who pays, the high-value subscriber whose card was replaced and who never saw the notice, the payer who simply needed a human to say the deadline out loud.
The discipline is in the rationing. Work the call queue by value and deadline, never by failure order: closest to the pause date first, highest plan value first inside that. Cap attempts at two per failure cycle — one genuine conversation attempt and, if it goes unanswered, one voicemail — then let email and text carry the case. Two is a ceiling, not a quota; a case that resolves after the first call does not need a second for symmetry, and a case that has had two does not get a third because someone feels uneasy.
Scripts exist so that nobody improvises the hard sentences under pressure. The caller should never have to invent, mid-call, how to identify themselves, how to state the failure plainly without shaming anyone, what to offer when the answer is "money is tight this week," or how to accept a cancellation cleanly when that is the answer. Each situation has a branch, and each branch ends the same way: a confirmation email within the hour carrying whatever was agreed, because calls create intent and the email carries the link that converts it.
The set I keep beside the phone is word-for-word dunning call scripts for live calls and voicemail — a live save call, a business accounts-payable call, and two voicemail drops, early and final, each written to be read as written.
A few rules in those scripts are worth stealing even if you write your own. Never take a full card number by phone unless your process is genuinely set up for it; stay on the line while the subscriber uses the secure update page instead, and confirm the moment it saves. Never state an amount on a voicemail, because you cannot know who hears it. Never threaten a consequence you will not carry out, and never state a deadline that is not the real one — the final voicemail only works because the pause date in it is true. And when someone says they meant to cancel anyway, close it on the call, confirm what the outstanding payment covers, and stop selling. A clean exit protects the winback you might earn in six months; an argument converts a quiet cancellation into a chargeback.
The business call deserves its own script because business failures are usually routing failures. The card belonged to someone who left, the purchase-order rule changed, accounts payable never received the invoice. The caller's job is not to collect; it is to find the payer, learn what that payer needs from you — a fresh invoice, a PO number on it, an update link sent to the actual cardholder — and leave with a named next step, an owner, and a date.
Measure whether any of this is worth it. Compare the recovery on called accounts against what your automated sequence achieves alone, on comparable value bands. If calls are not beating automation, the queue criteria are wrong, not the scripts.
Swipe Again runs the automated side — decline-aware retries, branded emails and texts, card-update pages — at $179 a month flat, so a team's calling hours land only on the accounts that genuinely need a voice. Ration the calls, script the sentences, and log everything. The log, in the end, is what turns one saved account into a process.

