What a collection call is actually for
A sales script is written to produce a next step. A collection script is written to produce four specific facts: an amount, a date, a payment method, and the name of the person who agreed to all three. If the call ends without those four things recorded, it produced nothing at all — no matter how polite it was, no matter how sincerely the other side said they would look into it.
That is a narrower goal than most scripts are built around, and the narrowness is the point. "When can we expect payment?" invites an answer that costs the other side nothing to give and gives your ledger nothing to act on. Next week. Once the month closes. When I have spoken to my finance director. None of those is a commitment; all of them end the call, which is why an unstructured collection call feels productive and changes nothing.
A promise is what a collection call produces when nobody wrote down what it was supposed to produce instead.
Where this frame comes from
The block structure and the timings below are our own prescriptions, not research and not an industry standard. They are what survived from reviewing calls on the founders' own floors — roughly ten years of running call centres, up to fifteen hundred live operators at peak, across France, Mexico and beyond. Where a figure comes from a named publisher instead, the publisher is named in the same sentence. Nothing here is legal advice, and collections rules differ by country and by the kind of debt: decide your rules first, then write the script inside them.
The seven blocks, and the two that change for receivables
We use the same seven-block frame for every outbound phone script: open, right to the conversation, right person, qualification, offer, objection, dated next step. The opening block runs ten to fifteen seconds, from hello to the reason for the call, and the first three blocks together should be done inside about thirty seconds. Those are our own operating prescriptions, and they hold for a receivables call as well as a sales call.
Two blocks change completely, though, and a collection script that reuses the sales version of either is the most common way these calls go wrong.
On a sales call this means the person who can decide. On a receivables call it usually means accounts payable, who did not sign anything and have no opinion about your product — while the person who did sign may have no idea the invoice exists. Getting routed to the signer feels like progress and is usually a detour.
On a sales call you are finding out whether there is a budget. Here the budget question is already settled: they agreed the amount. What you are finding out is why an agreed amount has not been paid, and that answer decides everything you say next.
We do not publish a target duration for a collection call. The under-four-minutes figure in our script frame was measured on cold calls, where the caller controls the agenda; a receivables call can legitimately need longer because the other side is looking something up, and a script that pushes for brevity there just produces a promise instead of an arrangement.
The question that has to come first
Before you ask when, ask why. There are only three real answers, and they are not variations of each other — they are three different calls that happen to start the same way.
- They never got it, or cannot find it. The invoice went to a person who left, sat in a spam folder, or is waiting on a purchase-order number nobody supplied. Nothing is in dispute and nobody is short of money. This is an administrative problem wearing the costume of a debt.
- They dispute it. The amount is wrong, the work is contested, a credit note was promised, or something was delivered late. The moment you hear this, you are no longer collecting — you are handling a dispute, and continuing to collect makes it worse.
- They cannot pay right now. The money is not there this week. This is the only one of the three where the classic collection conversation — an arrangement, a date, a partial payment — is the right instrument.
A script that does not fork here will treat all three as case three, which means pressing someone for a payment date over an invoice they have never seen, or negotiating terms on an amount that is genuinely wrong. Both of those cost more than the invoice.
The three calls the fork produces
Do not negotiate. Confirm the right address and the right reference, resend while still on the call if you can, and get a date by which they will confirm it has arrived and entered their system. The commitment you are asking for is administrative, so it is cheap for them to give and easy for you to check.
Stop collecting mid-sentence. Record what is disputed in their words, tell them what happens next and who will contact them, and put an internal date on it. Do not defend the invoice, do not explain the contract, and do not ask for payment of the undisputed portion in the same breath — that reads as ignoring what they just said.
This is where the arrangement belongs. Ask what they can do rather than proposing a figure first, because the number they volunteer is the one they are likely to keep. Then fix the amount, the date, the method and the person, and say all four back to them before the call ends.
The dated next step, said back out loud
The last block of the frame is a dated next step, and on a receivables call it has a form: amount, date, method, name. The reason to repeat it aloud is not politeness. It is that a vague arrangement and a firm one sound identical while you are on the call, and only one of them survives to the follow-up — where you need to be able to say what was agreed, not what you both remember.
Our qualification block is built around two or three questions, chosen because the answers change what gets offered. On a collection call those questions are: why has this not been paid, what can you actually do, and by when. Anything else you were going to ask belongs in the CRM already.
What the script must never do
- Imply a consequence the business has not actually decided to pursue. A script that mentions legal action the company will not take is both a lie and, in many places, a compliance problem.
- Discuss the debt with anyone who is not the debtor. That includes a colleague who answers the phone, a spouse, and a voicemail that anyone might play.
- Keep pressing after a clear refusal. Our own rule is a single recovery attempt past a first refusal — beyond that the number is burnt, and a burnt number is worth less than the invoice.
- Improvise on hardship. If someone describes illness, redundancy or insolvency, the script's job is to end the collection attempt and route the account to a person, not to find a smaller number.
The voicemail version, which is a different script
Most attempts will not reach the person. That makes the voicemail script part of the deliverable rather than an afterthought, and it is the one part of a collection script that has a hard constraint on content: you cannot say why you are calling, because you do not know who will listen to it. So a collections voicemail identifies the company, gives a reference number and a callback window, and asks for a return call — and nothing else.
That is a weak instrument. BIA/Kelsey's industry estimate puts 85% of people who reach voicemail as never calling back, and there is no reason a message that cannot state its purpose would beat that average. Treat the voicemail as a way of making the next attempt less cold, not as an attempt in itself, and let the pattern of attempts — different days, different hours — do the work the message cannot.
An invented example, block by block
The call below is invented — it is written to show the frame, not transcribed from any real call, and no recording or client conversation of ours is reproduced anywhere in it. Read it as a shape to fill with your own product, terms and tone.
- Open, ten to fifteen seconds. "Good morning, this is Alex from Northgate Supply. I'm calling about invoice 4471, from the twelfth of July. Am I through to accounts payable?"
- Right to the conversation. "It's a two-minute thing — I want to check whether it reached you, and if it did, what it's waiting on."
- Right person. "Are you the right person for that, or is there someone else who handles our account?"
- Qualification. "Do you have it on your side? ... It's not showing? Let me check what address it went to." — the fork happens here, on the answer, not before it.
- Offer, in the cash-flow case. "What can you do this month? ... If half goes out on the twenty-second and the balance on the ninth, I can hold the account as it is."
- Objection. "I understand you can't confirm today. Who can, and when will they be at their desk?" — one attempt, then accept it and set the callback.
- Dated next step. "So: four hundred and twenty on the twenty-second by transfer, the balance on the ninth, and you're Priya in accounts payable. I'll email that back to you today."
Building your first version, and where a voice agent fits
Do not write a collection script from scratch. Pull twenty to thirty recordings from different people on your own team, and take the sentences that actually got dates out of people — those exist already, unevenly distributed, and the job of a script is to spread them. Then revise it monthly against new recordings, because the objections change faster than anyone expects.
Once the script exists, the question of what to automate answers itself. The early, repetitive stages — the pre-due reminder, the first overdue call, chasing an arrangement that was not kept — are the same short conversation thousands of times, which is what a voice agent is for. The dispute fork and the hardship fork are where it stops, and the script should say so explicitly rather than leaving it to the model. That decision has its own article, and it is worth making before you automate anything.