Anu Agency
Playbook
Work with Anu
03.09 Measure follow-up: speed to lead, attempts per lead and contact rate

03.09

Measure follow-up: speed to lead, attempts per lead and contact rate

Pull the three follow-up numbers every week from Follow Up Boss reports or a 20-lead HighLevel sample, and use them to change one thing at a time.

35 minNeeds verificationChecked 2026-10-20

Video walkthrough

Coming soonThree numbers that tell you if follow-up is working
It will cover
  1. Speed to lead, attempts per lead, contact rate: exact definitions
  2. Follow Up Boss: Reporting > Lead Sources and Agent Activity, and what they leave out
  3. HighLevel: the 20-lead sample, the sla-missed tag, and the Lead Source Report
  4. Reading the numbers together: fast but few attempts, many attempts but slow
  5. One change per month, then measure again
This chapter is complete without it. Every step is written out on this page.

What you're building

A weekly follow-up scorecard with three numbers, per source and per agent, pulled the same way every time:

MetricFormulaCountsDoes not count
Speed to leadMedian of (first personal call or text time minus lead created time)Calls and 1:1 texts by a personAutomated instant texts, emails
Attempts per leadPersonal calls + texts + emails to new leads in their first 10 days ÷ new leadsEach dial, each personal messageAutomated messages
Contact rateLeads with a two-way conversation ÷ new leadsReply by text or email, answered callAuto-replies, opt-out replies
Opt-out rate (guardrail)Text opt-outs from new leads ÷ new leads textedSTOP keywords and plain-English requestsHard bounces

Why it matters

These three numbers explain each other. Fast with few attempts means you call once and give up. Many attempts with a low contact rate means wrong numbers or the wrong channel. A rising opt-out rate means your texts are too frequent or too generic. Watching them together tells you which chapter to revisit.

What you need

  • Two weeks of activity under the system from chapters 1 to 8, logged in the CRM.
  • Follow Up Boss: access to Reporting (admins see the team). HighLevel: access to Conversations, Opportunities and Dashboards.
  • The scorecard CSV below in a spreadsheet.

Time and cost

Time
15 minutes a week (Follow Up Boss); 30 to 40 minutes a week (HighLevel sample)
Cost
$0

HighLevel Call Reporting is listed as an Agency Pro plan feature; if your account does not have it, count calls from the sample instead.

Step by step

  1. Follow Up Boss: pull speed and attempts from Reporting > Lead Sources

    Set Lead Type to web, the time frame to last week, and choose these report options:

    • How quickly we follow up on leads per lead source: Avg. Speed to Action, Avg. Speed to First Call, Avg. Speed to First Text Message.
    • How many times we try to contact each lead per lead source: Avg. Contact Attempts, Avg. Call Attempts, Avg. Text Message Attempts.
    • What lead source has the most lead responses: % of Leads Responding. Use it as your contact rate.
    • How many leads have we not acted on: Leads Not Acted On. This should be zero.

    Repeat in Reporting > Agent activity for the per-agent view. Export with Export Report if you keep the scorecard in a sheet.

    Check: Your scorecard row for last week has speed, attempts, % responding and leads not acted on for each source.

  2. HighLevel: run the 20-lead sample for speed and attempts

    HighLevel's help center does not describe a single per-lead speed-to-lead report, so sample it. Filter opportunities created last week, take the first 20 (or all of them if fewer), and for each open the contact's conversation and activity:

    1. Write down the created time and the time of the first outbound call or personal text (skip the automated instant text).
    2. Count personal calls, texts and emails in the first 10 days.
    3. Mark Y if there was a two-way conversation.

    The scorecard sheet computes median minutes, attempts per lead and contact rate. Add the number of contacts tagged sla-missed by the chapter 5 escalation branch: that is your count of leads nobody texted within 5 minutes.

    Check: The sample tab of the scorecard has 20 rows and the three formulas show values.

  3. HighLevel: pull contact rate by stage and source from the dashboard

    Add the Lead Source Report widget (under the General category). It shows, per source, total leads (opportunities) and how many are open, won, lost or abandoned, with values. For contact rate, open the pipeline and count opportunities from last week's cohort that reached Contacted or later. SMS widgets (filter by Direction and Sent by) and Reporting > Call Reporting add volume context.

    Check: You can name your best and worst source by contact rate for last week.

  4. Change one thing, then measure for four weeks

    Pick the worst number and the chapter that fixes it: slow speed (chapter 5), few attempts (chapter 6), low contact with many attempts (check phone validity, try calling at different hours, review the first text), rising opt-outs (chapter 2 and fewer text touches). Change one thing, write the date in the scorecard notes, and leave it alone for four weekly readings.

    Check: The scorecard has a dated note for the one change you made and four rows after it.

What success looks like

  • A scorecard row every week, per source, pulled the same way.
  • Leads Not Acted On (Follow Up Boss) or sla-missed count (HighLevel) trending to zero.
  • Every change to the system has a date and four weeks of numbers after it.

Copyable templates

CSVFollow-up scorecard CSVWeekly rows per source plus a 20-lead sample section with the formulas written out. Import into Google Sheets or Excel.
textSpreadsheet formulas for the 20-lead sample

Assumes created time in column B, first personal touch in column C, attempts in D, two-way conversation Y/N in E, rows 2 to 21.

Minutes to first touch (F2, fill down):   =IF(C2="", "", (C2-B2)*1440)
Median speed to lead (minutes):            =MEDIAN(F2:F21)
Leads never touched:                        =COUNTBLANK(C2:C21)
Attempts per lead:                          =AVERAGE(D2:D21)
Contact rate:                               =COUNTIF(E2:E21,"Y")/COUNTA(A2:A21)

Try it

Reading the three numbers together (fictional week for Coastal Key Realty).
PatternExampleLikely causeGo to
Fast, few attemptsSpeed 4 min, 1.6 attempts, contact 31%One call and doneChapter 6 cadence
Slow, many attemptsSpeed 52 min, 7.5 attempts, contact 34%Alerts missed; effort comes lateChapter 5 alerts
Many attempts, low contactSpeed 6 min, 8 attempts, contact 18%Bad numbers or wrong channelSource quality (Part 06), email and call timing
Contact fine, opt-outs risingOpt-outs 4% of texted leadsTexts too frequent or genericChapter 2, fewer text touches

How to test it

  1. Pick 3 leads from last week. Compute their minutes to first touch by hand from the activity history.
  2. Compare with the report (Follow Up Boss) or your sample row (HighLevel). They must match within a minute or two.
  3. If they do not, find out why (automated text counted, teammate called, wrong time zone) and write the rule in the scorecard notes.

Troubleshooting

Follow Up Boss shows great speed but leads say nobody called.

Check Lead Type (web vs manual) and whether calls were made outside Follow Up Boss. Calls from a personal cell that are not logged do not exist for reporting.

Speed numbers look worse after adding the instant text.

They should not change: automated texts are excluded. If they did, check whether agents now wait because 'the text already went out'.

Contact rate is impossible to compute in HighLevel because stages are not updated.

Fix the stage habit first (chapter 1 ten-lead audit). Until then, use the 20-lead sample's Y/N column.

Deleted contacts made last month's report change.

Deleting contacts removes their statistics from Follow Up Boss reports. Move junk to the Trash stage instead of deleting.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsAutomating the HighLevel speed metric

For an exact HighLevel speed metric, have the routing workflow write the creation timestamp to a custom date-time field and a second workflow (trigger on the first outbound call or the 'A user to reply' resolution) write the first-touch time, then compute the difference in a custom metric or export. Test that the date fields actually populate in your account before relying on them; some workflow date values have been known to write blank in certain configurations.

Follow Up Boss exposes person-level fields such as Time to First Call, Calls Made and Texts Sent as filters and columns, so you can export a cohort (People > filter Created last week > Export with All Columns) and compute medians yourself.

Sources

Written from the best available information. One or more steps could not be confirmed; see the notes in the chapter. Last checked 2026-10-20.