A Professional Collection Call Script for Overdue Invoices

The short answer: a collection call follows a branching structure — confirm who you are speaking with, state the invoice facts, ask one open question about the balance, listen for the real reason, and close with a specific next step you confirm in writing the same day.

The purpose of the call is information and commitment, not pressure. You already know the amount; what you do not know is why it is unpaid — and the script below is built to find that out without putting the other person on the defensive. Every branch ends the same way: something specific, written down.

Before you dial

• Statement or aging report open, showing the balance and any partial payments.
• The invoice in front of you: number, amount, due date, terms, PO reference.
• A note of every reminder sent, with dates, and any reply received.
• The correct contact — and a fallback if they have left the company.
• The one thing you are asking for: a payment date, a reason, or a decision-maker's name.

Calling without this means improvising, and improvised calls produce vague answers. Two minutes of preparation is the whole difference.

Opening: confirm identity and role

Start by verifying you have the right person and that they own this process. Do not launch into the amount before you know who you are talking to.

Three facts in the first thirty seconds — invoice number, amount, due date — let the other side pull up the record while you are still talking. If they ask you to email instead of talking, take thirty seconds for one question ("Just so I can note it: has the invoice been received on your side?") before you comply.

Ask one open question, then listen

After the facts, hand the conversation over. Closed questions ("So you're going to pay, right?") produce yeses that evaporate. Open questions produce the reason:

• "How would you like to handle this balance?"
• "Where does this stand on your side right now?"
• "What's blocking approval, if anything?"

Then stop talking. The pause after the question is where the real answer lives — administrative delay, a dispute, a cash-flow problem, or nothing at all. What you hear decides which branch you take.

The branching table

If they say…	It usually means	Your next move
"It's in the approval queue."	Administrative delay	Ask for the approval or payment date; confirm it in a same-day email with the PO reference
"I don't have it / it never arrived."	Routing problem	Resend immediately; get the direct AP address and the person's name
"We're disputing the work."	Genuine dispute	Do not argue; ask exactly what is disputed and take it to the written track
"We're stretched this month."	Cash-flow problem	Ask what they can pay and when; move the conversation toward installments
"We'll pay next week."	Vague promise	Pin it down: which day, what amount, who sends the remittance confirmation
No answer, or repeated brushing off	Disengagement	Note the pattern, switch to written notices, and start weighing escalation

When the answer is a dispute

Never litigate the merits on the phone. Your job is to capture the objection precisely so it can be answered with documents. Ask three questions: what exactly is disputed, when it was first raised, and who holds the relevant paperwork. Then commit to a specific action — "I'll email the signed delivery receipt and the approved scope today" — and do it before the end of the day.

Pause the reminder cadence on the disputed portion while the written exchange happens. If the objection turns out to be a missing document rather than a real disagreement, the documents checklist for commercial debt collection shows which paper closes it.

When the answer is a promise

A promise you cannot point to later is just a polite end to the call. Convert it: exact date, exact amount, who is sending it. If paying in one piece is clearly not going to happen, propose installments on the call — "Would it work to split this into three payments, starting [DATE]?" — and put the design details in structuring a payment plan for overdue invoices. Two or more broken promises in a row is a signal, not bad luck.

Closing and the written follow-up

Always close by reading the agreement back:

Send that email the same day, even if the call produced nothing. A call with no written trace evaporates; a short recap — date, participants, what was said, next date — becomes part of your file and your next reminder can reference it. For the wording of the reminder that follows a silent call, use the stage-by-stage reminder templates.

Voicemail, gatekeepers, and callbacks

Most calls will not connect live. Twenty seconds is enough for voicemail: your name, your company, the invoice number and amount, and a request to call back. No arguments, no consequences, no details about the work - a voicemail is a callback request, not a conversation to hold with a recording. If the mailbox reports full or blocked, note that too; repeated attempts to a blocked line help no one.

With a gatekeeper, ask for the process rather than the balance: "Who handles invoices for your accounts payable?" Get the name spelled, the direct number, and the best time to reach them. Log every attempt with date and time. Two attempts at different times of day usually tell you what you need to know - if calls still do not connect, move to written notices and record that decision in the file rather than letting attempts quietly accumulate.

  <h2>The note you take while talking</h2>
  <p>
    Take the note during the call, not from memory afterward. A usable note has six
    lines:
  </p>
  <ul>
    <li>Date, time, and who you spoke with - name and role.</li>
    <li>Invoice facts the contact confirmed: number, amount, due date.</li>
    <li>Their explanation, in their words where the words matter.</li>
    <li>Any commitment: exact amount, exact date, who is paying.</li>
    <li>What you promised to send or do, and by when.</li>
    <li>The next contact date.</li>
  </ul>
  <p>
    This note is what the recap email, the next reminder, and any later escalation
    all draw from. Six lines written in the moment outperform a polished summary
    written three days later - and when memories differ later, the contemporaneous
    note is the one that settles it.
  </p>

  <h2>Boundaries: what never goes into a call</h2>
  <ul>
    <li>Threats of lawsuits, arrests, or other consequences you have not actually set in motion.</li>
    <li>Raised voices, sarcasm, profanity, or comments about the contact personally.</li>
    <li>Repeated calls in a single day designed to wear someone down.</li>
    <li>Discussions with people who have nothing to do with the account.</li>
    <li>Guarantees — of payment, of timelines, or of what any third party will do.</li>
  </ul>
  <p>
    Firm and specific beats loud. You are a business asking for money owed under an
    agreement, and every call is also a negotiation you may still need next week.
  </p>
  <div class="callout">
    <strong>(hypothetical example)</strong> "Hi, is Maria there? … Maria, this is
    Dan at Coastline Supply — you handle our invoices, right? I'm calling about
    INV-3391 for $12,400, due the 14th. Where does it stand on your side?" "Honestly,
    accounting is backed up. It's approved, just not scheduled." "Understood. What
    date can I write down?" "The 30th." "The 30th — I'll email you a summary today.
    If the date moves, reply to that email." The recap went out an hour later, and
    because it was in writing, the payment date survived two staff changes on the
    buyer's side.
  </div>
  <h2>Next steps</h2>
  <p>
    The call is stage 4 of the full sequence in
    <a href="/insights/how-to-collect-unpaid-invoices/">how to collect unpaid invoices: a step-by-step workflow</a>.
    If the call produces nothing — or never gets answered — the next written step is
    <a href="/insights/final-payment-reminder-email/">a final payment reminder email</a>,
    and if you are still diagnosing the silence,
    <a href="/insights/client-not-paying-invoice/">the causes-and-remedies tree for unpaid invoices</a>
    will help you name it. The full path sits under
    <a href="/resources/unpaid-invoice-recovery/">the unpaid invoice recovery guide</a>.
  </p>