Collections and overdue payments
Payment reminders on time, without chasing anyone.
Sends the WhatsApp reminders your team approves, with the payment link from your payment system, and notes payments in the ERP.
An approved reminder plan
The example follows a fictional invoice from the advance notice to confirmed payment, under the rules administration set.
What you can do
- Remind of due dates. Notices before and after the due date, on your schedule.
- Make paying easy. Each message carries the link from your gateway or bank.
- Note what is collected. When the payment system confirms payment, it is reflected in the ERP.
How the work flows
An example with fictional data to explain the workflow, not a customer case.
Overdue invoice
Invoice F-0000 for Example customer passes its due date.
Approved reminder
The message administration approved goes out.
Payment and entry
The customer pays through the link and the payment is noted in the ERP.
Connections and control
- Connection to your ERP, WhatsApp Business number and gateway or bank; your payment system generates the link.
- Administration approves texts, schedule and recipients. The agent does not change amounts, grant deferrals or write off debts.
- Questions, disputes or payment proposals go to a person.
- Layered protection: personal-data filters and access control. Masking data before the model is not the same as anonymising it permanently.
Frequently asked questions
Can it take payment or access the customer’s account?
No. It sends the link from your payment system; the customer pays.
What if the customer says the invoice is wrong?
The conversation goes to administration and reminders pause.
Who decides when and how to chase?
Your team: notices, tone and frequency are approved before they apply.