Anu Agency
Playbook
Work with Anu
04.08 Measure conversations and appointments, then decide whether to scale

04.08

Measure conversations and appointments, then decide whether to scale

Count replies, real conversations, appointments and opt-outs from tags in your CRM, compare message versions, and use a written rule to scale, repeat or stop.

30 minMatches official docsChecked 2026-10-20

Video walkthrough

Coming soonReading your pilot: what worked and what to do next
It will cover
  1. Replies are not the goal: conversations and appointments are
  2. Counting from tags with four Smart Lists
  3. Version A versus B: is the difference real at this size?
  4. The scale, repeat or stop rule
  5. Making it a monthly habit, not a one-time blast
This chapter is complete without it. Every step is written out on this page.

What you're building

A results view built from the pilot tags, a filled scorecard with your own rates, and a written decision: scale to the next 200, repeat 100 with one change, or stop and fix the data or message.

Why it matters

A reactivation campaign can look busy (lots of replies) and produce nothing (no appointments). Measuring each step separately shows where it breaks: a low reply rate points to the message or list; replies without conversations point to your follow-up; conversations without appointments point to the ask.

What you need

  • A finished or 14-day-old pilot (chapter 7)
  • Consistent tags: react-replied, react-conversation, react-appt, react-optout
  • The workbook Results tab

Time and cost

Time
30 minutes per review
Cost
$0

Step by step

  1. Build four results Smart Lists from tags

    Create Pilot | Replied, Pilot | Conversation, Pilot | Appointment and Pilot | Opted out, each with Tags Is reactivation-pilot AND the outcome tag. In Follow Up Boss use Filters > Tags Include all of reactivation-pilot and the outcome tag, then + New List.

    Cross-check appointments against the calendar: HighLevel has a Last Appointment At date filter, and Follow Up Boss has an Appointment Set stage and logs appointments on the profile. A tag without a calendar entry is not an appointment.

    Check: The four list counts equal the Y counts in your Pilot tracker.

  2. Fill the scorecard and Results tab

    Copy the counts into the workbook Results tab (it calculates rates using delivered messages as the base) and into the weekly scorecard below. Add appointments held: a booked appointment that did not happen is a follow-up problem, not a success.

    Check: Every rate on the scorecard has a number and a date.

  3. Compare version A and B honestly

    The Results tab shows reply rate and appointments per version. With 50 contacts per version, small differences are noise: 6 replies versus 8 replies is not evidence that B is better. Treat a version as the winner only when the gap is large (for example twice the replies) and the opt-outs are not higher. Otherwise keep the version you prefer and test a bigger change next time.

    Check: You wrote down which version you keep and why, in one sentence.

  4. Apply the scale, repeat or stop rule

    ResultDecision
    A stop rule triggeredSTOP and fix: clean the source of the opt-outs or complaints, then repeat 100
    No stop rule, at least one appointment held, replies answered within an hourSCALE: next 200 from the rank, same schedule, 20 to 40 a day
    No stop rule, replies but no appointmentsREPEAT 100: keep the list, change the ask (offer a 15-minute call or a home visit for the update)
    No stop rule, very few repliesREPEAT 100: change the message or the offer; check delivery and consent data

    These thresholds are a decision framework, not industry benchmarks. Your own pilot is the benchmark you compare future batches against.

    Check: The scorecard has one decision circled and a reason.

  5. Move the people who engaged into your pipeline

    Everyone tagged react-conversation gets a next step: a pipeline stage (Part 05 sets up a seller pipeline), a task, or a calendar follow-up date. Everyone else from the pilot goes back to your normal nurture after 30 days; remove the reactivation-pilot tag then so they can enter a later batch.

    Check: No contact with a conversation is left without a task or stage.

What success looks like

  • A filled scorecard with your own reply, conversation, appointment and opt-out rates
  • Appointments verified against the calendar
  • A written scale, repeat or stop decision
  • Every engaged contact has a next step

Copyable templates

textWeekly reactivation scorecard
REACTIVATION SCORECARD, week ending ____

                         Version A   Version B   Total
Contacts messaged          ___         ___        ___
Delivered                  ___         ___        ___
Human replies              ___         ___        ___
Conversations              ___         ___        ___
Appointments set           ___         ___        ___
Appointments held          ___         ___        ___
Opt-outs                   ___         ___        ___
Complaints                 ___         ___        ___

Reply rate          = replies / delivered
Conversation rate   = conversations / delivered
Appointment rate    = appointments set / delivered
Show rate           = appointments held / appointments set
Opt-out rate        = opt-outs / delivered
Median first-response time to replies: ___ minutes

Decision (circle one):  SCALE next 200  |  REPEAT 100 with changes  |  STOP and fix
Reason (one sentence): _____________________________________________

Try it

Pilot scorecard

Type your pilot counts. Rates use delivered messages as the base.

First-touch messages, one per contact
Sent minus bounces and failed texts
Any human reply, including 'not now'
Two or more back-and-forth exchanges
A date and time on the calendar
STOP replies plus email unsubscribes
Spam reports or angry replies
Your own limit. 2% is a starting assumption, not a published standard.
Reply rate0.0%
Conversation rate0.0%
Appointment rate0.0%
Opt-out rate0.0%

No stop rule triggered. Keep the pilot running as planned.

Enter your pilot counts to see the rates and whether a stop rule fires.

How to test it

  1. Pick 5 contacts tagged react-appt. Each must have a calendar appointment with a date.
  2. Recalculate the reply rate by hand from the list counts. It must match the Results tab.
  3. Check that every opted-out pilot contact still shows DND or an opt-out flag a week later.

Troubleshooting

Smart List counts do not match the tracker.

A tag was missed or misspelled. Filter Tags Contains react to find variants and fix them.

Lots of replies, zero appointments.

Read 10 conversations. If you delivered the update but never asked for a next step, add a clear ask: "Want to walk through it on a 15-minute call Thursday?"

Appointments booked but not held.

Send a reminder the day before and confirm by reply. Track show rate separately.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsPulling counts by API

Follow Up Boss GET /v1/people accepts tags and smartListId filters, so a small script can read the four result lists each morning into a sheet. Page with offset (max limit 100). In HighLevel, Bulk Actions > Show Stats gives per-send delivery stats for bulk SMS and email jobs.

Sources

Every product step matches the current official documentation listed under Sources. Last checked 2026-10-20.