A call, start
to finish.
Nothing about this is clever, and that is deliberate. It rings, it says who it is, it asks how you would like to settle, and it writes down the answer.
The shape of the script
Yours to change, and approved by you before anything happens.
ArohaKia ora, this is Aroha calling on behalf of Northbridge Joinery.
ArohaI am ringing about invoice 1055 for $3,460, which is 22 days past due.
CustomerI thought accounts had done that one.
ArohaNothing has come through yet. Would you like me to text you the invoice again?
CustomerPlease do. It will go out Thursday.
ArohaSent. I have noted Thursday against the invoice. Thanks for your time.
An illustration. Names, invoice numbers and amounts are made up.
Where it stops
The boundaries are built in. They are not switches somebody can find later and turn off.
The moment it is disputed
If the customer says the work was wrong, the amount is wrong or the invoice should not exist, the call stops being a reminder. It takes what they said, marks it for a person and emails your accounts inbox.
The moment somebody cannot pay
Hardship is a conversation for a human being. The caller takes the message and hands it over rather than negotiating a plan it has no authority to agree.
Anything outside the invoice
It knows your invoices and nothing else about the relationship. Asked something beyond that, it says so and passes the question on.
After one call
One per invoice per cycle. If you want somebody rung repeatedly, this is the wrong product and there is no setting for it.
What lands back on the invoice
A call that is not written down may as well not have happened.
Whether it connected
Answered, no answer, or wrong number. A wrong number is worth knowing before you chase again.
What was said
In the customer's own words rather than a summary that loses the bit that mattered.
What was promised
The date, if one was given, so you know on Friday whether Thursday happened.