Anu Agency
Playbook
Work with Anu
06.10 Assign every lead instantly and call within your speed target

06.10

Assign every lead instantly and call within your speed target

Route each new Meta lead to a named agent, alert them immediately, and run a written first-call script and 7-day attempt cadence that honors opt-outs.

40 minNeeds verificationChecked 2026-10-20

Video walkthrough

Coming soonSpeed to lead: the part of the system ads cannot fix
It will cover
  1. Why the pilot is really a test of your follow-up
  2. HighLevel: the Facebook Lead Form Submitted workflow
  3. Follow Up Boss: routing by the form-name tag
  4. The first-call script and the 7-day attempt cadence
  5. Opt-outs, wrong numbers and staying compliant
This chapter is complete without it. Every step is written out on this page.

What you're building

An automation that assigns every new lead from your form to a named agent and alerts them immediately, plus a written first-call script and a 7-day attempt cadence your team follows for every lead.

Why it matters

A Higher intent lead expects a call; your ending screen promised one. If the call comes the next afternoon, the person has moved on or talked to someone else. Your pilot measures the ads and the follow-up together, so a slow follow-up makes good ads look bad. This chapter makes the follow-up consistent so the data in chapter 11 is about the ads.

What you need

  • The working CRM connection and test lead from chapter 9
  • The responder, backup and speed target from your brief
  • HighLevel: permission to create workflows. Follow Up Boss: admin access to Lead Flow
  • For texting from HighLevel: an A2P 10DLC registered number

Time and cost

Time
30 to 60 minutes
Cost
$0 beyond existing CRM and phone costs

Text and call usage charges depend on your CRM plan.

Step by step

  1. HighLevel: create the lead workflow with the Facebook trigger

    1. Go to Automation > Workflows and create a new workflow named META SELLER_HI_v1 new lead.
    2. Click + Add New Trigger. Under Events, select Facebook Lead Form Submitted.
    3. Add filter Page Is = your Page, then Form Is = SELLER_HI_v1. Without filters the workflow fires for every form on every connected Page.
    4. Click Save Trigger.

    Check: The trigger shows both the Page and the Form filters.

  2. HighLevel: add assignment, opportunity and alert actions

    1. Add Assign to User: your primary responder.
    2. Add Create/Update Opportunity in your seller pipeline at the first stage, named with the lead's name and the form.
    3. Add Internal Notification to the assigned user (SMS or app notification) with the lead's name, phone, address and timeline answers.
    4. Add a task for the first call due now, and a wait step that alerts the backup if the task is still open after your speed target.

    These four action types are listed in HighLevel's trigger article as recommended actions. The exact wait-and-check pattern depends on how your team logs calls; the simplest version is a wait of your speed target followed by an internal notification to the backup.

    Check: The workflow shows the trigger and the assign, opportunity, notification and backup-alert actions.

  3. HighLevel: test the workflow with a test lead

    Use Test Workflow, then send a fresh test lead from the Lead Ads Testing Tool (delete the previous one first). Publishing the HighLevel workflow turns on automation for real leads; it does not publish or fund your ads. Turn it on only when you are ready for leads to be routed.

    Check: A test lead arrives, is assigned to the right person, creates an opportunity, and the responder's phone gets the alert.

  4. Follow Up Boss: route by the form-name tag

    Follow Up Boss tags each Facebook lead with the Page name and the form name. In Admin > Lead Flow, route leads carrying the SELLER_HI_v1 tag to your primary responder and attach an action plan that creates the first-call task and the cadence below. Turn on new lead notifications for that agent.

    Check: A test lead is assigned to the right agent and shows the action plan running.

  5. Adopt the first-call script and 7-day cadence

    Print the script below for whoever calls. Every lead gets the same script and the same number of attempts, whatever their name, accent or area. Log every attempt in the CRM so chapter 11 can count conversations, bookings and speed honestly.

    Check: The responder can recite the opening line and knows the opt-out and wrong-number handling.

What success looks like

  • Every test lead is assigned and alerted within seconds
  • A backup is alerted if the first call is late
  • One script and one cadence for every lead
  • Opt-outs and wrong numbers are removed immediately

Copyable templates

textFirst-call script and 7-day attempt cadence

Cadence numbers are Anu's starting rule, not a benchmark. Adjust to your team.

FIRST CALL SCRIPT (seller value review lead)

Opening (within your speed target):
"Hi [First name], this is [Your name] with [Brokerage]. You just asked for a value review on
[property address] through Facebook. Is now an OK moment for two minutes?"

If yes:
1. "What has you thinking about the value right now?"            (motivation, listen)
2. "If the numbers made sense, when would you ideally move?"       (timeline)
3. "Is anyone else on the title who'd want to see the review?"     (decision makers)
4. "I'll prepare a written price range from recent sales near you. The best way to go through it
    is a 20-minute meeting, at the home or by video. Does [day] at [time] or [day] at [time] work?"

If not now:
"No problem. When is a better time today or tomorrow?"  -> book a callback task in the CRM.

If they did not request it / wrong number:
"Sorry for the trouble, I'll remove this number."       -> mark DNC, remove from all follow-up.

If they ask to stop:
"Understood, I won't contact you again."                -> opt out in the CRM immediately.

VOICEMAIL (keep under 20 seconds):
"Hi [First name], [Your name] with [Brokerage] returning your value review request for
[street name]. I'll text you from this number too. Talk soon."

TEXT AFTER A MISSED CALL (only if your consent text covered texting and your number is A2P registered):
"Hi [First name], it's [Your name] with [Brokerage]. Just tried you about the value review for
[street name]. When's a good time for a 2-minute call? Reply STOP to opt out."

FOLLOW-UP CADENCE (attempts until a conversation or opt-out):
Day 0: call within speed target, voicemail, text; second call 2 hours later
Day 1: morning call + text
Day 2: afternoon call
Day 4: call + email with what they will receive
Day 7: call + final text: "Should I close out your request for now?"
After day 7: move to long-term nurture, monthly market update, opt-out honored

How to test it

Do a timed drill: send a test lead at a random moment during business hours without warning the responder. Measure minutes from submission to the first call attempt. Repeat once after hours to confirm the after-hours rule works. Delete the test contacts afterward.

Troubleshooting

The HighLevel workflow does not fire.

Check that the Page and Form filters match the form you tested, that the workflow is published, and that the Facebook integration still shows connected. If Pages or forms do not appear in the filter dropdown, HighLevel says the integration is incomplete.

Leads arrive but nobody sees them for hours.

The alert is going somewhere nobody watches. Send the internal notification as an SMS to the responder's phone and add the backup alert.

Callers skip the qualifying questions.

Put the three questions on the opportunity or person record as required fields the caller fills before moving the stage.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsWhat could not be verified

Speed measurement: compare the lead's created timestamp in the CRM with the first outbound call activity. Both platforms record these; export them for chapter 11 rather than estimating.

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.