Payment Reminder Call Script: Four Scripts, a Log and a Review
A payment reminder call script works when it names the invoice, asks what blocks payment, gets a dated promise, and ends in a log entry that lets you chase that date.
By Tej Pandya, Founder · Updated 6 Nov 2026

Key takeaways
- A reminder call is finished only when it produces a calendar date, an amount, a payment mode and a log entry. "Soon" is not an outcome.
- Call about 3 to 4 days before the due date, then at about 5, 10 and 15 days overdue, getting firmer each time. The firmest call ends in a named next step inside your business, never a threat.
- The 8 am to 7 pm limit binds regulated lenders and their agents under Reserve Bank of India (RBI) rules. A business chasing its own invoice sets its own hours.
- Pull 10 recordings a week and score them on 10 pass/fail checks. Coach on any check missed three or more times.
In this article
- 1What should a payment reminder call script say?
- 2When should you call, and how firm should each call be?
- 3What do you say on the day-10 and day-15 calls, and when nobody answers?
- 4How do you turn "I'll pay soon" into a date you can chase?
- 5What should you write in the call log after every reminder call?
- 6Does the RBI 8 am to 7 pm rule apply to invoice reminders?
- 7How do you check your team follows the script?
- 8How can your team run these calls with logging and recording built in?
- 9Frequently asked questions
The hardest part of a reminder call is the moment the customer says "I'll pay soon". "Soon" gives you nothing to chase and nothing to write down.
Most scripts stop when the call ends. A call that finishes without a date, an amount, a payment mode and a log entry has to be redone from scratch next time, by whoever picks up the phone.
This page gives four scripts by days overdue, replies that turn "soon" into a day, the fields to log after every call, and a 10-call recording review. It also settles a point that is easy to get wrong: the 8 am to 7 pm calling limit is a rule for banks, non-banking financial companies (NBFCs) and their recovery agents, not for one business chasing another's invoice. The scripts are for businesses calling their own customers about invoices, fees and instalments.
What should a payment reminder call script say?
A payment reminder call script should make five moves in order: name the invoice, ask whether it arrived, ask what is holding it up, agree one date with an amount and a payment mode, and repeat the three back before confirming in writing the same day. Script 1 is the call before the due date, and Script 2, the first overdue call (about 5 days late), is the one every later script builds on.
Script 1: before the due date

Hello [Name], this is [your name] from [company]. Do you have a minute? I am calling about invoice [number] for ₹[amount], due on [date]. Has it reached you? Who clears payments on your side, and will it go out by the due date?
Script 2: first overdue call
Hello [Name], this is [your name] from [company]. This call is recorded for quality. Invoice [number] for ₹[amount] was due on [date] and we have not received it yet. Has it reached you?
Is anything holding it up: an approval, a question on the bill, or the payment run?
Which date can I note for payment?
So that is ₹[amount] on [date] by [Unified Payments Interface (UPI) / bank transfer / cheque]. I am sending you a message with that now.
Ask the "what is holding it up" question once, then stop talking. The customer's answer is the most useful thing on the call. The recording line at the start is covered in our call recording announcement guide. Opening and closing pleasantries are in our telecalling script card, so they are not repeated here.
When should you call, and how firm should each call be?
Call 3 to 4 days before the due date, then at about 5, 10 and 15 days overdue, with the tone moving from helpful to specific to firm. These intervals are our recommendation, not a rule. Shorten them for customers with a history of late payment and lengthen them for large accounts you want to protect.
| When | Tone | Aim | Script |
|---|---|---|---|
| 3 to 4 days before the due date | Helpful | Confirm the invoice reached the right person | 1 |
| About 5 days overdue | Matter-of-fact | Find the blocker, get a promised date | 2 |
| About 10 days overdue | Specific | Hold the customer to the promised date, or get a new one with a reason | 3 |
| About 15 days overdue | Firm, with a named next step | The owner or a senior person calls and agrees a firm date | 4 |
A promised date is a calendar date, with an amount and a payment mode, that the customer agrees to on the call.
Here is a worked example, our own, for an ₹85,000 invoice due Monday 16 November 2026:
- The pre-due call is Thursday 12 November.
- Day 5 falls on Saturday 21 November, so make that call on Friday 20 November. On that call the customer promises Wednesday 25 November.
- They miss it, so on the day-10 call (Thursday 26 November) they promise Friday 27 November.
- The chase call is Monday 30 November at 10 am, the next working day after the promised date. It replaces the day-15 call.
If a call day lands on a weekend, bring it forward to the Friday rather than pushing it to Monday, so the count does not slip.
What do you say on the day-10 and day-15 calls, and when nobody answers?
On the day-10 call, you are asking for the date you were already promised and saying what happens next inside your business. On the day-15 call, the owner or a senior person agrees a firm date. When nobody answers, a short voicemail and a clear stopping rule keep the account moving.
Script 3: day-10 call
Hello [Name], this is [your name] from [company]. On [date] you told us payment would reach us by [date]. It has not. I need either payment by [new date] or the reason, so I can pass it to [owner's name]. If I do not hear from you by then, [owner's name] will call you himself or herself.
The next step is an internal handover, not a consequence. Keep threats out of it.
Script 4: day-15 call by the owner or a senior person
Hello [Name], this is [owner or senior person's name] from [company]. [Colleague's name] has spoken to you about invoice [number] for ₹[amount], due on [date], and you agreed [promised date]. It has still not reached us. I am calling personally to agree a date today. Which date can you commit to, with the amount and the mode? I will confirm it in writing today, and I will call you the day after to check it arrived.
Voicemail script (about 20 seconds)
Hello, this is [your name] from [company], calling about invoice [number]. Please call me back on [number].
Leave the amount off, in case someone else hears the message.
Our recommendation on when to stop: make at most 2 attempts a day. After 3 days without an answer, send a written message and hand the account to the owner.
How do you turn "I'll pay soon" into a date you can chase?
Offer a choice of two days. "Soon" survives because it asks nothing of the customer, while "Thursday or Friday?" has to be answered with a day. Pair each reply with what you write down, so the next call starts from fact.
| Customer says | You say | Write down |
|---|---|---|
| "I'll pay soon." | "Which day should I put down, Thursday or Friday?" | Promised date, amount, mode |
| "I'll pay when my own client pays me." | "Understood. Which date can you commit to for ours, even for part of it?" | Date, amount, reason: waiting on their client |
| "I have not received the invoice." | "I will resend it now. Can you check your inbox while we speak? Which day can it be paid?" | Outcome: invoice resent; promised date |
| "The amount is wrong." | "Which part differs: amount, quantity or date? I will note it and come back by [time] today. Can the undisputed part go by [date]?" | Outcome: disputed; the line in dispute; callback time |
| "I have already paid." | "Thank you. Please send the UTR or a screenshot and I will check it against our statement and call you back today." | Outcome: says paid; reference when received |
| "Call me later." | "Of course. What time tomorrow suits? I will call then." | Callback time |
UTR is the unique transaction reference your customer's bank or UPI app shows for a transfer. Ask for it every time someone says "paid", because it lets you match the payment to the invoice in minutes.
If the customer calls you back after a reminder, our missed call callback workflow covers what to do. On a callback, check the log first so you pick up where the last call ended.
What should you write in the call log after every reminder call?
Write eight fields before dialling the next number: the invoice number, the amount due, the contact's name and role, the time of the call, an outcome code, the promised date with amount and mode, the next action, and who owns it. Add the UTR when payment arrives. An outcome code is a one-line label for how the call ended, also called a call disposition.
Our call disposition guide gives 10 base codes, including wrong number, no answer, callback requested and do not call. For money calls, add four more:
- Promised date: the customer agreed a date.
- Disputed: the customer questions the bill.
- Says paid: the customer claims payment is made.
- Escalated: the account has gone to the owner.
The log serves one purpose: tomorrow's call list. Every promised date gets a chase at 10 am on the next working day after it, and any account with no promised date goes onto the next day-count call.
TalkEasy's Business Dialer logs and records every call placed through it, and you add a note against the call afterwards. We suggest typing the log line into that note: "Inv 2231, ₹85,000, Mr Rao (accounts), 10:15, Promised date, 27 Nov by UPI, chase 30 Nov 10 am, owner: Asha."

Does the RBI 8 am to 7 pm rule apply to invoice reminders?
No. The 8 am to 7 pm limit applies to banks, NBFCs and their recovery agents, not to one business reminding another about an invoice. The RBI's circular of 12 August 2022 tells regulated entities to ensure borrowers are not called "before 8:00 a.m. and after 7:00 p.m. for recovery of overdue loans". It covers commercial banks, co-operative banks, NBFCs, all-India financial institutions and asset reconstruction companies. As of November 2026, the RBI's 2025 NBFC directions (updated 1 July 2026) carry the same 8 am to 7 pm limit for NBFC recovery, except microfinance loans, which have a 9 am to 6 pm window.
Other windows exist, and they cover different callers:
| Window | Who it binds | Source |
|---|---|---|
| 8 am to 7 pm | Regulated lenders and their recovery agents, for overdue-loan recovery calls | |
| 9 am to 6 pm | NBFC microfinance borrowers | |
| 10 am to 7 pm | Credit card issuers' representatives contacting customers (para 6(a)(ix)) | |
| 9 am to 9 pm | Promotional commercial communication |
TRAI defines a transactional voice call as a non-promotional, time-critical alert to a business's own customers or account holders (clause (bu) of the definitions), and clause (bw) excludes transactional and service calls from unsolicited commercial communication. In our reading, a reminder to your own customer about their own invoice is a service or transactional call, not promotional, so the 9 am to 9 pm promotional window does not apply. Keep any sales pitch out of the call, or it becomes promotional.
If you are a lender, treat 8 am to 7 pm as a hard limit (9 am to 6 pm for NBFC microfinance borrowers). As of November 2026, RBI-regulated lenders must make service and transactional voice calls, including repayment reminders, from 1600-series numbers under TRAI's direction of 19 November 2025. If you are not a lender, set your own hours: we suggest 10 am to 6 pm on working days, then adjust from your own answer rates with our guide to finding your best time to call customers.
The lenders' conduct rules make good practice for everyone. The RBI's credit card directions bar intimidation, public humiliation and intruding on the privacy of family members, referees and friends. The NBFC directions bar threatening or abusive language and harassing relatives, friends or co-workers. For any business, that means three lines to avoid: threats, calling someone other than your contact about the debt, and shaming.
How do you check your team follows the script?
Take 10 recordings from one week, score each on the 10 checks below, and coach on any check failed three or more times in the 10. That threshold is our recommendation. It focuses coaching on repeated habits rather than one-off slips.
| # | Check | Pass | Fail |
|---|---|---|---|
| 1 | Invoice named | Number and amount said in the first 20 seconds | Said later, or not at all |
| 2 | Receipt and blocker asked | Both asked; the caller let the customer finish | Skipped, or the caller talked over the answer |
| 3 | Dated promise | Customer stated a calendar date, amount and mode | "Soon", "this week" or no answer |
| 4 | Read back | Caller repeated date, amount and mode; customer said yes | No read-back |
| 5 | Language | No threats, shaming or consequences beyond the named internal next step | Any one of these |
| 6 | Right person | Details shared only with the account contact | Amount or invoice stated to anyone else |
| 7 | Hours | Call started inside your own window | Outside it |
| 8 | Log | All eight call fields completed before the next dial (UTR only once paid) | Any field empty |
| 9 | Written confirmation | Message with date, amount and mode sent the same day | Not sent, or sent without the date |
| 10 | Recording line | Announcement made in the opening seconds | Missing |
Recordings make this practical: you hear the call rather than trusting the log. AI Call Insights analyses recordings and flags follow-up commitments and conversations that may need attention, so a reviewer can start with the flagged calls. The flags point you to calls worth listening to, and the judgement stays with the reviewer.
How can your team run these calls with logging and recording built in?
Run the calls through one tool that logs and records them automatically, so the log and the review do not depend on memory. In Business Dialer, your team places each call with a tap, every call is logged and recorded, and the note against the call carries your promised date.
To see it on your own invoice list, talk to us: write to support@groweasy.ai or use the booking link below.
Run reminder calls with logging and recording built in
Frequently asked questions
Treat "tomorrow" as a promised date and write it down: "Tomorrow, [date], ₹[amount], by UPI?" If it slips twice, move to Script 4 and bring in the owner.
Sources
- 1.RBI circular RBI/2022-23/108, Outsourcing of Financial Services: Responsibilities of regulated entities employing recovery agents, 12 August 2022, Reserve Bank of India
- 2.Reserve Bank of India (Non-Banking Financial Companies, Responsible Business Conduct) Directions, 2025, issued 28 November 2025, updated 1 July 2026, Reserve Bank of India
- 3.Master Direction, Credit Card and Debit Card, Issuance and Conduct Directions, 2022, Reserve Bank of India
- 4.The Telecom Commercial Communications Customer Preference Regulations, 2018 (19 July 2018), Telecom Regulatory Authority of India
- 5.Direction regarding phase-wise implementation of mandatory adoption of 1600-series numbers by RBI, SEBI and PFRDA regulated entities, 19 November 2025, Telecom Regulatory Authority of India


