Anu Agency
Playbook
Work with Anu
03.06 Write a 10-day follow-up cadence and let the CRM remind you

03.06

Write a 10-day follow-up cadence and let the CRM remind you

Turn 'follow up more' into a written schedule of calls, texts, emails and tasks that respects quiet hours and stops when the lead replies or opts out.

45 minMatches official docsChecked 2026-10-20

Video walkthrough

Coming soonThe cadence: who does what, on which day, and when it stops
It will cover
  1. Why most leads get one or two attempts and then silence
  2. The 10-day cadence: calls by you, reminders by the CRM
  3. Planner demo: a Friday 8:40pm lead and what quiet hours do to it
  4. HighLevel: one workflow with Add Task steps, Wait steps and Stop on Response
  5. Follow Up Boss: an action plan of task steps that pauses when the lead responds
This chapter is complete without it. Every step is written out on this page.

What you're building

A written cadence (the touches, their timing and who does each) plus the CRM setup that creates reminders for every human touch and sends only the automated touches that are allowed. Calls and personal texts stay human. The CRM's job is to make sure you never forget one.

Why it matters

Without a written cadence, follow-up depends on memory and mood. Leads that do not answer the first call simply stop hearing from you. A cadence makes 'how many attempts' a decision you make once, then measure (chapter 9).

What you need

  • Chapters 1 to 5 done: stages, compliance, routing, Smart Lists and alerts.
  • Your message templates below, edited into your own voice.
  • HighLevel workflow access, or Follow Up Boss admin access to Admin > Action Plans.

Time and cost

Time
45 minutes to build; 20 minutes a day to work
Cost
Per-message SMS and email costs on your CRM plan

Step by step

  1. Plan the cadence in the planner

    Use the planner below. Pick a cadence, set your sending window and allowed days, and try arrival times that hurt: Friday 8:40pm, Saturday noon, Sunday 7am. Watch the 'first call after arrival' number. If it is longer than you can accept, allow more days or add a morning speed check.

    Check: You have a cadence you are willing to run on every new lead, with its touches written down.

  2. HighLevel: build the cadence workflow

    1. Trigger: Pipeline Stage Changed to Attempting Contact in your Buyer & Seller Leads pipeline (the first call moves the lead there).
    2. For each human touch in your cadence add Add Task: Title (for example Day 1 call + text), Assign To the contact owner, Due In the right number of days, a Due Time, and Skip Weekends if you do not work them.
    3. Between tasks add Wait with A set period of time. Add the day 3 email as Send Email at its spot.
    4. At the end add Add Task: Day 10: decide Nurture or close out.
    5. Open Settings: turn on Stop on Response so a reply removes the lead from the automation, keep Allow Re-entry off, and turn on Time Window 9:00 AM to 8:00 PM.
    6. Name it 03 New lead cadence and Publish.

    Check: Move a test contact to Attempting Contact: the Day 1 task appears in Contacts > Tasks with the right due date, and a reply from your test phone removes the contact from the workflow.

  3. Follow Up Boss: build the cadence as an action plan

    1. Name it New lead 10-day cadence.
    2. Tick Automatically pause this action plan when the lead responds. It pauses on an email reply, a text reply, or a logged call longer than 2.5 minutes.
    3. Add steps. Run sets how many days after the previous step; Action is Create task, Send email, Change stage and others. Use Create task for every call and personal text, Send email for the day 3 email, and Change stage to Nurture as an optional final step only after the day 10 decision task.
    4. Tick Share with everyone if your team uses it. Save.
    5. Apply it to new leads on Admin > Lead Flow (Action Plan for each source), or manually from a lead profile under Action Plans with the blue + icon.

    Check: Apply the plan to a test lead: the first task shows on the Tasks page the day it is due, and a text reply from your test phone pauses the plan.

  4. Write and save your message templates

    Save the templates below as text and email templates in your CRM, edited into your voice. The first text to someone who has never texted you includes your business name and opt-out wording. Later texts in an ongoing conversation do not need to repeat it, but never remove the STOP option from automated messages.

    Check: Each template is saved under a name that starts with its cadence day, for example D1 text.

What success looks like

  • Every new lead in Attempting Contact gets the same, written sequence of tasks.
  • No automated touch goes out after a reply or an opt-out, or outside 9am to 8pm.
  • Day 10 always ends with a decision: Nurture, Lost/Trash, or Contacted.

Copyable templates

textDay 1 personal text (after a missed call)
Hi {first name}, {agent name} again with {business name}. Tried you just now about {property or topic}. Is text easier? Reply STOP to opt out.
textDay 3 value email
Subject: {property or neighborhood}: what I'd want to know

Hi {first name},

I haven't caught you by phone, so here is something useful instead: {one specific fact, for example recent sales on that street or how long similar homes took to sell}.

If you'd like, I can send a short list of homes like {property} that are not on the big sites yet, or walk you through what it would sell for today.

What's the best way to reach you?

{agent name}
{business name} | {phone}
{brokerage name and license line as required in your state}

You received this because you asked about {property or topic} on {source}. Unsubscribe: {unsubscribe link}
textDay 4 personal text
Hi {first name}, {agent name} here. Still looking at homes around {area}, or did the timing change? Either answer helps. Reply STOP to opt out.
textDay 10 close-out text
Hi {first name}, I don't want to crowd your phone. I'll stop reaching out about {property or topic}. If you want help later, just reply here. Reply STOP to opt out.
textVoicemail script (20 seconds)
Hi {first name}, it's {agent name} with {business name}, calling about {property or topic} you asked about. I have an answer for you. Call or text me back at {phone}. Again, {agent name}, {phone}.

Try it

Follow-up cadence planner

Times are the lead's local time. Calls and texts outside your sending window move to the next opening. Nothing here sends a message.

Cadence
Federal rule for solicitations: not before 8:00am. Some states are stricter.
Federal rule: not after 9:00pm. Default here is 8:00pm.
Days you allow calls and texts
First call after arrival12 h 20 min
Attempts in first 24h4
Attempts total11
Moved by quiet hours10
Standard 10-day new-lead cadence
TouchWhoWhenStatus
Instant intro text with opt-out lineCRMSat 9:00amMoved to next allowed time
Call 1 (alert fires, agent dials)YouSat 9:00amMoved to next allowed time
Call 2 if no answerYouSat 9:00amMoved to next allowed time
Intro email with how to reach youCRMSat 9:00amMoved to next allowed time
Day 1 callYouSun 9:00amMoved to next allowed time
Day 1 personal textYouSun 9:00amMoved to next allowed time
Day 2 callYouMon (wk 2) 9:00amMoved to next allowed time
Day 3 value emailCRMMon (wk 2) 8:40pmOn time
Day 4 callYouWed (wk 2) 9:00amMoved to next allowed time
Day 4 personal textYouWed (wk 2) 9:00amMoved to next allowed time
Day 7 callYouSat (wk 2) 9:00amMoved to next allowed time
Day 10 task: decide nurture or close outCRMMon (wk 3) 8:40pmOn time

The instant text and alert fire immediately only when the lead arrives inside your window. A Friday 8:40pm lead gets its first call Saturday morning if Saturday is allowed, Monday if not. That gap is the real cost of a narrow window, and it is why after-hours leads need a morning-first Smart List.

Starter cadences are assumptions. The rules are in plain sight: calls and texts move to the next allowed time, opted-out leads get no texts, and a reply stops every automated touch.

How to test it

  1. In the planner, set a Friday 8:40pm arrival with weekends off. Note when the first call lands. Decide whether that is acceptable.
  2. Run the cadence on a test lead for 2 days in your CRM. Confirm the Day 1 tasks appear and the day 3 email is scheduled.
  3. Reply from the test phone. Confirm the workflow stops (HighLevel) or the action plan pauses (Follow Up Boss).

Troubleshooting

The day 3 email still went out after the lead replied by text.

HighLevel: turn on Stop on Response in workflow Settings. Follow Up Boss: tick 'Automatically pause this action plan when the lead responds'. Calls logged manually on desktop do not pause a Follow Up Boss plan; pause it by hand (Action plans tile > Running > Pause).

Follow Up Boss action plan has no text step.

Action plans send emails and create tasks; automated texts other than the Lead Flow initial text are not part of them. Use a task that says 'Send D1 text' and send it personally from the template.

Too many overdue tasks pile up.

Your cadence has more human touches than you have time for. Use the light cadence for low-intent sources, or clear Overdue Tasks and restart with fewer steps.

Opt-outs went up after adding texts.

Check that every first text names you and your business, uses no links in the first message, and is sent only to leads with a consent source. Reduce text touches before reducing calls.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsCadence logic, precisely

The planner works on the lead's local clock in minutes. Each touch is planned at arrival plus offset. Calls and texts outside [window start, window end) or on a disallowed day move to the next opening. A touch never lands before the one before it. Opted-out leads get no texts. An automated touch scheduled at or after a reply is stopped; human touches remain. The logic is a small pure function with unit tests, so you can check it does what this paragraph says.

HighLevel Wait also supports waiting for 'The contact to reply' with a timeout, waiting for a specific date, or a time window. Combine 'The contact to reply' after a Send SMS with a timeout to branch: replied leads go to a task for the owner; non-replies continue the cadence.

Sources

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