Outbound call
Payment reminders
A polite reminder with a payment link. No pressure, ever, by design.
- Opened with
- AI disclosure and consent
- Resolved in call
- Dispute routed, not argued
- Handed over
- Accounts, with invoice open
One real call
Press play and read it as it ran.
What it handles on its own
Resolved while the caller is still on the line.
- Reminders timed to your dunning schedule, only inside permitted calling hours for the caller region
- Reads the invoice number and the exact amount, never a rounded or inflated figure
- Sends a payment link by SMS during the call and confirms it arrived
- Takes a stated payment date and writes it to the account for your team to see
- Records a clear opt-out and never dials that number for reminders again
- Leaves a short, neutral voicemail when there is no answer, with no amount disclosed
When it hands over
Straight to a person, with no second ask.
- Any dispute, the moment it is raised. The reminder script stops there
- Any request for a discount, a waiver or a payment plan
- Hardship, bereavement or medical circumstances mentioned by the caller
- A third party on the line who is not the account holder
The person who picks up receives the call summary, the caller details and everything already done on this call, before they speak.
Five settings decide how this call behaves.
Nothing here is a hidden model behaviour. These are the knobs you own, reviewed with you before the first live call and changeable afterwards without a rebuild.
- Schedule
- Days past due, retry count and the gap between attempts
- Hours
- Permitted calling windows per region, enforced in the dialer
- Script
- The exact reminder wording, reviewed before a single call goes out
- Suppression
- Do-not-call lists, opt-outs and accounts in dispute
- Escalation
- The accounts queue that receives every dispute handoff
A week, in three moves.
This call type does not need a migration project. It needs your number pointed at us, your rules written down, and one week of reading the transcripts closely.
- Day 1
Point the number, connect the system
A forward or a SIP trunk, plus read access to the one system this call depends on. Nothing changes for your callers yet.
- Day 2 to 4
Write the rules down
Your allowed actions, your handoff triggers, your wording. We run the first calls against your real data with your team listening in.
- Day 5 onward
Read the transcripts
Every call is on the record. The handoff log tells you exactly which rule to loosen or tighten, and changes take effect on the next call.
Can Zimaao take this call for us?
Point your number at me, tell me what I am allowed to resolve, and I will take the next payment reminders call that comes in.