Course overview
Lesson 3 of 9 · 3 promptsAI for Accounts Receivable Specialists
LESSON 03 OF 9

Collections Call Prep

3 prompts for Accounts Receivable Specialists

Prompts for Accounts Receivable Specialists: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Build a Collections Call ScriptUse this when you need a structured opening, discovery questions, and a clear close for a collections call.
  2. 02Summarize Account Before Collections CallUse this when you need a quick history of invoices, payments and promises before dialing a customer about an overdue balance.
  3. 03Draft Collections VoicemailUse this when you reach a customer's voicemail and need a short, professional message that asks for a callback about an overdue invoice.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Build a Collections Call Script

Use this when you need a structured opening, discovery questions, and a clear close for a collections call.

Prompt

Role: You are an accounts receivable specialist who prepares clear, respectful collections call scripts that help secure payment commitments without damaging the customer relationship.

Context you provide

  • {{customer_name}}: the account you are calling
  • {{invoice_details}}: invoice numbers, amounts, and due dates
  • {{days_past_due}}: how overdue the balance is
  • {{prior_contact}}: summary of previous reminders or calls
  • {{payment_terms}}: agreed terms and any dispute notes
  • {{caller_name}} and {{company_name}}: who is making the call
  • {{desired_outcome}}: e.g., payment date, partial payment, or payment plan
  • {{tone}}: e.g., firm, friendly, or neutral

Instructions

  1. Ask for any missing inputs, then restate the call objective and the account status in one sentence.
  2. Draft a brief opening that identifies you, your company, and the reason for the call.
  3. Write 4 to 6 open questions to understand the reason for non-payment and the customer's ability to pay.
  4. Add short responses to three likely objections: 'I already paid,' 'I can't pay now,' and 'I need to check with someone.'
  5. Draft a close that confirms the agreed next step, payment date, amount, and method.
  6. Keep the script to one page and use plain, non-threatening language.

Output format Return four labeled sections: Opening, Discovery Questions, Objection Responses, Close. Use bullet points for questions and responses. Keep the total under 400 words. Leave out legal threats, interest calculations, and any promise you cannot verify.

Guardrails

  • Do not invent invoice numbers, amounts, payment terms, or customer details; use only the inputs provided.
  • If the user has not provided a payment deadline or dispute status, ask for it before drafting.
  • Flag that formal demand letters, credit reporting, or legal escalation must be checked with a qualified professional.

Example Customer: Northwind Traders, Invoice INV-2043, $4,820, 45 days past due, two reminder emails sent, contact: Dana Reyes, desired outcome: payment by Friday, tone: firm but respectful.

Open as its own page

02

Summarize Account Before Collections Call

Use this when you need a quick history of invoices, payments and promises before dialing a customer about an overdue balance.

Prompt

Role You are an accounts receivable analyst preparing a short pre-call brief so a collections specialist knows the balance, the history and the open promises before dialing. Optimise for accuracy and a clear ask.

Context you provide

  • {{customer_name}} and {{account_number}}: who the call is about
  • {{invoice_ledger}}: pasted invoice lines with number, date, amount, due date, status
  • {{payment_history}}: pasted payments with date, amount, method, invoice applied
  • {{prior_contact_notes}}: call logs, emails, promise-to-pay dates
  • {{credit_terms}}: agreed terms and credit limit
  • {{call_objective}} and {{today_date}}: the outcome you want and the call date

Instructions

  1. Ask for any missing inputs, then wait. Do not start until the ledger and payment history are supplied.
  2. Reconcile the ledger against payments. State the current balance, total overdue and the oldest overdue invoice.
  3. Age the overdue items into buckets using {{today_date}} and each due date.
  4. Summarise payment behaviour: how often this customer pays late, typical days late, largest payment received.
  5. List every promise to pay in {{prior_contact_notes}} with its date and whether it was kept.
  6. Write three talking points tied to {{call_objective}}, in the order to raise them, and flag anything to check first: disputes, missing remittance advice, credit limit breach.

Output format Markdown brief under 300 words: Account snapshot (3 lines), Open invoices (table), Payment behaviour (3 bullets), Promises and outcomes (bullets), Talking points (3 numbered), Check before calling (bullets). Neutral business English. Leave out guesses about intent and any advice on legal action.

Guardrails

  • Use only the figures supplied. Never invent invoice numbers, amounts, dates or payment references. Mark anything absent as "not provided".
  • Flag assumptions and say what data would confirm them.
  • Tell the user to check the company credit policy and involve a manager or legal advisor before any escalation, credit hold or formal demand.

Example {{customer_name}}: Northgate Supplies Ltd, {{account_number}}: AR-10442, {{credit_terms}}: net 30, {{today_date}}: 14 March, {{call_objective}}: agree payment dates for the two oldest invoices.

Open as its own page

03

Draft Collections Voicemail

Use this when you reach a customer's voicemail and need a short, professional message that asks for a callback about an overdue invoice.

Prompt

Role You are an accounts receivable specialist drafting a collections voicemail. Optimise for a short, respectful message that names the account, requests a callback, and protects the customer relationship.

Context you provide

  • {{customer_name}}: who you are calling
  • {{company_name}}: your company
  • {{your_name}}: your name
  • {{invoice_number}}: invoice reference
  • {{amount_due}}: outstanding balance
  • {{due_date}}: original due date
  • {{days_overdue}}: days late
  • {{callback_number}}: your direct number
  • {{best_time_to_call}}: when you are available
  • {{prior_contact}}: earlier messages or promises
  • {{tone}}: friendly reminder or firm follow-up

Instructions

  1. Ask for any missing inputs, then confirm the goal: a voicemail requesting a callback about an overdue invoice.
  2. Write a script under 30 seconds spoken. Open with your name, company, and customer name.
  3. State the invoice number, amount, and due date plainly. Include days overdue only if given.
  4. Ask for a callback by a specific day or time. Give your direct number and best time to reach you.
  5. Keep the tone professional and non-threatening. Offer to answer questions or discuss a payment plan. If prior contact is provided, reference it neutrally. Provide one alternate version if the tone input calls for firm follow-up.

Output format Plain text voicemail script, no headings or bullets. 45 to 90 words. Tone: respectful, clear, calm. Leave out legal threats, aggressive language, unnecessary personal data, and any invented figures or codes.

Guardrails

  • Do not invent invoice numbers, amounts, dates, or company names. Use only the inputs provided.
  • Do not include threats, legal language, or promised outcomes. Flag if the account may need supervisor or legal review.
  • If local debt collection rules require specific disclosures, tell the user to check with a licensed professional or compliance team.

Example Customer: Acme Corp, Company: Northwind Supply, Your name: Jordan Lee, Invoice: INV-1042, Amount: $2,450, Due date: 2025-03-01, Days overdue: 15, Callback: 555-0142, Best time: 9-11am, Prior contact: left message 3 days ago, Tone: friendly reminder.

Open as its own page

Skills for these tasks

Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.