SkillRetaining
Chasing Overdue Payments
Polite, and it doesn't forget
What is Chasing Overdue Payments?
Chasing Overdue Payments is a receivables-tracking method that reminds customers of payments as they fall due and after, forwards the payment link, and records the date the customer promises. luup binds the tone of reminders to the conversation rules rules; wording that implies threat or legal action is blocked, and the payment date the customer gives is recorded as a commitment.
Chasing payment is the job nobody wants; overdue money piles up.
The reminder goes on time and in the same tone, and the promise given is recorded.
How does it work?
- 1
Due dates are watched
Payments approaching and past their due date are listed.
- 2
A reminder goes
Reminders are sent at defined intervals, in a defined tone.
- 3
The link is sent
The payment link or account details are shared.
- 4
The promise is recorded
The payment date the customer gives is recorded as a commitment.
What does it need?
A skill with a missing precondition is not hidden in the panel — it is shown with the gap. Hiding what is required only produces disappointment during setup.
- An invoice or receivables record
- At least one messaging channel
What it deliberately does not do
Claiming a result is easy. What follows is not a claim but a set of limits the product enforces mechanically: the skill cannot do these things, because a layer that cannot be switched off stops it.
- It uses no threatening language and implies no legal action.
- It sends no collection message during quiet hours or on public holidays.
- If the balance is disputed it stops the chase and hands the case to you.
Where it sits on the autonomy ladder
A 0–4 ladder decides how much the assistant may do without asking you, and it is set separately for each channel and each topic. The meaning of each rung is the same across every skill.
Chasing Overdue Payments comes into play at rung 2 of the ladder.
- 0
Listens only
Writes nothing to customers; it only records.
- 1
Drafts a reply
Writes it but does not send it; the draft waits in the panel.
- 2
Waits for approval
The reply is ready; sending it is your decision.
- 3
Answers on its own
Sends, and stops to call you in when it gets stuck.
- 4
Full authority
Books, quotes and collects payment.
Wherever the ladder sits, every outgoing message passes the Conversation Rules and the consent check; neither layer can be switched off.
SSS
Sık sorulanlar
The tone is entirely your definition and is subject to the conversation rules rules. The default tone is polite; wording that implies threat, pressure or legal action is blocked by the rule layer.
Yes. The date the customer states is recorded as a commitment, and if payment has not happened by then, a fresh reminder goes. Promises kept and broken are shown separately.
Your invoice and receivables records can be connected through an integration; where they are not, receivables are imported into the panel manually or by file. The skill works the same way in both cases.