Follow Up Boss Automation: Limits and Workarounds

You set up Action Plans in Follow Up Boss, wired the smart lists, and figured lead follow-up was handled. Then the automated texts stopped firing, half your custom fields went stale, and the loan officer still didn't know a borrower had replied three days ago. Follow Up Boss does a lot, but it has hard edges, and the deals leak right at those edges.

Quick answer: Follow Up Boss automation handles lead assignment, drip email, and Action Plan triggers well, but it can't reliably automate texting the way most teams want (its own rules and carrier rules throttle it), it can't force anyone to read a custom field, and it won't keep your loan origination system or inbox in sync on its own. Teams work around these limits by keeping a human in the loop on texts, cutting custom fields down to the few that drive action, and adding a layer that syncs Follow Up Boss with the rest of the stack.

What Follow Up Boss automation actually does well

Follow Up Boss automation is strong at the structured, rules-based work that fires the same way every time: routing a new lead to the right agent, starting an Action Plan when a lead hits a stage, sending drip email on a schedule, and updating a lead's stage when something changes. If your process is "new Zillow lead comes in, assign to the pod on rotation, start the 14-day email sequence," Follow Up Boss handles that cleanly and has for years.

The trouble starts where the process depends on judgment, on a channel Follow Up Boss doesn't fully control, or on a system that lives outside Follow Up Boss entirely. That is most of what actually loses deals.

Why Follow Up Boss text automation is limited

Follow Up Boss text automation is deliberately restricted, and it is not a bug you can configure away. Follow Up Boss limits fully automated texting because carriers and messaging rules (the A2P 10DLC registration every business texting number now goes through) throttle or block traffic that looks like bulk automation, and Follow Up Boss would rather protect your number's ability to send at all than let you blast unregistered automated texts.

In practice that means the drip texts you imagined don't behave like drip email. You can trigger a text from an Action Plan, but volume, timing, and content all get watched, and the moment a lead replies, most teams want a person to take over anyway because the reply is where the deal actually opens. This is the same failure the boring work most teams never get to describes: the sequence fires until the lead engages, then falls back on someone remembering to keep going.

Nothing about texting compliance is something a tool can promise you away. Your compliance team decides what your numbers are allowed to send and how. Any automation you add, inside Follow Up Boss or on top of it, should follow the rules your team sets, not the other way around.

The workaround: keep a human on the reply, automate the reminder

The teams that get the most out of Follow Up Boss text automation split it in two. Use Action Plans for the first outbound touches that are safe to schedule. Then, the instant a lead replies, route it to a person and turn the automation into a nudge system instead of a sender: a reminder that a reply has sat unanswered for two hours, a flag that a lead went cold after three touches, an escalation when nobody has responded by end of day. The text still goes out in a human's voice; the machine just makes sure the human doesn't forget.

The custom fields nobody reads

Custom fields are the most quietly broken part of most Follow Up Boss setups: teams create dozens of them, populate maybe a third, and read almost none. A field only helps if something acts on it. A "Pre-Approval Expires" date that lives in a custom field but triggers no reminder and shows up on no list is just data decay.

The pattern shows up the same way in voice-agent CRM work, where the top silent-sync failure is mismatched picklists and fields that never map cleanly between systems. A field that half the team fills in and the other half ignores is worse than no field, because now your smart lists are built on data you can't trust.

The fix is subtraction, then wiring. Cut your custom fields down to the handful that actually drive an action: the ones a smart list filters on, the ones an Action Plan branches on, the ones a report is built from. For a mortgage team that is usually a short list, such as loan stage, expected close date, document status, and referral partner. Every field that survives the cut should have a job. If you can't name the automation or the report that reads a field, delete it.

Where Follow Up Boss automation stops: the rest of your stack

Follow Up Boss automation ends at the edge of Follow Up Boss. It does not know what your loan origination system (LOS) knows, it does not read your shared inbox, and it does not update the referral agent who sent you the deal. Follow Up Boss has an API (the connection that lets other software read and write your Follow Up Boss data), so those handoffs are possible, but the API doesn't build the workflow for you. Someone still has to decide what syncs, when, and in which direction.

This is where the copy-paste routine takes over: someone checks the LOS, opens Follow Up Boss, updates a stage by hand, then texts the agent an update. Every hop is a place a deal stalls because a human had to remember. The two failure modes that show up again and again in CRM sync work are the outcome-only update that logs a status code but none of the detail (so nobody can see why a deal stalled) and the duplicate-contact explosion, where an integration creates a new record instead of matching the existing one and leaves you with three to eight copies of the same borrower within months.

Manual sync vs a layer that keeps systems in step

The table below shows the difference between working around the limit by hand and closing it, for a stalled purchase deal waiting on a borrower document.

This is the gap SalesOS is built to close. It works with the Follow Up Boss you already have, keeps it in sync with your LOS and inbox, tracks what was promised at each stage, and keeps referral partners updated without anyone making the call, so the follow-up continues after the lead replies in your team's own voice. If that sounds like the layer your stack is missing, you can see how AI Cofounder works.

Common pitfalls when automating Follow Up Boss

Most Follow Up Boss automation problems come from trying to automate too much of the wrong thing before the basics are clean. The mistakes below are the ones that quietly cost deals.

FAQ

Can Follow Up Boss send automated text messages?

Follow Up Boss can send texts from Action Plans, but it deliberately limits fully automated texting because carrier rules and A2P 10DLC registration throttle traffic that looks like bulk automation. Most teams schedule the first outbound touches and route every reply to a person, using automation to remind and escalate rather than to send.

What are the main limits of Follow Up Boss automation?

Restricted text automation, custom fields that hold data but trigger no action, and no built-in sync with outside systems such as your loan origination system and shared inbox are the main limits. Its Action Plans and lead routing work well; the gaps are texting judgment, stale fields, and cross-system handoffs.

How do I sync Follow Up Boss with my other tools?

Syncing Follow Up Boss with your other tools runs through its API, which lets other software read and write your Follow Up Boss data, but the API doesn't design the workflow for you. Decide what syncs, in which direction, and make sure any integration matches existing contacts on email or phone so it updates records instead of creating duplicates.

Is Follow Up Boss automation compliant with texting rules?

No tool, including Follow Up Boss, can make your texting compliant on its own; your compliance team decides what your numbers are allowed to send and how. Any automation you add should follow the rules your team sets, and A2P 10DLC registration is the baseline every business texting number now goes through.

If your Follow Up Boss is doing the structured work but the deals still leak at the edges, that gap is worth an hour to map. Book a demo and we'll walk your actual process, find where it leaks, and show you what a sync layer on top of Follow Up Boss would do about it.