How a debt-recovery team automated 9 in 10 of its inbound calls
An Auckland debt-recovery firm turned its biggest daily distraction, the phone, into a system that mostly runs itself, and got about 20 hours a week back.
9 in 10
Calls handled automatically
20 hrs
Returned to the team weekly
1 month
From kickoff to live
Jade Financial Services, an Auckland debt-recovery firm, was fielding 30 to 50 calls a day, mostly the same questions: what is my balance, when was my last payment, how much is left to pay. Every call pulled someone off recovery work, and their customer database lived only in a spreadsheet. We built a voice agent that verifies the caller, reads their live account data, and answers those calls itself. It now handles around nine in ten calls without a human, gave the team roughly 20 hours a week back, and went live in a month.
In debt recovery, the phone never stops. Jade Financial Services runs collections across New Zealand and Australia, and on a normal day their team takes 30 to 50 inbound calls. Almost all of them are the same handful of questions: what is my balance, when was my last payment, how much do I still owe, when is my next one due.
None of those calls need a skilled person. But every one of them pulled a skilled person off the actual recovery work to answer it. And to answer it, that person had to go digging through a spreadsheet to find the account first.
Why were 30 to 50 calls a day such a problem?
A debt-recovery team makes its money by working accounts, not by reading balances down the phone. Every routine call was an interruption: stop the recovery work, find the caller in the spreadsheet, read out a number, get back to what you were doing.
Across 30 to 50 calls a day, that added up to roughly 20 hours a week of skilled time spent on questions a system could answer. The data that should have made it easy, their customer database, made it harder, because it only existed as a spreadsheet nobody could query in real time.
~20 hours a week, gone to the phones
Skilled recovery staff answering balance and payment questions a verified system could handle on its own.
What does the voice agent actually do on a call?
It answers the phone, verifies who is calling, and handles the routine account questions end to end, reading from live data.
It verifies before it shares anything
The agent identifies the caller one of two ways: their account number if they have it, or their name plus date of birth and address as verification. Only once the caller checks out does it pull up the account. For a finance business, that verification step is the security, built into every call.
It answers the questions that fill the day
Once verified, the caller can ask the things they always ask: how much is left on my account to pay, when was my last payment, what is my current balance, when is my next payment due. The agent reads the answer straight from their live account and gives it on the spot, any hour of the day.
It only escalates when it should
Around one call in ten is handed to a human. Anything sensitive, or outside the routine questions, gets escalated rather than forced through the agent. The team stops fielding the easy 90% and keeps the calls that genuinely need them.
Why move their data out of a spreadsheet?
A voice agent is only as good as the data behind it, and Jade's ran on a spreadsheet. Their entire customer database, across New Zealand and Australia, lived in Excel. Useful to a person clicking through it, useless to anything that needed to read it live.
We cloned that database into a secure cloud database with a daily sync, so it stays current without changing how the team works. Access is locked to owner and admin only. That one move did two things: it gave the voice agent live account data to read from, and it gave the business a real database to build on instead of a file that only worked one click at a time.
What was the real return?
The agent now handles roughly nine in ten of the 30 to 50 daily calls, which gives the team back about 20 hours a week, close to a thousand hours a year of skilled time returned to recovery work.
| Inbound calls a day | 30 to 50 |
| Handled automatically | ~9 in 10 (90%) |
| Escalated to a human | ~1 in 10 (10%) |
| Team time returned | ~20 hours a week |
| Otherwise needs | a receptionist (~NZD $55,000 / yr), 9 to 5 only |
| The agent runs | 24 / 7 |
| Kickoff to live | 1 month |
The work the agent does, fielding and verifying routine account calls, is what you would otherwise hire a receptionist for: around NZD $55,000 a year, working business hours only. The agent does roughly 90% of that volume, around the clock, for a fraction of the cost.
Why not just hire a receptionist?
Because the maths does not work. A receptionist to field those calls runs around NZD $55,000 a year all in, works nine to five, takes leave, handles one call at a time, and still has to look up every account in the spreadsheet by hand. The voice agent handles around nine in ten calls 24/7, verifies the caller and reads live data instantly, and never has a bad day on the phones. The team keeps the calls that actually need a person.
“We receive 30 to 50 phone calls a day, constantly distracting our team from what they are working on. Sentry's AI voice receptionist means we only get phone calls when it is absolutely mandatory, and the majority of calls are automated, freeing up hours and hours of time per week for our team.”
Could this be your team?
If your team is buried under inbound calls that mostly ask the same routine questions, or your business runs on a spreadsheet that can never become anything smarter, this is exactly the kind of problem we solve. We start with a Discovery Week: we find your single biggest win, scope it, and ship a first working piece fast, so you feel the value before any bigger decision.
Contact UsFrequently asked questions
Is customer data secure?
Yes. Their customer records moved off a shared spreadsheet into a proper cloud database with access locked to owner and admin only. The voice agent never reads anything until the caller is verified, and the whole setup operates under the New Zealand Privacy Act 2020.
How does the agent know it is really the customer?
It verifies before sharing any account detail. The caller gives their account number, or, if they do not have it, their name plus date of birth and address. Only then does the agent pull up the account.
What happens with sensitive or complex calls?
About one in ten calls is handed to a human. Anything outside the routine account questions, or anything that needs a person, is escalated rather than forced through the agent.
Will customers actually talk to an AI?
For routine questions, they prefer it. The agent answers immediately, any hour of the day, with no hold music, and resolves the common queries (balance, last payment, amount left to pay) on the spot. The calls that need a person still get one.
How fast can it go live?
Jade went from kickoff to live in a month, including cloning their data into the cloud and standing up the daily sync.