A good reminder starts before writing the message.
Automating isn't sending the same demand to the whole base. First you have to know whom it's right to write to, with what information and when a person should step in.
1. Choose the balance you really want to communicate.
Total balance, overdue debt and current debt aren't the same thing. Check which field your system delivers and use it both in the rule's conditions and in the template. If there isn't enough information, don't fill the message with an estimated figure.
2. Separate reminders from campaigns.
A due-date notice and an offer for someone who stopped buying have different goals. Define separate rules and messages; check the template's approved category at Meta and don't assume every commercial message gets the same treatment.
Greeting with the customer's name.
Outstanding balance: data from their account.
Due date: date available.
How to pay: verified instructions.
A clear way to ask or request a review.
Don't copy the example's values as real data: templates must use the variables corresponding to each contact.
3. Set the pace and the exceptions.
Choose time windows, daily caps and minimum spacing between messages. Respect exclusions and no-contact requests. If the customer disputes the balance or needs special terms, the flow must lead them to a person.
4. Simulate and check the result.
Review recipients and text before activating a batch. Then distinguish candidates, sent, skipped and errors. A rule having thousands of candidates doesn't mean all of them are sendable in that run.
A "sent" status doesn't equal "read" or "paid" either. Measure each stage separately and check the statuses the channel provider reports.
Frequently asked questions
What people ask us most before getting started. If something's missing, write to us and we'll answer it.
Do all contacts that match a rule receive the message?
Not necessarily. After the conditions, exclusions, channel availability, time windows, limits and other protections are applied. You have to review the batch result, not just the number of candidates.
Does a receipt mean the payment is validated?
No. A received receipt is queued for review. A transfer detected by a payments integration follows a different circuit. Messages and reports must distinguish the two states.
Let's see how it would work in your company.
First we understand your operation. Then we define the data, the rules and the people involved.
I want to be contacted