Follow Up Boss Automation: What It Can't Do and Workarounds

Follow Up Boss runs a lot of your team's day. It sends drip emails, assigns leads, fires action plans. But you have probably hit the wall where the automation stops and someone has to remember the rest, and the deals that leak out that gap are the ones you paid for.

Quick answer: Follow Up Boss automation handles round-robin lead assignment, action plans, drip email, and trigger-based tasks well. It hits real limits on text follow-up (it stops the moment a lead replies and won't run compliant two-way texting on its own), on custom fields nobody keeps clean, and on syncing with tools outside its ecosystem. Teams work around these with human follow-up, field discipline, and a separate layer that reads the CRM and acts on what's stalled.

What Follow Up Boss automation actually does well

Follow Up Boss automation is strongest at the mechanical, one-directional work: assigning a new lead the second it lands, starting an action plan, and sending the first few emails on a schedule. If a lead comes in from Zillow or your site, FUB can route it by round-robin, tag it, start a drip, and create a task for the assigned agent. That part works and it works fast.

The tool calls its automation "action plans" and "automations." Action plans are step sequences (send this email, wait two days, send this text, create this task). Automations are trigger-and-action rules (when stage changes to X, do Y). Between them you can build a decent first-touch machine. The problem is not the first touch. It is everything after the lead does something you did not script.

Why Follow Up Boss text automation stops when the lead replies

Follow Up Boss text automation stops the moment a lead texts back, by design, because a human is supposed to take the conversation from there. That is the single biggest leak in most FUB setups. Your action plan fires three texts, the lead replies "still looking, call me next month," and the sequence ends. Now the only thing standing between that lead and a closed deal is whether a loan officer remembers to reach out in thirty days.

There is a second wall on texting. FUB and the carriers enforce rules on automated messaging (consent, opt-out handling, message volume), so you cannot just point a bot at your database and blast. The CRM's compliance guardrails block a lot of what people imagine "text automation" means. This is a good thing for staying out of trouble and a bad thing if your plan was to automate your way past follow-up entirely.

The manual workaround is what most teams do: they let the action plan handle first contact, then rely on people to carry every reply. The known failure of that workaround is memory. As we wrote in working the leads nobody has time for, the leads that die are almost never the ones your team decided to drop. They are the ones nobody circled back to because there was no system reminding them.

This is where SalesOS fits. SalesOS is not a CRM and does not replace Follow Up Boss; it reads what is in FUB and keeps the follow-up going after the lead replies, in your team's own templates and voice, within the texting rules your compliance team sets, until the lead acts or is clearly dead. Your team decides what those rules are; the system follows them.

Custom fields nobody reads, and how to make them earn their keep

Custom fields in Follow Up Boss are only as useful as the discipline behind them, and on most teams that discipline erodes within a quarter. Someone sets up a "Pre-Approval Status" field, three people fill it in for a month, and then it goes stale because nothing depends on it. The field exists; the data does not.

This is the "outcome-only" problem researchers see across CRM integrations: the system logs a code or a stage but not the detail behind it, so managers cannot tell a good lead from a dead one at a glance. A stage of "Nurture" tells you nothing. A field that says "waiting on 2023 tax return since Oct 12" tells you exactly who to nudge.

Three practices make custom fields worth having:

The reason clean fields matter beyond tidiness: any layer you add on top of FUB, including SalesOS, reads those fields to decide what is stalled and who to chase. Garbage in the field means the automation chases the wrong deals or misses the right ones.

Syncing Follow Up Boss with the rest of your stack

Follow Up Boss syncs cleanly with tools in its own ecosystem and struggles with everything else, especially your loan origination system (the LOS where the actual loan file lives). FUB has an API and native integrations for lead sources and dialers, but the systems that matter most to a mortgage team, and the industry systems many partners use, often have no clean connection. So people copy-paste. An assistant reads a status in the LOS and types it into FUB, or screenshots a document checklist and pastes it into a note.

Two failure modes show up over and over when teams wire these together, and both come from the same research on CRM syncs:

The honest answer for systems with no API is that a person's browser actions can be automated the same way a person does them, clicking through the screens, reading the status, and writing it back. We walked through that approach in how to sync a CRM with a system that has no API. It is not magic. It is a system doing the copy-paste a human was doing, without forgetting and without the typos.

The workaround most teams settle for is a weekly status meeting to reconcile what the systems disagree on. That meeting is the tax you pay for tools that do not talk. The alternative is one layer that reads FUB, reads the LOS, and keeps them in agreement so nobody exports a report to find out where a deal stands.

Manual workarounds vs a layer on top of Follow Up Boss

Every limit above has a manual workaround, and every manual workaround has a known failure. The table is the fastest way to see where the leaks are.

A layer on top of FUB does the boring work these workarounds depend on a human to remember: it keeps following up after the reply, it reads the fields to find what is stalled, it nudges the borrower for the missing document, and it keeps the referral partner updated without a phone call. For getting borrowers over the finish line specifically, we broke down the document-chasing sequence in get borrowers to finish the application and send documents.

Common pitfalls when automating Follow Up Boss

The most common pitfall is trying to automate every exception at once instead of the common case first. Teams map out the perfect flow for the rare deal and never ship the sequence that covers the 80 percent. Build the narrowest high-value path first, usually the first follow-up sequence, then widen.

FAQ

What are the main limits of Follow Up Boss automation?

Follow Up Boss automation stops text sequences when a lead replies, cannot run unrestricted two-way texting on its own because of carrier and consent rules, relies on custom fields that go stale without discipline, and does not sync cleanly with systems outside its ecosystem like most loan origination systems. Each limit forces a manual workaround that depends on someone remembering.

Can Follow Up Boss send automated texts?

Follow Up Boss can send scheduled texts inside action plans, but it stops automated texting the moment a lead replies and enforces carrier rules on consent, opt-outs, and volume. It is built so a human takes over the conversation after first contact, which is why follow-up after a reply falls back on someone remembering to do it.

How do you sync Follow Up Boss with a loan origination system?

Syncing Follow Up Boss with a loan origination system works either through an API where one exists or, where it does not, by automating the same browser steps a person would take to read status and write it back. The two things to guard against are duplicate contacts (match on email or phone, never name) and syncs that log a stage change but drop the note or document behind it.

Why do custom fields in Follow Up Boss stop getting filled in?

Custom fields in Follow Up Boss stop getting filled in when nothing depends on them. If no automation, report, or task reads a field, the team has no reason to keep it current, and it goes stale within a quarter. Tie every field to a trigger or view and give it an owner, and it stays clean.

Does SalesOS replace Follow Up Boss?

SalesOS does not replace Follow Up Boss or act as a CRM. SalesOS works with the CRM your team already has, reading what is in Follow Up Boss to keep follow-up going after a reply, chase stalled deals, and keep systems in sync, so you keep your CRM and close the gaps around it.

If your Follow Up Boss setup is leaking deals at the reply, the stale field, or the LOS handoff, the fastest way to see what a layer on top of it would catch is to walk through your own process with us. Book a demo and we will map where your pipeline leaks before anyone builds a thing.