follow-up-bosscrmsales-reporting

Follow Up Boss Speed-to-Lead Report: Why the Number Lies

·Terrell Gentry·9 min read
Follow Up Boss Speed-to-Lead Report: Why the Number Lies

The Follow Up Boss speed to lead report only counts the assigned agent's personal 1:1 outreach. It does not count the automated first text your action plan sends, and it does not count another teammate who answers the lead first. So the number on your dashboard can both understate the work being done and mis-credit who actually did it, which makes it a shaky thing to coach from.

If you run a team on Follow Up Boss and you use that report to decide who is fast, who is slow, and who needs a talking-to, you are reading a partial record and treating it as the whole story. This is the problem with coaching off a metric that measures one channel of effort and quietly drops the rest.

What the speed to lead report actually measures

The speed to lead report measures the gap between when a lead comes in and when the assigned agent personally reaches out by call, text, or email. Per Follow Up Boss's own help documentation, the speed metrics are based on the assigned agent. That is the whole definition, and it is narrower than it sounds.

Three things fall outside that definition, and all three are common on a real team:

  • The automated first text or email your action plan fires. Follow Up Boss's docs state automated follow-up through action plans is not counted in the speed metrics.
  • A teammate who is not the assigned agent. If your ISA or another loan officer answers first, their communication will not be counted in the average speed numbers.
  • Marketing and batch sends. Marketing emails and texts, action plan emails, and batch emails are left out of the unactioned and speed calculations.

Put those together and the report is really answering one question: how fast did the one person whose name is on the lead reach out, by their own hand. That is a legitimate question. It is just not the question most team leads think they are asking, which is "how fast did my team respond to this lead."

Where the number lies

The number lies in both directions, and which way depends on how your team is actually set up. The report can make a fast team look slow, or make a quiet agent look busier than they are.

Here is the understatement case. Say a lead comes in at 9:02 a.m. An action plan fires an automated text at 9:03. Your ISA sees the reply and calls at 9:11. The assigned agent, a producing loan officer buried in a closing, doesn't personally touch the lead until 2:40 p.m. The lead got a response in one minute and a human call in nine. The speed to lead report, measuring only the assigned agent's own outreach, will show about five and a half hours. On that dashboard your team looks negligent on a lead it actually worked inside ten minutes.

Now the mis-credit case. A lead sits untouched. Nobody calls, nobody texts by hand. But the action plan is running, sending its scheduled touches. The Follow Up Boss dashboard counts a lead as unactioned only when there is no outbound call, email, or text from the assigned agent, and action plan emails don't count. So the lead shows as unactioned, which is honest. The trap is the reverse: a lead that got real human attention from someone other than the assigned agent can still read as thin, and an agent who leans entirely on automation while doing little by hand can look like they have nothing to show, even when the automation is carrying the deal. You cannot tell the two apart from the report.

The same exclusion runs through the agent activity report. It documents speed by the assigned agent and leaves out automated follow-up and non-assigned teammates. The deals leaderboard, available on the Pro and Platform plans, ranks people by the total value of deals marked as closed in the window, which is a different measure again and tells you nothing about who answered first.

How to read the report honestly

Read the speed to lead report as one agent's personal first-touch record, nothing more, and pair it with what you know about your routing. The number is useful when you treat it as a measure of individual hand-raising, not team response.

A few rules that keep you honest:

  1. Match the metric to how leads are routed. If leads auto-assign to a producing loan officer who is often in a closing, a slow personal speed number is expected and not a performance problem. If you expect the assigned person to be the first responder, then the number means what you think it means.
  2. Know what your action plans are doing before you judge speed. If an action plan sends an instant first text on new leads, your real response time is near zero and the report will never show it. Coaching an agent for being "slow" when automation already answered in a minute burns trust.
  3. Watch the "Missing Initial response" flag with suspicion. If that flag is on but your action plan is firing, the lead was contacted. The flag is telling you no human touched it by hand yet, not that nothing happened. Those are different problems with different fixes.
  4. Remember that a reply does not pause an action plan on its own. In Follow Up Boss, someone has to manually pause or remove the contact after a lead replies. So a lead can be mid-conversation with your ISA while the plan keeps sending scheduled touches, which muddies any read of who is driving the deal.

The honest version of the coaching conversation stops being "your speed to lead number is bad." It becomes "walk me through what happened on these five leads," because the report cannot tell you that on its own.

Building a true first-touch view across the whole team

A true first-touch record counts whoever reached the lead first, by any channel, automated or human, and ties it to the deal all the way through. That is the view the native report was never built to give you, because it only ever looks at one person's manual outreach.

To build it, you have to pull the signals Follow Up Boss excludes and stitch them back together: the action plan's automated first touch, the ISA's call, the processor's text during a handoff, and the assigned agent's own outreach, all on one timeline per lead. Then "how fast did we respond" has a real answer, and "who worked this deal" shows every hand that touched it instead of just the name on the file.

This is the record SalesOS keeps. It works alongside the Follow Up Boss account you already have, keeps the real first-touch across every rep and every automation in sync, and gives you a top-level view across reps so you can see where each deal stands and how long it has sat there, without exporting a report and pasting it into a chat window. You can see how AI Cofounder works if you want the fuller picture of what it does inside the tools you already pay for. If you want to read the native reporting as part of a broader read on where deals leak, our piece on mortgage pipeline visibility across four systems and the one on why follow-up still leaks after you switch a CRM cover the same leak from other angles.

The reason any of this matters is the stakes on speed. The 5-minute rule everyone cites comes from the 2007 MIT and InsideSales lead response study by James Oldroyd, which measured over 15,000 leads and found the odds of making contact were 100 times higher and the odds of qualifying 21 times higher at five minutes versus thirty (rework.com). If you are chasing that window, you need a report that actually shows whether you hit it. The native speed to lead report, by design, cannot.

FAQ

Does the Follow Up Boss speed to lead report count my action plan's first text?

The speed to lead report does not count automated follow-up sent by an action plan. Per Follow Up Boss's own documentation, automated communication is excluded from the speed metrics, so if your real first response was an instant automated text, the report will show the later manual touch instead and overstate your response time.

If my ISA answers a lead first, does it show up in the speed numbers?

An ISA or any teammate who is not the assigned agent will not be counted in the average speed metrics. Follow Up Boss bases those metrics on the assigned agent's own outreach, so a lead your ISA calls in two minutes can still read as slow if the assigned agent doesn't personally touch it until hours later.

What does the "Missing Initial response" flag really mean?

The "Missing Initial response" flag means there is no outbound call, email, or text from the assigned agent yet, not that nothing has happened. If your action plan is firing automated touches, the lead has been contacted even while that flag is on, so treat it as "no human has worked this by hand," not as "this lead is cold."

Does getting a reply pause the action plan automatically?

A reply does not pause an action plan on its own in Follow Up Boss. Someone has to manually pause or remove the contact, which means a plan can keep sending scheduled touches while your team is already mid-conversation with the lead, so read any speed number against what your plans are still doing in the background.

Which Follow Up Boss reports have these exclusions?

The exclusions run through the speed to lead report, the agent activity report, and the unactioned count on the dashboard, all of which key off the assigned agent's manual outreach and leave out automation and other teammates. The deals leaderboard, on the Pro and Platform plans, is a separate measure that ranks people by the value of deals marked closed, so it answers a different question entirely.

Reading these reports honestly gets you only so far, because the native tool was never built to credit the automation or the teammates doing the work. If you want one true record of who touched every lead first, across your reps and your automation, kept in sync with the Follow Up Boss account you already run, Book a Demo: SalesOS follows up with every lead in your own voice, keeps your CRM in sync, and shows you where every deal stands, seen working on a pipeline like yours.

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