This illustrative service-business scenario follows a part-paid invoice. It shows the intended review process around payment records and customer follow-up; no live messages or money movements are involved.
Start with the account, not the reminder.
Before asking a customer to pay, check the invoice, payment records, and remaining balance. A reminder based on the original amount can miss a payment the customer has already made.
Review the allocation.
For sample invoice INV-0022, the total is KES 65,000. Review a KES 25,000 payment against its payer and reference before allocating it. The remaining balance is then KES 40,000. An unclear payment stays in review until the team can resolve it.
Prepare a considered follow-up.
Use the confirmed remaining amount and invoice reference in the draft. Thank the customer for the part payment where appropriate. A person should review the wording and timing, and pause the reminder if the account needs a conversation.
- Confirm that recent payments have been reviewed.
- Check the invoice reference and remaining balance.
- Read the draft in the context of the customer relationship.
Check whether follow-up became easier.
Compare preparation time and the number of reminders needing a balance correction. Record the same tasks before and during the pilot. These checks assess the workflow; they do not by themselves prove that a customer paid faster.
What we would measure.
These are proposed checks, not achieved results. Agree the sample, definitions, and review period with the business before starting.
Balance corrections
Count drafts corrected before sending
Track the same check during the pilot
Preparation time
Time the account check and draft preparation
Compare similar follow-up tasks
Customer outcomes have not been measured for this example. Verified results can be added after an agreed pilot review and customer approval.
Start with one useful workflow.
See where your team fits