Dunning Call Scripts: Live Calls & Voicemail

Most failed payments are not disputes. The card expired, the account was short that week, or the invoice landed with the wrong person. A short, well-run call fixes what email cannot — but only if the caller has words ready. Ad-libbed calls drift into apologies, threats, or discounts nobody budgeted for. The four dunning call scripts below are written to be read word-for-word, adapted only where the brackets tell you to.

Calls work best for higher-value and B2B accounts, where one save pays for the hour spent calling. For lower-value plans, automated retries usually carry the load — use our recovery calculator to size an account's worth first. Keep the tone discipline from our dunning tone guide in front of every caller: factual, brief, never shaming. A cornered subscriber does not update a card — they dispute the charge.

Compliance basics before you dial

General basics, not legal advice — check your jurisdiction's rules first.

• Identify yourself immediately. Name, company, and why you are calling, in the first sentence.
• Verify you have the right person before discussing amounts or dates. If it is not the account holder or an authorised contact, leave only a callback request.
• Respect calling hours. Reasonable local hours for the person called — daytime and early evening in their time zone.
• No threats, ever. Never threaten legal action, credit reporting, or consequences you will not carry out. State real deadlines plainly.
• Never take full card numbers by phone unless your process is set up for it. These scripts send the subscriber to a secure card-update page instead.
• Honour a stop request instantly. Confirm it, log it, and move further contact to email.
• Log every call. Date, time, who you reached, what was agreed, and the follow-up sent.

Script 1: The live subscriber save call

Use when: A subscriber's payment has failed, automated outreach has not produced an update, and the account value justifies a call. Goal: A card update completed on this call, or a dated commitment plus a link sent.

Opening: "Hi, is this [First name]? … Hi [First name], this is [Your name] from [Company]. I am calling about your [Product] subscription — the payment on [date] did not go through, and I wanted to help sort it before your account pauses on [real pause date]. Do you have two minutes?"

If they say it is a bad time: "No problem at all. I will email you a secure link to update your card right after this call — it takes about a minute. Is [email on file] still the best address? … Thank you. If it is not sorted by [pause date], the account will pause, but you can reactivate any time after."

Diagnose — pick their branch:

• "The card expired / I have a new card." "That is the most common reason we see, and a quick fix. I will stay on the line while you open the secure update link — sending it to [email] now. I cannot take the number over the phone, but I can confirm the moment it saves. … Has it gone through? Perfect — your next billing date stays [date]."
• "Money is tight this week." "Understood — thank you for telling me. I can [pause your subscription until [date] at no charge / move this payment to [date]], so nothing lapses. Which works better?" Do not offer a discount here unless your approved offer matrix says to.
• "I meant to cancel anyway." "That is completely fine — I can close it on this call so there are no further charges. The failed payment of [amount] covers service through [date]. [Then follow your cancellation process exactly. Do not argue.]"
• "I do not recognise this charge." Stop selling. "Let me help you pin it down. The charge appears as [exact billing descriptor] for [amount] on [date], for the [plan name] plan started on [start date]. Does that ring a bell? … If not, I will flag it for review today and email you what I find — do not worry about the account pausing while we check."

Close: "So to confirm: [the card is updated and the next charge is [date] / we have paused until [date] / the account is cancelled, with a confirmation email]. You will get that email within the hour. Thank you, [First name]."

Script 2: The B2B accounts-payable call

Use when: A business account has failed and your contact is not the person who pays. B2B failures are usually routing failures — a replaced corporate card, a new AP contact, a purchase-order rule. This script finds the payer, and pairs with our guide to B2B subscription payment recovery.

Opening to your known contact: "Hi [Name], this is [Your name] from [Company], your [Product] provider. The card we have on file for your account was declined on [date] for [amount]. You may not be the right person for billing — could you point me to whoever handles payments, so your team's access is not interrupted on [pause date]?"

Opening to the AP contact: "Hi, this is [Your name] from [Company]. [Contact name] gave me your details. We provide [Product] to [Company name], and the payment of [amount] on [date] did not go through — the bank returned [decline reason in plain words, e.g. 'card expired']. What is the fastest way to get it cleared: a card update on your side, or do you need a fresh invoice or anything else from us first?"

Handle the standard AP branches:

• "We pay by invoice / ACH, not card." "Happy to switch you. I will send the invoice for [amount] to [confirm email] today, reference [invoice number]. What are your standard payment terms, so I can note the expected date?" Only promise to keep access live meanwhile if your policy allows it — then log the date given.
• "We need a PO number on it." "Of course. Give me the PO number and I will reissue today. If a PO needs raising first, who owns that, and what lead time should I plan around?"
• "That card was replaced." "That explains it. I will send a secure update link to you — or to the cardholder, if that is someone else. Who should receive it? … Sent. It takes about a minute, and I will confirm by email once it saves."
• "We are disputing / not paying this." "I want that with the right person rather than arguing it here. Can you tell me briefly what the issue is, so I log it accurately? … Thank you. I will pass it to [team] today, pause further attempts while it is reviewed, and confirm by email who owns it."

Close: "To confirm: [exact next step, owner, and date]. I will email that summary within the hour. Thank you, [Name]."

Script 3: Voicemail drop — early

Use when: First unanswered call, within the first week after failure. Under 30 seconds. Never state an amount on voicemail — the wrong person may hear it.

"Hi [First name], this is [Your name] from [Company]. A payment on your [Product] subscription needs your attention, and there is a quick fix — I have just emailed you a secure link; it takes about a minute. To talk it through, call us on [number] between [hours]. Thank you."

Script 4: Voicemail drop — final

Use when: Last call before a real pause or cancellation date. The deadline stated must be the real one.

"Hi [First name], this is [Your name] from [Company] with a final note about your [Product] subscription. The payment is still outstanding, so the account pauses on [real date]. The email I have just sent has a secure link to update your details — it takes about a minute. After [date] you can still reactivate, but I wanted you to hear it from us first. Our number is [number]. Thank you."

The follow-up email that closes every call

Every call — answered or not — ends with this email within the hour. Calls create intent; the email carries the link that converts it.

Subject: As discussed: your [Product] payment

"Hi [First name], thank you for speaking with me today [or: I just tried to reach you]. As mentioned, the payment for your [Product] subscription on [date] did not go through. [One line only, matching what was agreed: 'Update your card securely here: [secure update link] — about a minute, and your next billing date stays [date].' / 'As agreed, we have paused your account until [date] — no charges before then.' / 'As agreed, your account is cancelled and no further charges will be taken.'] If anything here is wrong, reply and I will fix it myself. [Your name], [Company] — [phone number]"

Running the call queue without burning the team

Work the queue by value and deadline, not failure order: closest to pause date first, highest plan value first within that. Cap attempts at two calls per failure cycle — one conversation attempt, one voicemail — then let email and SMS carry it. Compare recovery against our failed payment recovery benchmarks to check calls beat your automated sequence at all. The scale justifies a scripted hour: involuntary churn is an estimated 20–40% of subscriber churn, according to Recurly research. Calls are the most expensive touch in recovery — let automation clear the long tail.

The bottom line

A dunning call script exists so a caller never improvises the hard sentences: identification, the plain statement of failure, the branch for each answer, and a close that puts the agreement in writing within the hour. Run calls sparingly, by value and deadline, behind a secure update link, and log everything. If you would rather the retries, emails, SMS, and update pages ran themselves while your team only calls accounts that need a voice, see the full system's cost on our pricing page — a 14-day trial with your existing backlog worked from day one.

Frequently asked questions

When is a phone call worth it for a failed payment?

When the account value is high enough that one save pays for the calling time, when automated outreach has already failed, or when the blocker is organisational — a business account where the user is not the payer. For low-value plans, automated retries are the better spend.

Can I take card details over the phone?

Only if your business has a payment process set up and approved for phone payments. For most teams the safer pattern is the one in these scripts: stay on the line, but send the subscriber to a secure card-update page. Never write card numbers on call notes.

How many times should we call about one failed payment?

Two attempts per failure cycle is a workable default: one conversation attempt and, if unanswered, one voicemail. After that, let email and SMS continue. Repeated calling rarely adds updates and can generate complaints instead.

What should I never say on a dunning call?

Never threaten consequences you will not carry out, never shame the subscriber about their finances, never state a false deadline, and never discuss the payment with anyone but the account holder or an authorised contact.

What if the subscriber says they want to cancel?

Accept it and complete the cancellation cleanly, confirming what the outstanding payment covers and that no further charges will run. A clean exit protects future winback; arguing converts a quiet cancellation into a dispute.