Accounts Receivable Automation

Collections Call Script: What to Say When You Reach the Switchboard, Not the Payer

Most collection calls reach a main line, not the payer. Word-for-word scripts for the switchboard, wrong person, voicemail and payer, plus finding AP.

Jared Shulman
November 21, 2026
Controller holding a desk phone to his ear while waiting on hold at an office counter
Many collection calls reach a receptionist, a general voicemail or the wrong person, not the payer. Use a script for each of those, lead with the reference the customer recognizes, find the accounts payable contact, and log every call so the next one starts further along.
  • On the first call, aim to get routed, not paid: give the switchboard only what it needs to send you to the right desk.
  • Lead with the customer's own reference (PO, vendor ID, matter or client name), not just your invoice number.
  • Ask every wrong person who the right one is, and log it as a wrong contact plus the suggested contact.
  • Keep voicemails under 30 seconds and focused on routing; leave amounts off general mailboxes.
  • Find the AP contact from your contract, remittance emails and supplier portal before turning to public sources.

A customer we worked with, a contingency-fee employment law firm, had its controller spend part of one week on collection calls about past-due settlement payments: about 16 calls in all. Roughly four in five reached a main office line instead of anyone who pays bills. A few of those accounts paid anyway. For the rest, nobody could say whether the message had ever reached the right desk.

Most collections call scripts skip that part. They open with "Hi, is this [AP contact]?" and go straight to the payment conversation. In practice, many calls start with a receptionist, a general voicemail box, or someone who has never seen your invoice. Below is a script for each person you actually reach (the switchboard, the wrong person, voicemail, then the payer), how to find the accounts payable contact, and how to log each call so the next one starts further along.

Why Collection Calls Stall Before They Reach the Payer

Three things usually go wrong first.

The person who owes isn't the person who pays. The relationship sits with a client lead, a project owner or, for a law firm, the lawyer on the other side. The payment runs through accounts payable, an office manager or a billing assistant. A main line routes calls by name and purpose, so a call that opens with "past-due invoice" and your own invoice number often gets parked in a general mailbox.

Your reference isn't their reference. Recipients file payables under their own identifiers: their PO, their vendor ID, their matter or client name. At the firm above, invoices named the firm's own client but not the opposing lawyer whose office would handle payment. As the controller saw it, a large firm's accounting team that receives a bill it can't tie to one of its own clients will most likely throw it away. Either way, if the person on the line can't match your reference to something in their system, the conversation stops there.

Nobody wrote down the route. The same team had no system for the right department, the right person and the right channel for each payer. Every call started from zero, and whatever one caller learned stayed in their head.

If you're a law firm collecting settlements from the other side, one more point applies. When the paying party has a lawyer in the matter, the safest practice is to get opposing counsel's consent (ideally in writing) before your team contacts that party's AP, copy counsel, and stick to payment logistics. Our guide to law firm collections covers those ground rules and the rest of the process.

Before You Dial: A One-Minute Prep Sheet

Review the account, but build your prep around what the recipient will recognize, not what your ledger shows.

  • Their reference first. Their PO number, vendor ID, matter name or the client name they use. If you don't know it, finding it is one of the call's goals.
  • Your facts. Invoice number, amount, original due date, and any installment that's due.
  • Who you think pays, and in what role. A name if you have one; otherwise the role ("whoever processes outside invoices").
  • A fallback ask. If you can't get a person: the shared AP inbox, a department extension or a supplier portal.
  • One callback number and one email. Give the same two every time so replies come back to one place.
  • Your outcome codes (see the call log below), so you can record the result while it's fresh.

If an email sequence is running on the account, check what went out last so the call doesn't contradict it; automated payment reminders covers how calls and emails fit into one cadence.

Script 1: The Switchboard or Receptionist

Your goal on this call is to get routed, not paid. Tell the receptionist only what they need to send you to the right desk; keep amounts and account detail for the person who handles payment.

You: Hi, this is [Name] from [Company]. I'm calling about a payment on [their reference: PO, account or matter name]. Could you put me through to whoever handles vendor payments, accounts payable or the billing team?

If they ask what it's about:

You: It's about an invoice we sent for [their reference]. I just need to confirm it reached the right person and when it's scheduled for payment.

If they say they can't give out names:

You: That's fine. Is there a shared accounts payable email I can send it to, or an extension for the department? Or could you tell me the title of the person who processes outside invoices? Then I'll ask for them by title.

If they offer to take a message:

You: Thank you. Could you pass on [Name] from [Company], about [their reference], and my number, [number]? And could I get your name, in case I need to follow up?

Before you hang up, confirm the spelling of any name or email address, and note who gave it to you. A receptionist who helped once is often the fastest route next time.

Script 2: The Wrong Department or the Wrong Person

You got through, but to someone who doesn't handle it: the lawyer instead of the billing assistant, or a project manager instead of AP. Don't pitch the invoice. Ask for the route.

You: Thanks for taking the call. I'm [Name] from [Company], calling about invoice [number] for [their reference]. It sounds like this isn't with you. Who approves or processes invoices like this on your side?
Them: That'd be our AP team. Or [Name].
You: Great. Could you transfer me, or would it be easier if I emailed them and copied you so they know it's legitimate? And which reference do they usually file these under: the [PO, matter or client name], or something else?

Then confirm the name, role, direct line or email, and the reference they gave you.

This call is worth more than it looks. An email that names a colleague ("[Name] suggested I reach out") usually gets a warmer reception than a cold note to AP. And you've learned that the contact on file was wrong and who the right one is. Log it as exactly that: wrong contact, plus the suggested contact. That pair is what stops the next call from landing in the same place.

Script 3: Voicemail

Keep it under 30 seconds. A voicemail that sounds like a sales call gets deleted; one the listener can act on in one step gets returned or forwarded.

You: Hi, this is [Name] from [Company], calling about a payment on [their reference], invoice [number]. Could you call me back at [number], or reply to [email] with the best person to talk to about it? Again, that's [Name], [number]. Thanks.

If you're leaving it on a general or shared mailbox, consider leaving out the amount and any account or case detail. Enough to identify the account and ask for routing is a sensible default.

On the second voicemail, a few days later, change the ask instead of repeating the first message:

You: Hi, it's [Name] from [Company] again, about [their reference]. If you're not the right person for this, could you just reply to [email] with who is? That's all I need.

A smaller ask is easier to say yes to, and a forwarding reply is often as good as a call back.

Script 4: When You Reach the Person Who Can Pay

Most scripts cover this part. Keep it short.

You: Hi [Name], thanks for taking the call. I'm [Name] from [Company], about invoice [number] for [their reference]: [amount], due [date]. First, can you see it on your side under that reference?

If they can:

You: Great. What date is it scheduled for payment?

Then, before you hang up:

You: For next time, what's the best way to reach you about invoices: this number, email or something else? And is there anyone I should copy?

That last question matters. The firm in our example wanted to add text messages, because some payers prefer a text and others a call, but a text to a main office line goes nowhere. Asking each payer how they want to be reached builds that data one call at a time.

Send a short email recap (invoice, date, agreed contact details), then act on what you heard:

  • They committed to a date. Track it as a promise, and know what to do if it slips: see broken promise to pay.
  • They disputed the amount or the work. Open a dispute instead of pushing for payment: see invoice dispute management.
  • They'd rather handle it in writing. Our guide to the past due invoice email covers what to send someone you'll work with again.

How to Find the Accounts Payable Contact

If you don't know who pays, look in this order, from sources you control to ones you have to ask for:

  1. Your own contract or engagement terms. Look for billing instructions, a named billing contact, a PO requirement or a notice address.
  2. Past remittance advice and payment confirmations. Whoever sent the last payment notice or remittance email is usually in or near AP.
  3. The customer's vendor onboarding or supplier portal. Many larger organizations ask suppliers to submit invoices through a portal or a specific inbox, and the instructions often name the team.
  4. A shared AP inbox. Addresses like ap@ or invoices@ are common; confirm one exists before relying on it.
  5. Your first successful call. Ask the routing question from Script 1 or Script 2 and write down the answer.
  6. Public sources, last. The company website or a professional networking profile can suggest a name and role, but confirm it on a call or by email before you send account detail.

Record what you find per counterparty, not per invoice: name, role, direct line, email, preferred channel and the reference they file under. One payer contact can cover several invoices; for a law firm, one opposing lawyer's office may be paying on several of your clients' matters, so a contact found for one settlement saves calls on the next.

And get the phone data right before you add channels. If most of your numbers ring a main office line, a text-message reminder won't reach anyone.

Log Every Call So the Next One Starts Further Along

A call that misses the payer still produces information. Capture it with a few outcome codes:

Outcome What to record Next action
Reached payer Payment date, preferred channel Send the recap email; track the date
Routed New contact's name, role, line or email Contact them within a day or two
Wrong contact Who you reached, and who they said to contact instead Update the contact on file; reach the suggested person
Voicemail left Which mailbox (direct or general) Second voicemail with a routing-only ask, or an email
No route found What you tried Work down the AP-contact list above

Give every row a next-action date. The "wrong contact" row is the one that changes results: if four in five calls hit a switchboard this week, a record of who you reached and who you should have reached is what shrinks that share next week.

Where AI Helps: Checking You're Contacting the Right Person

A phone number and an email address are two ways to reach a contact. If the contact is wrong, switching channels doesn't fix it: the call reaches the wrong person, and the email lands in the wrong inbox. A call gets a partner who says someone else handles billing. A reminder email to an opposing lawyer gets a reply from their assistant saying invoices go to the firm's accounting team.

That's where Daylit uses AI. An AI model judges whether the contact on file is the right one for a given invoice. When it isn't, Daylit raises a wrong-contact suggestion with who to reach instead, and your team reviews and confirms it before anything changes. A wrong-contact case can start from an email reply or from a flag your team adds after a call, so what you learn by phone and by email ends up in one place. Collection Cases, including the Wrong contact type, are covered in our article on AI dispute resolution.

Putting It Together

On a collections call, route first and collect second. Use the reference your customer recognizes, ask every wrong person who the right one is, keep voicemails short enough to forward, and write down what you learn on every call. The scripts get you through this week's calls; the contact log gets next week's calls to the payer sooner.

What should I say on a collections call?

Start by getting routed: your name, your company, the customer's reference, and a request for whoever processes vendor payments. With the payer, confirm they can see the invoice, ask for a payment date, and ask how they'd like to be contacted next time. Scripts 1 to 4 above give the exact lines.

Should I leave a voicemail about a past-due invoice?

Yes, but keep it short and focused on routing: who you are, the customer's reference, one number, one email, and a request to call back or name the right person. On a general mailbox, leave out amounts.

Does the FDCPA apply to B2B collection calls?

The FDCPA covers consumer debts, so it generally doesn't apply when a business collects its own B2B invoices in its own name. State laws vary, so check yours. Our collection letter guide has a short note on the FDCPA and B2B collections. This isn't legal advice.

How do I find who pays invoices at a company?

Check your contract, past remittance emails, the customer's supplier portal and any shared AP inbox, then ask on your first successful call. Use public sources last and confirm what you find.

Insights

You might also like...

VP of Finance pinning blank cards into three columns on a cork board
Credit Policy Template With Customer Risk Tiers: Criteria, Limits and Collection Rules per Tier
A credit policy template you can copy, plus a simple way to sort customers into risk tiers and set limits, terms and collection rules for each tier.
Read more
Credit Policy Template With Customer Risk Tiers: Criteria, Limits and Collection Rules per Tier
Accounts Receivable Automation
Operations lead re-reading an email draft on her laptop in an office lounge armchair
How to Write a Past Due Invoice Email to Someone You'll Work With Again
How to write a past due invoice email to a client or counterparty you'll deal with again: who to address, tone by recipient, three examples, a final check.
Read more
How to Write a Past Due Invoice Email to Someone You'll Work With Again
Accounts Receivable Automation
AR specialist checking her phone at an office kitchen counter beside her laptop
Broken Promise to Pay: What to Do in the First 72 Hours (and When to Escalate)
A customer missed a promised payment. A 72-hour playbook to confirm, diagnose, re-commit and set escalation triggers — plus how to track every installment.
Read more
Broken Promise to Pay: What to Do in the First 72 Hours (and When to Escalate)
Accounts Receivable Automation
Book a free consultation with Daylit

Learn how to shorten your cash conversion cycle by reducing inventory levels, extending vendor payment terms, and accelerating customer collections.

Button
Button