Clara adapts to the way your company works.
Clara carries out your loan-processing tasks autonomously in your existing LOS and approved portals, following your company’s SOPs and lender requirements. She brings exceptions that need judgment to your team.
During onboarding, we map your processes, approved systems and tasks, then test the workflow on two or three files.
Clara works inside
Workflows built around your team.
Message Clara in Slack, Teams, SMS or email. Ask for a task or a file update. Clara follows the workflow set up for your company, works in the relevant systems and records the result.
Your team sends the task
In your team’s approved messaging channel
Clara works in the relevant system
She retrieves the record from the county or public-records site mapped during onboarding.
Within the access and task scope you agreed
The result returns to your LOS
The record is filed with the loan. The activity log shows what happened, and Clara replies to your team.
Record filed · Activity logged
Across the systems your files need
Alongside your LOS, Clara can work in approved lender and investor portals, FHA Connection, and county or public-records sites. We map the portals, company SOPs and lender or investor guidelines for the tasks your team wants her to handle.
Using Empower, MeridianLink Mortgage, Byte, Mortgage Cadence, Calyx Point or LoanQuest? Talk to us about whether Clara can handle the work your team needs.
See the condition log on Results for work recorded on a live file.
What Clara reads and writes
- Reads:
- the loan file, its open conditions, the document list, and where the file sits.
- Writes:
- documents filed against the condition they answer, condition status and notes, submission records, and the loan status your team reads.
- Never touches:
- pricing, credit decisions, AUS findings, or your milestone triggers.
Items that need judgment stay on your processor’s list.
How Clara handles a conflicting edit
If someone on your team edited the file while Clara was working, her change waits and your processor sees the conflict.
Clara works the condition list in your underwriter’s wording. When a document does not match the condition, she stops and puts the item on your processor’s list.
How Loandock connects
Where your system offers a direct connection, Loandock uses it. Where it does not, Clara signs in to the systems you approve and works the screens the way a person on your team would.
Access stays with your admin
Your admin issues the login, assigns the role, and sets what it can reach on day one. You can narrow it or shut it off in one step. Clara works with the credentials you issue, in the systems you name, and nowhere else.
Every write is logged
Every write is logged with its timestamp, who made it, the loan file it touched, and the document behind it. Borrower and third-party messages are logged the same way.
How borrower data is handled
- The work runs in the United States.
- Borrower documents and messages are encrypted in transit and at rest.
- Your LOS stays the system of record. The file of record is yours, in your instance.
Retention, deletion and incident terms are on the security page.
Book a walkthrough

