Verify and hear account status
Zip code and the last four of the SSN, like the portal login. Current callers hear their next payment; past-due callers hear where they stand.
Techelogy Virtual Assistant verifies callers, reads their loan straight from Lendisoft, and walks them through payment details, promises to pay and account updates. It follows your approved script, with the exact compliance wording supplied by code.
For English, say English or press 1. Para español, diga español u oprima el 2.
Thank you for calling ABC Finance. This call may be monitored or recorded. I’m a virtual assistant…
Thank you. Am I speaking with John?
Yes, that’s me.
This is an attempt to collect a debt, and any information obtained will be used for that purpose.
The assistant follows the Lendisoft Self-Service Consumer Portal, so callers get the same answers they would online, in their own words. Parts that need texts or new Lendisoft data are on the roadmap.
Zip code and the last four of the SSN, like the portal login. Current callers hear their next payment; past-due callers hear where they stand.
Amount due with its breakdown, balance, rate and remaining payments, read straight from the loan record.
Recent payments, and the payoff amount with its good-through date.
Terms read word for word, a date within 7 days, a read-back, and the promise recorded on the account.
Offered only to eligible accounts, under your Lendisoft rules, with the hardship reason in the caller’s own words.
Being verifiedEmployer and insurance updates, spelled back before saving; address and phone updates are being verified. Callers can leave a voice message for your team.
A language model alone can paraphrase a disclosure, skip a step or hear digits it shouldn’t. So the parts your script makes mandatory are enforced by code around the AI: the order of steps, the timers, the keypad, and the exact text of each compliance line.
Your staff sign in to an operations console with their own Lendisoft login. Calls, transcripts, tool actions and voice messages are recorded and reviewable, with roles that decide who sees what.
The assistant works on top of your Lendisoft tenant through its API. Your loan system stays the source of truth.
Your lender name, languages, which self-service actions to offer, and how callers reach your team.
Test calls in the browser console first, review every transcript, then connect your support number.
Lendisoft tokens and provider keys are sealed with AES-256-GCM, bound to the record they belong to.
Keyed digits are checked on the server, not by the AI. Phone recordings are muted while they are entered.
Staff act as themselves in Lendisoft, with its two-factor sign-in. No shared service passwords in the console.
No. It never collects card or bank details by voice. Today it explains how to pay online and logs the request. Texting a secure Payment Portal link, and confirming the payment on the call, is on the roadmap.
Not yet. The full call flow runs today in a browser console for testing. The phone line is built and tested, and its first live calls come next: borrowers call, the assistant verifies them and shares loan details and payment history, and calls are recorded with SSN entry muted.
Callers can ask for a representative at any time. Today they leave a voice message for your team; messages from verified callers are noted on their account. Warm transfer to your queues is on the roadmap.
Callers are asked to key the last four digits. Keyed digits are checked by our server against Lendisoft; the digits are not passed to the AI, the logs or the call record. On the phone line we are confirming that keypad tones in the call audio do not reach the AI before any live calls. The assistant never reads an SSN, card or bank number back.
It is built for the Lendisoft LMS and reads and writes through the Lendisoft API. It works from the same loan record your team uses, with personal details it doesn’t need filtered out, and changes are recorded where they belong.
Tell us about your lending operation and we’ll set up a demo on a Lendisoft test tenant.