The BNTouch borrower portal is a personalized mini-website you generate for each client. They log in with the last four digits of their SSN (or a password you set), and from there they see their loan progress, communicate with the team, complete the 1003 application, view shared documents, e-sign anything pending, and see who else is working on their file. The portal also has an integrated MAIA AI chat for mortgage and product questions, refinance benefit presentations the LO can push to specific clients, and a contact-us page that wires directly back into the CRM. The full configuration lives in options under borrower and partner portals.
By Yuri Polukeev, Founder of BNTouch.
What the borrower sees on the dashboard
The borrower portal is a complete website experience built around a single mortgage file. From the demo: “Using this portal site, your client will be able to stay up to date with information regarding their mortgage as it is updated by you and your [team]” [007sfOsyYLk m0]. So this is not a static login page; it is a live status portal that reflects every change you make on the file inside the CRM.
The dashboard shows loan progress metrics pulled directly from CRM data, plus a communication log: “These statistics are pulled from your CRM. To the right, the client can see a log of any communications with you through your CRM. This will include messages and images that you have sent” [007sfOsyYLk m2].
So when an LO sends an email or SMS from the CRM, the borrower sees that touch logged in their portal. Same for processor messages, partner messages, and document share notifications. The borrower no longer wonders if anyone is working on their file.
MAIA chat built into the borrower portal
MAIA, the BNTouch AI assistant, is available to borrowers inside their portal. From the walkthrough: “[They can] use the portal to help clients with questions they may have about their mortgage terms, their loan status, and the like. They can even ask her [things like], can I get a quote, to get help walking through the pre-approval process” [007sfOsyYLk m3].
This matters because borrower questions arrive at all hours. A borrower at 11pm who wants to understand what “underwriting” means doesn’t need to wait for the LO to come online; they ask MAIA inside the portal and get a clear answer. The LO gets the call only when the question is actually one a human needs to handle.
1003 application inside the portal
The 1003 lives inside the portal. “The best part about this loan application is that your clients can stop at any time without losing their progress. Whenever they click the save and [continue button, the data persists]” [007sfOsyYLk m4]. So a borrower who starts the 1003 on a Tuesday morning can pick up on a Saturday evening without re-entering the front half of the form. This is the difference between a 60% completion rate and a 25% completion rate on long forms.
Document storage and e-signature inside the portal
Documents you have shared with the borrower live in the portal under a documents view. The view distinguishes between two types: documents the borrower needs to sign electronically, and documents you have made available to them as reference (closing disclosures, rate sheets, prequal letters). From the demo: “[Documents available include] them [requested for borrower to] sign electronically, and a storage of files you have made available to them through your CRM. You can navigate between these lists using the toggle switch in the upper right corner” [007sfOsyYLk m5-6].
So a borrower who needs to sign a disclosure can find it instantly without hunting through inbox emails. A borrower who needs to reference an old rate sheet can find that too.
Refinance benefit presentations (admin-enabled feature)
One feature that is gated to admin activation but is worth knowing about: refinance benefit presentations the LO can push to specific clients. “[This feature can be enabled for your account by your administrator. It allows you to send short, clear presentations for your clients about the possible benefits of refinancing]” [007sfOsyYLk m7]. So when you spot a refi opportunity for a past borrower, you can push a personalized benefit presentation to their portal in addition to (or instead of) an email. The borrower opens the portal, sees the presentation framed in their numbers, and the conversation starts on stronger footing.
Loan contacts page (who else is working on this file)
Every borrower portal includes a loan contacts page that lists every partner involved in the file. “Any partners that are working with you for a client’s mortgage will be listed in the loan contacts page. Here all participating partners will be listed along with their role in the mortgage process and basic contact information” [007sfOsyYLk m8].
For a purchase transaction, this means the buyer can see the buying agent, the listing agent, the title attorney, the insurance contact, all in one place. They don’t have to hunt through emails to find phone numbers when they have a closing-week question.
Contact-us page wired back to CRM
The portal includes a contact-us page that routes messages back to the LO inside BNTouch. “Lastly, your clients can use the contact us page to get in touch with you directly. Here they can see any contact information you have entered for yourself in the CRM, and they can use the buttons below to call you, message you, [or email you]” [007sfOsyYLk m9]. Click-to-call from the portal. Click-to-message that lands as a new event on the tracker.
Configuration: where the portal lives in options
The portal is configured under options. “In the options tab of your CRM, look for the section titled borrower and partner portals, then click the client [portal sub-tab]” [007sfOsyYLk m10]. From there, you control which pages are visible, what notifications fire when, and the default login credentials.
One useful default to know about: “By default, your borrowers will be able to log in with the last four digits of their social security number. You can choose to set a default password for all of your clients here, and you can always add an individualized [password per client]” [007sfOsyYLk m11]. So you can use SSN-based auth (low friction for borrowers, who already know their SSN), a default account password (better security across an entire book), or per-borrower passwords for high-value or VIP clients.
A specific scenario: the portal handles the weekend that would have killed your Sunday
It is Saturday evening. Your borrower’s offer just got accepted on a Sunday-listing house. They want to know exactly what the next steps look like before they call you on Monday morning panicked.
With the portal: they log in, see their loan status (currently “pre-approved, awaiting purchase agreement”), see the document checklist (purchase agreement, updated income docs), see the loan contacts (their buying agent, you, the processor), and read a status note you posted earlier in the week explaining the next steps. They ask MAIA “what happens after I get a purchase agreement” and get a clear answer. They open Monday’s call already calibrated.
Without the portal: they call you Sunday morning, then again Sunday afternoon, then text you twice Sunday evening, because they have no way to see their own file.
Honest limits
- Portal access requires an invite. If you have not sent the borrower their portal invite link, they cannot log in. Make sending the invite part of your new-lead workflow, not a one-off.
- SSN-based default authentication is convenient but not high-security. For high-value clients or borrowers with privacy concerns, set an individualized password.
- Some features are admin-gated. The refinance benefit presentations feature needs to be turned on by an account administrator. If you do not see it on a client’s record, ask your admin to enable it.
- The portal reflects what you put in the CRM. If your loan status updates are stale in BNTouch, they are stale in the portal too. The portal is downstream of CRM data hygiene.
See the portal on a sandbox borrower
To walk through the portal as both an LO and a borrower on a sandbox account, request a demo. The borrower portal page covers the full client-side feature set.



