Risk-ranked work queues
Queues built from delinquency age, balance, loan product, channel, payment history and prior contact outcome — so the highest-recovery accounts are worked first rather than the alphabetically earliest.
Collections suite
Collections that work the book, not the list
Risk-ranked queues, promise-to-pay tracking, statutory notices, dialer and SMS integration and an agent desktop that shows the entire relationship — through to write-off, court filing and post-judgment payments.
6collections and contact-centre integrations pre-built
1screen with the whole borrower relationship
0exports needed to work a queue
Queues
Strategy, not a delinquency report
Notices on schedule
Missed-instalment notices, late-fee grace periods and collection notices generated from the loan state, with the timing and content the state requires. The wording is yours: notices and borrower communications come from your own templates, populated by mapping QFund’s existing placeholder values — so re-wording one is configuration, not a change request.
Dialer, SMS and IVR
Integrated with Five9, LiveVox, RingCentral, VoApps, Solutions by Text and TXT180 so the contact attempt and its outcome land back on the loan.
Partners →Promise to pay
Promises recorded against the account with due dates, kept/broken tracking and automatic re-queueing when a promise fails.
Right-party contact
Contact attempts, right-party contact and consent state tracked per phone number and channel.
Legal and recovery
Write-off, post-court-filing and post-judgment payment handling, plus bank deposit for redeposit and garnishment.
Agent desktop
One screen, whole relationship
A collections agent with three systems open is a collections agent reading a screen instead of listening to a borrower.
Collections is not a separate application — it is a view of the same core, so the whole relationship is already on one desktop. It is also the same screen layout your counter CSRs use, so an agent moved onto collections is productive immediately rather than learning a second system (one interface, every module).
With the AI assistant, the agent can take a payment, set up a plan or send a receipt by saying so, while keeping the conversation going.
On the agent’s screen
- Current balance, next due amount and payoff quote
- Full payment, reversal and NSF history
- Promises made, kept and broken
- Every contact attempt and its outcome
- Signed documents and issued notices
- Other loans and the borrower’s full history with you
FAQ
Collections questions
Do you replace our dialer?
No — QFund integrates with the dialer and contact-centre platforms lenders already run, including Five9, LiveVox, RingCentral and VoApps. The value is that the attempt and its outcome are written back against the loan, so queue strategy can use them.
Can we run collections in our own tool instead of QFund’s?
Yes. Collections activity — queue and account retrieval, contact attempts and outcomes, promises to pay, payment posting, notice and letter generation, status changes — is available through the RESTful JSON API, so a lender that has built its own agent desktop or standardised on a CRM can drive collections from there with QFund as the core. Webhooks push the events back the other way, so a broken promise or a returned payment reaches your tooling as it happens. API layer →
Can we keep using a third-party collections agency?
Yes. Placement with an agency, recall and reconciliation of agency payments are supported, and integrations exist with agency and recovery platforms including Remitter and Paydit.
How is compliance handled on contact attempts?
Consent state, contact attempt counts and right-party contact are tracked per number and channel, and notice generation follows the state configuration. QFund records what was done and when; your policy decides the limits, and the platform enforces them.
Show us your delinquency buckets
We will build the queue strategy live and show what an agent sees when the account surfaces.