As of 13 August 2026, AI can chase a late-paying business customer.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. Open the invoice, customer account and signed contract or purchase order, and gather the invoice number, amount, issue date, due date, payment record and exact payment terms.
   2. Paste the relevant facts and correspondence into the prompt, removing unnecessary personal data and keeping the contract wording exact.
   3. Ask the chatbot to produce the reminder sequence, call script and checking table without sending any message.
   4. Compare every amount, date, name and contractual reference in the drafts against the invoice, ledger and contract before editing the wording.
   5. Remove any legal threat, interest claim, penalty or escalation statement that is not clearly supported by the contract or advice from your solicitor.
   6. Send the first approved message through your normal business email or credit-control system, record the date and response, then use the later drafts only if the agreed interval passes.

   Prompt

   Act as a careful business communications assistant for a UK company. Draft a payment-chasing sequence for this overdue business invoice using only the facts I provide. Do not invent contract terms, dates, payment rights, interest, penalties or legal consequences. Do not threaten court action, debt collection, reporting, winding-up proceedings or any other escalation unless the supplied documents clearly support the wording, and flag anything that needs a solicitor instead.
   
   Prepare:
   1. A short first reminder email.
   2. A firmer follow-up email.
   3. A final escalation email that remains factual and professional.
   4. A short call script and voicemail version.
   5. A table showing when to send each message, what fact it relies on and what I must check before sending.
   
   Keep the tone commercially firm but preserve the customer relationship. Ask the customer to confirm the payment date or explain any genuine dispute. Separate the undisputed invoice balance from any disputed amount. Include no personal data beyond the names and contact details I provide. Mark every uncertain point as CHECK BEFORE SENDING.
   
   Company: [company name]
   Customer: [customer business name]
   Customer contact: [name and role, if needed]
   Invoice number: [invoice number]
   Invoice date: [date]
   Due date: [date]
   Amount and currency: [amount]
   Payments received: [details]
   Relevant contract or purchase order terms: [paste exact relevant wording]
   Previous communications: [paste relevant messages]
   Known reason for non-payment or dispute: [details or 'unknown']
   Preferred outcome: [payment date, payment plan, dispute response or other]
   Messages already sent and their dates: [details]
   Do not send or publish anything. Return drafts and checks only.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.