Voice-assisted agent experience
Spoken commands drive real transactions — payments, receipts, refinances, quotes and lookups — instead of dictating into a note field.
New in the latest release
Say it, see it done
A next-generation voice-assisted agent experience with intelligent navigation. Agents state the outcome they want; QFund walks the screens, fills the fields and posts the transaction — while the agent keeps talking to the borrower.
Voiceassisted agent experience, not a chatbot
Navigationintelligent, from a spoken request
Fasterramp-up for new branch staff
The problem
Your best agents are your fastest typists
That is not a compliment to the software.
In a branch, the work is a conversation. In most lending systems, the work is a menu tree. The agent stops listening to the borrower in order to find the right screen, and a new hire spends weeks learning where things are rather than how lending works.
QFund attacks that on two fronts. The interface is modern and consistent — every module uses the same screen layout, so a new hire serves customers on day one (how the interface works). The AI assistant then removes the keystrokes: the agent states the outcome and QFund walks the screens, fills the fields and posts the transaction.
The borrower experiences an agent who is paying attention. The operation gets a shorter handle time and a much shorter training curve.
“Look up John Smith”
Customer found, profile opened
Open
“Take a $60 payment on loan 100428”
Payment screen opened, amount filled
Posted
“Email the receipt”
Sent to the address on file
Sent
Capabilities
What the assistant does
Intelligent navigation
Jump straight to the right screen for a spoken request, rather than walking a menu hierarchy to find it.
Faster agent ramp-up
New staff can be productive while they are still learning the system, because they describe the outcome rather than remember the path.
Always in context
Every command names what it acts on — a customer or a loan — so nothing is ambiguous. Once the borrower or loan is on screen, follow-on commands act on that context and stay short.
Inside your rules
Actions run through the same state rule sets, permissions and audit trail as a click. Voice is an input method, not a bypass.
Security →Shorter handle time
The keystrokes disappear from the call rather than from the compliance record.
Boundaries
What it deliberately does not do
The assistant does not make credit decisions
It is an operational aid for your staff. Underwriting stays with the configurable underwriting matrix and your policy, every action it takes is attributed to the agent who asked for it, and everything is written to the same audit trail as a manual transaction. Voice input does not widen anyone’s permissions.
Is this a borrower-facing chatbot?
No. It is an agent-facing assistant inside the lending system. Borrower self-service lives in QFund Online, and the website has a separate assistant for answering questions about QFund.
Does it make lending decisions?
No. Credit decisioning remains with the underwriting matrix you configure and the state rule set. The assistant navigates and executes what an authorised agent asks for — it does not approve, decline or price a loan on its own.
How is it audited?
Every action produces the same audit record as the equivalent manual transaction, attributed to the signed-in agent. Permissions are unchanged: if an agent cannot post a waiver by hand, they cannot post one by voice.
What if a branch is noisy?
Voice is an option, not a replacement. Every screen remains fully usable by keyboard and mouse, and agents mix the two — typically speaking navigation and lookups while typing anything sensitive or precise.
Hear it before you believe it
This is the part of the platform that does not translate to a slide. Ask for the live voice walkthrough and give the agent your own instructions.