Loan officer reviewing CRM work with an AI assistant and human approval
Short answer: BNTouch describes MAIA as an embedded assistant that works with CRM records and sales-pipeline context. Its published material describes retrieving records, drafting communications, creating or updating tasks, notes, and statuses on user direction, scheduling reminders, and summarizing conversations. A loan officer remains responsible for checking borrower-specific facts, choosing the next action, and approving every communication or record change that matters.
What MAIA is designed to help with
Workflow
Published MAIA role
Human-review boundary
Find a record or pipeline context
Retrieve CRM records and related information on demand.
Confirm the selected borrower, stage, and relationship context before acting.
Prepare follow-up
Draft email or borrower communication from CRM context.
Review facts, recipient, tone, company policy, and any required disclosures before sending.
Document a next step
Create or update tasks, notes, or statuses on user direction.
Check the record history and make sure the task owner, due date, and status are right.
Plan follow-up
Schedule reminders and surface tasks connected to a loan record.
Decide whether the timing and message are appropriate for that relationship.
Understand a conversation
Summarize a recorded conversation in the CRM.
Compare the summary with the underlying record before relying on it.
Four safe workflow examples
1. Prioritize a follow-up queue
Ask MAIA to surface records with a specified status, recent activity, or missing next step. The loan officer reviews the resulting list, determines priority, and assigns the outreach. The useful proof is not that an answer appeared. It is that the user can inspect the records behind it.
2. Draft, then review, a borrower message
Use CRM context to prepare a first draft. Before sending, the loan officer checks that the message reflects the actual loan stage and relationship, then applies the organization’s communication policy. A drafted message is input to human work, not a final decision.
3. Turn an approved conversation into a task
After a conversation is reviewed, ask MAIA to create a task or note. The user verifies the owner, due date, and wording in record history. This is especially useful when a handoff would otherwise live only in a memory or inbox.
4. Summarize before a handoff
Ask for a concise history of the relationship before a referral-partner or team handoff. The receiving user checks the source record and adds context that should not be assumed from a summary alone.
What to ask in a MAIA workflow walkthrough
Which CRM records and fields does the request use?
Can the user see the source context behind the response?
Which actions change a record, and where does the change appear in history?
What requires a user to review, approve, or edit before it is used?
What is intentionally outside the product’s role, including underwriting and legal judgment?
What this guide intentionally does not claim
BNTouch has published a separate MAIA NextStep walkthrough that labels the feature as beta. This guide does not treat that beta workflow as a general current capability. It focuses on the published, user-directed CRM work that can be reviewed in a live walkthrough: finding context, preparing a draft, documenting a next step, and checking record history.
For a mortgage workflow, the most credible AI claim is a narrow one: MAIA can help a user find, prepare, document, and organize work inside the CRM. It should be evaluated by whether a person can understand, review, and own the result.
