mortgagecrmfollow-up-boss

Follow Up Boss for Mortgage: Make a Real-Estate CRM Work for Loans

·Terrell Gentry·11 min read
Follow Up Boss for Mortgage: Make a Real-Estate CRM Work for Loans

You are on Follow Up Boss (FUB) because your referring agents live there, not because it was built for loans. Now you have to run a loan pipeline inside a tool designed for real estate transactions, and the default stages, fields, and automations do not match how a deal actually moves. This is how to make it workable without switching, and where it will still fall short.

Quick answer: To set up Follow Up Boss for mortgage, rebuild the pipeline stages to match your loan process (Lead, Application, Processing, Underwriting, Cleared to Close, Funded), add custom fields for loan type, LOS status, and target close date, and either add your referring agents as collaborators or track lenders in a custom field. FUB has no native loan origination system integration, so live loan status still requires a two-way sync or manual updates.

How to set up Follow Up Boss stages for a loan pipeline

Replace the default real-estate stages with the six that describe how a loan actually moves, because the out-of-the-box "New Lead / Nurture / Active / Closed" set was built to track a home sale, not a file through underwriting. A loan officer who leaves the defaults in place ends up with deals piling into "Active" for six weeks with no way to see whether the file is stuck in processing or waiting on the appraisal.

Your stages should mirror the milestones your team already talks about on the phone. A workable set for most brokerages:

  1. Lead — inquiry received, not yet contacted or pre-qualified.
  2. Application — borrower is filling out the 1003 or has started in the portal.
  3. Processing — application submitted, documents being collected and verified.
  4. Underwriting — file submitted to the lender or underwriter, awaiting conditions.
  5. Cleared to Close — conditions cleared, scheduling the closing.
  6. Funded — loan closed and funded.

Set a maximum days-in-stage expectation for each one so you can see aging at a glance. A file sitting in Processing for 14 days usually means a document never came back. That is the leak: a deal stalls waiting on the borrower, and nobody owns the nudge. FUB will show you the stage, but it will not tell you why the file is stuck or send the reminder for you.

If your agents and loan officers share the same FUB account, keep loan stages visually distinct from the agents' buyer/seller stages, or the pipeline view turns into noise. Some teams run a separate pipeline entirely for loans so the two do not collide.

What custom fields a loan officer should add in FUB

Add custom fields for the loan-specific data FUB does not track by default, because a real-estate CRM has no concept of loan type, rate lock, or LOS status. Without these, your loan officers keep the real numbers in a spreadsheet or the loan origination system (LOS, the software that actually processes and underwrites the file) and copy screenshots back and forth.

The fields worth creating first:

  • Loan type (Conventional, FHA, VA, USDA, Jumbo) so you can filter and route.
  • LOS status — a text or dropdown field mirroring the current stage in your LOS, updated as the file moves.
  • Target close date — the date the contract needs the loan to fund by.
  • Rate lock expiration — so a lock that is about to expire surfaces before it costs the borrower money.
  • Referring agent — the partner who sent the deal, if you are not adding them as a user (more on that below).
  • Loan amount and property address for reporting and quick reference.

The catch is that every one of these fields is a value someone has to keep current by hand. FUB does not read your LOS, so the LOS status field is only as accurate as the last person who remembered to update it. On busy files that is exactly when it goes stale. We wrote more about the trap of keeping two systems in sync by hand in how to sync your CRM with a system that has no API.

How to set up lender collaboration in Follow Up Boss

Follow Up Boss gives you two ways to connect lenders to a deal: add them as users so they can see and work leads assigned to them, or track the lender in a custom field. Which one you use depends on whether the lender needs to act inside FUB or just be recorded on the file.

Per FUB's own lender collaboration documentation, added lenders can only see leads assigned to them, and they cannot reassign those leads. That is a real limit if you expected a lender to help triage your whole pipeline. If you only need to know which lender is on a deal for reporting, the custom-field route is simpler and cleaner.

The richest live loan-status view inside FUB is tied to a specific integration: the two-way sync with Zillow Home Loans (ZHL), which pushes loan status back into FUB automatically. If you are not on ZHL, that automatic status pipe does not exist, and you are back to manual updates or a paid connector chain. We broke down exactly what that collaboration does and where it stops in Follow Up Boss lender collaboration: what it does, where it stops.

The three places Follow Up Boss won't work like a mortgage-native tool

Follow Up Boss handles the relationship side of a loan well and falls short in three specific places: live LOS status, mortgage-shaped follow-up sequences, and compliance texting. These are not configuration problems you can fix with better setup. They are gaps in what the tool was built to do.

Lead Planet describes FUB plainly as "not mortgage-specific," and that is the honest frame. It is a strong real-estate CRM you are asking to run a loan operation.

It won't show live loan status from your LOS

FUB has no native LOS integration, so the loan status you see is whatever a human last typed in. BNTouch states it directly: "Follow Up Boss has no LOS integrations because it was built for real estate," which leaves loan officers with double data entry and manually updating pipeline stages. FUB's own help documentation for its Leaf360 connector requires LOS API keys to pipe loan and document status in, and Agent Legend has documented teams stringing together a LOS to Leaf360 to FUB to Agent Legend chain — each one a separate subscription — just to keep stages current. Every layer is another bill and another thing that can break.

It won't run mortgage follow-up sequences the way you'd write them

FUB's Action Plans are built around a real-estate cadence, and its automated texting has a documented hard limit: per FUB's own help docs, an Action Plan's initial text will not send when the plan is triggered by an automation. In practice that means native texting is an initial message plus manual texting after that. An entire paid add-on business, CallAction, exists to fill this exact gap, and their framing is worth remembering: "follow-up doesn't fail all at once — it fades." A mortgage sequence that nudges a borrower for a missing pay stub on day three, day seven, and day twelve, in your loan officer's voice, is not something FUB does out of the box. This is the same leak we covered in Follow Up Boss automation: what it can't do and workarounds.

It won't decide your texting compliance for you

FUB has texting rules and controls, but it does not make your follow-up compliant on its own, and no setup guide should tell you it does. Mortgage texting sits under stricter scrutiny than a typical real-estate blast, and the rules about consent and timing are decisions your compliance team owns, not a checkbox in a CRM. Any automation you layer on should follow the rules your team sets and pause where a human needs to approve first contact.

This is the point where SalesOS fits on top of FUB rather than replacing it. SalesOS is the layer that fills these mortgage-specific gaps: it runs follow-up in your team's own voice and templates, keeps the LOS status field current instead of leaving it to whoever remembers, and works inside the CRM and the Claude or ChatGPT account you already pay for. It follows the rules your team sets and waits for your yes on first contact and anything that goes out publicly. You can see how AI Cofounder works if you want the full picture of what runs on its own and what waits for approval.

Follow Up Boss vs. a mortgage-native CRM: which fixes your problem

Switching to a mortgage-native CRM fixes the LOS gap but usually does not fix the real bottleneck, which is the follow-up and pipeline hygiene inside whatever tool you use. If your referring agents are on FUB and it is working for them, moving your loan side onto a separate platform trades one seam for another.

Follow Up Boss (configured for loans)Mortgage-native CRM (e.g., LoanOfficer.ai, BNTouch)
Shared with referring agentsYes — they already live hereNo — a separate system your agents won't use
Live LOS statusManual, unless on ZHL two-way syncOften built in
Mortgage sequencesReal-estate cadence, texting limitsBuilt for loan milestones
Migration costNone — you're already on itRip and replace your whole stack

LoanOfficer.ai markets an all-in-one that automates follow-up, syncs the LOS, and reactivates old leads with "no third-party tools needed" — meaning you move your entire business onto their platform, including the shared workspace your agents rely on. That is a real tradeoff, not a free upgrade. We laid out the fuller version of this decision in AI mortgage CRM vs. adding AI to the CRM you already have and best mortgage CRM for a small team (the real problem).

Common pitfalls when setting up FUB for a mortgage team

The most common mistake is treating the LOS status custom field as if it updates itself. It does not, and a stale status field is worse than no field, because your team trusts it and acts on the wrong information.

  • Leaving the default real-estate stages in place. They hide where a loan is actually stuck. Rebuild them around loan milestones.
  • Adding a lender as a user expecting full pipeline access. They can only see leads assigned to them and cannot reassign. Confirm this matches what you need before you set it up.
  • Assuming Action Plans will text borrowers automatically. The initial text will not send from an automation trigger, so your sequence quietly stops before it starts.
  • Mixing loan stages and agent buyer/seller stages in one pipeline. The view becomes unreadable. Run a separate pipeline for loans if your team shares the account.
  • Treating FUB texting as compliant by default. It follows the rules you configure; your compliance team decides what those rules are.

FAQ

Does Follow Up Boss integrate with a loan origination system?

Follow Up Boss has no native LOS integration because it was built for real estate. To get live loan status into FUB you need a two-way sync like Zillow Home Loans, or a paid connector chain such as LOS to Leaf360 to FUB, each requiring API keys and its own subscription.

Can loan officers use Follow Up Boss?

Loan officers can use Follow Up Boss, and many do because their referring real-estate agents already work in it. It handles contacts, follow-up, and shared visibility well, but it needs custom stages and fields to track a loan pipeline, and it will not pull live status from your LOS.

How do I add a lender to Follow Up Boss?

You add a lender in Follow Up Boss either as a user, where they can see and work only the leads assigned to them, or by creating a custom "lender" field to record which lender is on each deal. Added lender users cannot reassign leads, so choose the method that matches how much the lender needs to act inside the system.

Is Follow Up Boss good for mortgage brokers?

Follow Up Boss works for mortgage brokers as a relationship and follow-up CRM, especially when their referring agents are already on it, but it is not mortgage-specific. Live loan status, mortgage-shaped sequences, and compliance texting are the three areas where it falls short of a mortgage-native tool, and they usually need a layer on top rather than a switch.

If your FUB is configured well and the follow-up and LOS status are still the thing that leaks, that is exactly the gap SalesOS was built to close on top of the CRM you already run. Book a demo and we'll walk your actual loan process and show you where it fits.

About Terrell Gentry

Founder at 6omb

Terrell is the founder of 6omb and runs Claude Community, the #1 Skool community for Voice AI agents. Over 16 months his team has built 100+ AI agent systems delivering $10M+ in business value, including voice agents like Emily, which booked 453 new clients for a law firm in 8 months. He is a Y Combinator Startup School alum (SUS20) and a Gold Retell partner.

AI AgentsClaude CodeVoice AIBusiness AutomationGrowth Marketing

Close more of the deals you already have

SalesOS follows up with every lead in your own voice, keeps your CRM in sync, and shows you where every deal stands. See it working on a pipeline like yours.

Book a Demo