Short answer
Automate payment reminders using a current balance source and stopping rules for payment, disputes and permissions. A promise is not a receipt: confirm reconciliation before closure. Check again before sending to cancel prepared messages when the balance changes.
Key verification: Simulate full payment with a message queued and verify that the reminder is cancelled.
Sources and limitationsAn automated reminder needs to know whether the invoice remains unpaid when contact occurs. Preparing a campaign using yesterday’s balance can produce demands to customers who have already paid. The flow should distinguish confirmed balance, payment promise, movement awaiting reconciliation and dispute, because each state needs a different action.
Vocalcom Collections with WhatsApp presents reminders and agreement follow-up. CX Automation addresses cross-channel flows and AI Workforce automated agents. The following process is a proposed exercise for evaluating reconciliation and exceptions, not a legal collections policy or a product test.
The billing system determines the balance
Identify one balance source, an invoice reference and an update time. Before communicating an amount, query the current state or a copy sufficiently recent for the process. If the query fails or contradictory data appears, pause the reminder and open a review; do not turn missing data into confirmed debt.
A statement such as “I will pay tomorrow” creates a dated promise rather than revenue. An invoice becomes paid only when the responsible system records and reconciles the applicable movement. If AI may propose plans, define who authorises the terms and which changes need a human handoff.
Example of an invoice with a partial payment
| Fictional event | Confirmed balance | Proposed action |
|---|---|---|
| Overdue invoice for 120 euros | 120 | Check eligibility before the reminder |
| Promise to pay 120 euros | 120 | Record the promise; do not mark paid |
| Reconciled payment of 50 euros | 70 | Update the amount before contacting |
| Dispute over the remaining amount | 70 | Pause automation and hand off for review |
| Final reconciled payment of 70 euros | 0 | Close the task and cancel reminders |
The table is educational and does not establish collection terms. The control point lies between selecting the customer and sending the message: if the final payment arrives during that interval, the system should check the balance again and cancel the pending send. Keeping a queue of prepared messages requires that validity check.
Stopping rules before channel selection
Write conditions for a zero balance, open dispute, unverified recipient, withdrawn contact preference and unavailable data. An alternative voice or WhatsApp route should not bypass those conditions. Also define applicable hours, frequency and permissions with process owners before activating real contacts.
A refusal, wrong number and no answer need different states. A wrong number requires recipient correction; repeating the same reminder does not fix identity. If the customer requests a person, hand over the case with invoice, queried balance and escalation reason so they do not need to reconstruct it.
Tests that reveal incomplete reconciliation
- Repeat an overdue event and check for one open task.
- Record a partial payment before sending and verify the updated amount.
- Record full payment with a message queued and check cancellation.
- Open a dispute and verify that another follow-up channel is not activated.
- Interrupt the balance query and confirm that an assumed amount is not communicated.
- Resume after human review and check that the current case version is used.
Evaluate confirmed receipts and avoidable contacts
Fictional example: of twenty eligible invoices, eight generate a promise and five have reconciled payments at period end. Promise rate is 8 / 20, 40%; confirmed-payment rate is 5 / 20, 25%. One may include cases outside the other: do not assume every payment followed a promise or automatically attribute receipts to reminders.
Also record contacts after payment, incorrect amounts and time spent on exceptions. Retain a comparable group or period to investigate an effect on receipts, and separate reconciliation improvement from commercial changes. Accept the flow only when it stops contacting in stopping cases and the record demonstrates why it acted.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original exercise.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- Vocalcom Collections with WhatsAppwww.vocalcom.ai
- CX Automationwww.vocalcom.ai
- AI Workforcewww.vocalcom.ai
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.