WhatsApp payment reminders: 4 stop cases
The collections lesson set when to send a reminder: three days before the due date, on the day, and a week after. This lesson sets when not to. If your system sends WhatsApp payment reminders automatically, stop it in 4 cases before every message: a payment has arrived but is not yet matched; the invoice is disputed, or goods came back with no credit note issued; the customer agreed a payment date with a member of staff; or the number is not registered to receive payment requests, or a reminder went out only days ago. One misplaced reminder costs more goodwill than it collects.
A case from the floor
Illustrative example: a building materials supplier sells on credit to 90 contractors and switched on an automated step that sends WhatsApp reminders each morning instead of the accounts clerk. In week one the system prepared 40 reminders and held back 7 before sending.
Those seven are the lesson. Three contractors had transferred the money the day before and the transfer was not yet matched. Two had disputed a quantity on the invoice, and the dispute was logged with the accountant. One had agreed with the sales rep to pay on the 25th. Another's registered number belonged to an employee who had left. Had all seven gone out, each would have called in anger, and each would have been right.
Four cases where the reminder stops
- A payment arrived but is not matched. Before each reminder the system checks unmatched incoming transfers and sales reps' receipts not yet posted. If it finds an amount close to the customer's name or invoice value, it holds the reminder and passes it to the accountant. If the payment was partial, the reminder states the balance only, not the original amount.
- An open dispute or return. An invoice the customer disputed on quantity or price, or one with returned goods and no credit note, leaves the reminder list until the dispute is closed. Chasing an amount the customer contests turns a small disagreement into a loss of trust.
- An agreed payment date. If the customer promised to pay on a set date or agreed a schedule, staff record the date on the invoice and the system stays silent until it arrives. Then it reminds them of the promise itself: "Today is the payment date we agreed", not a fresh demand as if nothing had happened.
- The right number and a sensible frequency. The reminder goes only to the number registered on the account to receive payment requests, as in the customer statement checks. It never sends a second reminder for the same invoice before the written minimum gap, and never combines two accounts' invoices in one message.
What the system does, case by case
| Case | What the system does |
|---|---|
| Unmatched incoming transfer of a similar amount | Holds the reminder and sends it to the accountant to match |
| Partial payment recorded | Sends a reminder for the balance only |
| Dispute, or return with no credit note | Excludes the invoice until the dispute is closed |
| Payment date recorded | Stays silent until that date, then reminds them of the promise |
| Registered number unreachable or reported changed | Sends nothing and asks staff to update the number |
When the customer replies
A contractor gets a reminder on his registered number and replies:
Customer: I transferred it yesterday
System: Thank you. The transfer has not shown in our account yet. I have passed it to the accountant to match, and you will get no further reminder for this invoice until he replies. Send the receipt here if you have it.
And the owner asks in the morning:
Owner: Who gets a reminder today?
System: 33 customers. I held back 7: three with unmatched transfers, two with open disputes, one with a payment date on the 25th, and one whose number needs updating. Send the list?
The owner wrote no reminder by hand, and no reminder went to the wrong place. That is what WhatsApp invoicing adds: the system follows every invoice, and the four cases are checked every time without anyone remembering them.
Checklist before switching on automatic reminders
- Does the system check unmatched transfers before each reminder?
- Are disputes and returns recorded on the invoice itself, not in a side chat?
- Do staff have a field to record an agreed payment date?
- Does each account have a number registered for payment requests, and a written minimum gap between reminders?
- Is every reminder logged: to whom, which invoice, what amount, and when?