Back to Blog

    WhatsApp Payment Reminder Messages: Templates and a Follow-Up Schedule for Indian Businesses

    Illustration for WhatsApp Payment Reminder Messages: Templates and a Follow-Up Schedule for Indian Businesses, VedLink AI blog

    You raised the invoice on the 5th. The due date was the 20th. It is now the 28th, and your accountant is still ringing the customer, who keeps saying "will send tomorrow." Chasing dues by phone eats hours, and an awkward call can cost you a good customer.

    A well-timed WhatsApp reminder does the same job more gently. The customer sees it, has the amount and payment details in front of them, and can reply or pay straight away. This guide gives you a reminder schedule, template wording you can adapt, and the rules that keep these messages approved and welcome.

    Why WhatsApp Works for Payment Reminders

    Calls get missed and emails get buried. A WhatsApp message sits in the same app your customer checks all day, and it can carry an invoice PDF, a UPI payment link or a reply button in one thread. It is also less confrontational than a phone call, which matters when the customer is someone you want to keep.

    This applies across clinics with pending treatment bills, coaching classes collecting fees, salons with package balances, B2B suppliers with credit customers and small electronics or clothing retailers who sell on account. If you already run Tally, our guide to connecting Tally to WhatsApp shows how outstanding balances can feed these messages automatically.

    Reminders Are Utility Messages, Not Promotions

    On the WhatsApp Business API, a message you send first, outside the 24-hour window, must use an approved template. Meta groups templates into marketing, utility, authentication and service categories. A reminder about an invoice the customer already owes normally falls under **utility**, because it relates to an existing transaction.

    That only holds if the message stays about the payment. If you add "also check our new stock, 10% off this week", Meta can treat it as marketing or reject it. Keep reminders plain, and send offers separately to customers who opted in. For how categories affect your bill, see WhatsApp Business API pricing in 2026.

    A Simple Reminder Schedule

    Most businesses do better with a fixed rhythm than with ad hoc chasing. Here is a schedule you can adjust to your credit terms:

    3 days before the due date: a friendly heads-up with the amount and due date.

    On the due date: a short "payment due today" message with the payment link.

    3 days after: a polite follow-up asking if there is any issue with the invoice.

    7 days after: a firmer message with the outstanding amount and a request for a payment date.

    14 days after: a personal message from a named person, ideally followed by a call. Stop automation here and let a human take over.

    Do not send more than this without a reason. Repeated daily messages push customers to block you, and blocks and reports hurt your sending quality. Our explainer on quality rating and messaging limits covers why that matters.

    Template Wording You Can Adapt

    Templates use variables such as {{1}} that your system fills in per customer. Keep real sentences around the variables, and avoid starting or ending a template with a bare variable. These are examples to adapt, not fixed text.

    Before due date: "Hi {{1}}, a reminder that invoice {{2}} for ₹{{3}} is due on {{4}}. You can pay here: {{5}}. Thank you, {{6}}."

    On due date: "Hi {{1}}, invoice {{2}} for ₹{{3}} is due today. Pay using this link: {{4}}. If you have already paid, please ignore this message."

    After due date: "Hi {{1}}, we have not yet received payment for invoice {{2}} of ₹{{3}}, which was due on {{4}}. Please let us know if there is any query. You can pay here: {{5}}."

    Final follow-up: "Hi {{1}}, ₹{{2}} is still outstanding against invoice {{3}}. Could you share a date by which we can expect the payment? Please reply to this message and our accounts team will assist."

    Notice the wording: it states the amount, the invoice number and the due date, offers a way to pay and invites a reply. It never threatens. You can check your draft against Meta's common rejection patterns with our free template message checker.

    Tone: Firm Without Being Rude

    The goal is to get paid and keep the customer. A few habits help.

    Assume good faith early. Most late payments are forgotten, not refused. Early messages should sound like a helpful nudge.

    Be specific. Amount, invoice number and due date remove the "which bill?" reply that delays payment.

    Offer a way out. "Reply if there is a query" gives a customer with a genuine dispute somewhere to go, other than ignoring you.

    Never shame. Do not mention other customers, public posting or legal threats in a template. If a case needs legal action, handle it outside automated messaging.

    Let Replies Reach a Person

    Reminders create replies: "paid yesterday", "send me the bill again", "can I pay on Friday?" Each reply opens a 24-hour window in which your team can answer freely. Make sure those replies land in a shared inbox, not on one person's personal phone. A team inbox lets accounts staff pick up payment queries while the rest of the team handles sales. See the 24-hour messaging window explained for how that window works.

    Be careful with automated replies here. A bot can send a copy of the invoice or the payment link, but a dispute or a promised payment date should go to a human. Our guide to chatbot-to-human handoff covers where to draw that line.

    Where the Data Comes From

    Reminders are only automatic if your system knows who owes what. Common options:

    Tally: outstanding balances and due dates can be pulled from the same entries your accountant makes. See the Tally integration.

    Google Sheets: if you track dues in a sheet, a Google Sheets integration can send a template when a row's status or due date changes.

    Your own software: an API connection can send the right template when an invoice becomes overdue.

    Build the templates once in the template builder, name them clearly, such as payment_due_soon and payment_overdue_7d, and test each one on your own number before using it on customers.

    Compliance Checklist

    Consent: customers should have agreed to receive messages from you on WhatsApp, for example when they shared their number for billing. See our guide on WhatsApp opt-in and data privacy.

    Correct data: wrong amounts or wrong customers damage trust. Check your source data before enabling automation.

    Easy stop: respect any request to stop messages and mark the contact accordingly.

    Right category: keep reminders free of promotion so they stay utility.

    Sensible frequency: stick to a short schedule and move to a personal call when it fails.

    Frequently Asked Questions

    Can I send a payment reminder without a template? Only if the customer has messaged you in the last 24 hours. Outside that window, you need an approved template.

    Can I attach the invoice PDF? Yes. Templates can include a document header, so the invoice travels with the message.

    Should I add a payment link? It usually helps, since the customer can pay in one tap. Use a link from your payment provider and keep the wording neutral.

    What if a customer says they already paid? Ask for the payment reference, check it against your records and update the contact so reminders stop. This is a job for a person, not a bot.

    The Bottom Line

    Good payment reminders are short, specific, polite and sent on a schedule. Set up four templates and a clear hand-over to a human, and you will spend less time on calls and collect faster without souring relationships. To see how this fits your business, view our plans or book a demo.