A lead follow-up sequence that still sounds human

A person who asked for a callback is not the same as someone who downloaded a guide. A former client is not the same as a cold prospect. Yet many follow-up systems send all of them through the same sequence.

That is why the messages start sounding automated.

The problem is not always the wording. It is usually the pipeline underneath it.

Most broker pipelines are built for loan delivery.

They begin at New Lead, then move through servicing, document collection, submission, approval and settlement. That structure becomes useful once a person is genuinely in the broker process.

It does not explain where the person came from, what they asked for, how warm the relationship is, or what permission the brokerage has to contact them.

Those questions belong in acquisition pipelines that sit above the delivery pipeline.

Word of mouth is often the first channel a brokerage builds. It carries trust and can produce strong introductions. The risk begins when it becomes the only source the business can see or influence.

A brokerage can add one or two deliberate acquisition channels without treating every contact like an application.

Alex Hormozi’s Core Four framework groups lead generation into four broad methods: warm outreach, one-to-one contact with people who already know you; posting free content, one-to-many communication with an audience you are building; cold outreach, one-to-one contact with people who do not yet know you; and paid ads, one-to-many reach bought through advertising.

This is a useful planning framework, not proof that every channel will suit every brokerage. Channel choice still depends on audience, offer, permissions, capability and economics.

For this workflow, the four methods map to four acquisition pipelines.

The name of the pipeline matters less than the boundary. Each contact should enter a sequence that matches what actually happened.

Human follow-up has memory, restraint and a reason.

Before writing any messages, define six things for every stage.

A stage is not done because a timer expired. It is done because the person replied, booked, opted out, was assessed as unsuitable for this path, or reached the end of an approved attempt sequence.

That distinction stops a workflow moving people forward without evidence.

Paid-ad leads usually expect a response, because they completed a form or took another stated action. They may still have low context, and they may have enquired with more than one business.

The first job is to connect the advertisement they remember with the person now contacting them.

1. New Lead

• Entry trigger — The approved advertising form or landing page is submitted.
• Stage job — Confirm the enquiry arrived and identify the broker.
• Automation allowed — Create the contact and opportunity, record source and campaign, send the approved acknowledgement, assign an owner and create a response task.
• Human handover — As soon as the person asks a specific question, describes their situation or requests a call.
• Exit condition — A first reply, a successful call, a booking, or an approved follow-up timeout.

2. Auto - Follow Up

• Entry trigger — The acknowledgement was delivered, but there is no reply and no connected call.
• Stage job — Make it easy to respond without creating pressure.
• Automation allowed — A small, approved sequence with reply, booking and opt-out stop conditions.
• Human handover — Any substantive reply.
• Exit condition — A reply, a booked appointment, an opt-out, or the final close-out message.

The three messages below are illustrative, not a universal cadence.

Choose timing that reflects the person’s stated expectation, your approved consent process and your team’s capacity. Do not publish an optimal number of messages without your own evidence.

3. In-Conversation

• Entry trigger — The person replies, or a call connects.
• Stage job — Understand the question and agree the next human action.
• Automation allowed — Notify the owner, summarise the thread for review, offer approved calendar times and record a task.
• Human handover — This stage is human-led.
• Exit condition — Booked, not qualified for this path, referred elsewhere, nurture agreed, or a no-response follow-up agreed.

AI may organise the thread. It should not decide what credit product the person needs, or conduct a full discovery conversation without the broker.

4. No Response

• Entry trigger — The approved follow-up sequence ends without a reply.
• Stage job — Stop active pursuit and preserve a truthful record.
• Automation allowed — Close the task, mark the reason and suppress the sequence.
• Human handover — Only where the broker has a real reason for a personal attempt.
• Exit condition — Archived, later re-engagement, or a documented nurture permission.

No Response should be a state, not an invitation to keep sending.

5. Not Qualified

• Entry trigger — A person is not suitable for this acquisition path, or is not ready to proceed.
• Stage job — Record why, and agree what happens next.
• Automation allowed — Apply a reason, create an approved future task, or stop contact.
• Human handover — The assessment and the explanation should be reviewed or delivered by an authorised person.
• Exit condition — Nurture with permission, referral, future review, or closed.

Not Qualified should never be a silent dumping ground. Use clear reason fields such as timing, scope, geography, service fit or contact error. Do not let AI infer a credit outcome from a casual conversation.

6. Booked

• Entry trigger — An appointment is confirmed.
• Stage job — Prepare the broker and the client for the conversation.
• Automation allowed — Confirmation, reminders, a calendar record and an approved pre-meeting checklist.
• Human handover — The broker owns the relationship from here.
• Exit condition — Appointment held, rescheduled, cancelled, or returned to follow-up.

Once the meeting establishes a genuine finance need, create or move the opportunity into the main broker pipeline.

A social lead has usually asked for something small: a checklist, a calculator, a guide, an event or an answer.

Deliver that thing first. Do not disguise a sales sequence as access to a free resource.

1. Opt-In - Free Thing

• Entry trigger — The person requests the stated resource.
• Stage job — Deliver it, and confirm what they agreed to receive.
• Automation allowed — Send the resource, tag the source and store consent evidence where applicable.
• Human handover — A direct finance question or a callback request.
• Exit condition — Delivered, replied, undeliverable, or opted out.

2. A.I Conversation

• Entry trigger — The person responds to the resource delivery.
• Stage job — Route a simple request, or bring the broker in.
• Automation allowed — Clearly identified AI can ask a limited approved question, offer a callback or appointment, and notify the broker.
• Human handover — Anything situational, sensitive, advice-related, or outside the approved response library.
• Exit condition — Booked, handed over, no response, not qualified for this path, or opted out.

The public label should make the system’s role clear. The OAIC recommends that organisations identify public-facing AI chatbots and maintain human oversight where personal information is involved.

3. No Response

Stop the resource follow-up after the approved bounded sequence. Do not treat a download as permanent permission to send unrelated marketing.

4. Not Qualified

Record the actual reason, and offer only a next step that fits. Someone researching for next year may belong in a permission-based nurture process; someone who opted out does not.

5. Booked

Confirm the appointment and transfer the relationship to the broker. Carry the original content source into the meeting notes, so the broker knows what started the conversation.

Warm relationships need less automation, not more.

A former client, accountant, buyer’s agent, local business owner or personal contact can usually detect when a personal message has been generated at scale. The system should help the broker remember context and follow through. It should not imitate friendship.

1. Contact Added

Record who the person is, how the broker knows them, the source of the introduction, the permitted contact method, and the next genuine reason to speak.

Do not add people to a marketing sequence merely because their details are available.

2. Nurture

The stage job is to remain useful over time.

Appropriate system support includes reminders, relationship notes and suggested relevant content. The broker should choose the message and send it in their own voice when the context is personal.

3. Solve Small Issue

Help with one bounded problem before asking for a larger commitment.

That could mean explaining a process, pointing to a public resource, making an appropriate introduction, or clarifying what information would be needed later. It should not be a manufactured favour.

The stage exits when the issue is resolved, a genuine finance conversation starts, or no further action is wanted.

4. Coffee / Drinks

This is a human relationship stage.

The system may remind the broker to reach out. It should not autonomously invite someone for coffee or drinks, negotiate times, and continue a personal conversation as if it were the broker.

Use the stage when a real relationship justifies it. Rename it if your business prefers a more inclusive or professional label, such as Relationship Meeting.

Cold outreach has the least relationship and the highest need for restraint.

It is not a shortcut around consent. Australian commercial electronic messages generally require consent, accurate sender identification and a functional unsubscribe mechanism. Telemarketing also sits within Do Not Call Register and industry rules. A purchased list or a publicly visible address should not be treated as automatic permission.

This is general information, not legal advice. Have your cold-outreach process reviewed before activating it.

1. Prospect

• Entry trigger — A person or business fits a documented audience rule, and the proposed channel has passed the required permission and suppression checks.
• Stage job — Confirm relevance and lawful contact conditions before sending.
• Automation allowed — Research administration, deduplication, list hygiene, and Do Not Call or suppression checks where applicable.
• Human handover — Approval of the audience, the message, the source and the real relevance signal.
• Exit condition — Approved to contact through the chosen channel, excluded, or suppressed.

2. Open

An email open is a weak technical signal, not intent.

Do not move someone into the broker pipeline or call them interested because tracking recorded an open. Keep the record in outreach until the person takes a meaningful action.

3. Replied

Any reply should stop the automated sequence.

A positive or questioning reply belongs with a person. A negative response, an unsubscribe or a correction should be honoured and recorded promptly.

4. Opt Out

Opt Out is a suppression state, not a future campaign list.

Store the minimum information needed to honour the request across connected systems. Stop the relevant automation, and make sure a later import cannot silently re-enrol the person.

Acquisition and delivery should connect without becoming one enormous board.

The acquisition pipeline answers where the person came from, what they asked for, what permission and context exist, and whether a real conversation or booking has happened.

The broker delivery pipeline answers what work is now being performed, what evidence or action is missing, who owns the next step, and what milestone has actually been reached.

When a person becomes a genuine broker opportunity, move or create the record in the main pipeline and preserve the acquisition source.

Pre-Submission

The precise meaning of Prelim / Pre-AOL and AOL Submission should be defined in the operating procedure the brokerage uses. A stage label alone is not a control.

Approval - Settlements

Do not let an automated email alone prove that a consequential milestone has occurred. Define the source of truth for each movement.

Construction Loans

Construction schedules vary. Treat these as configurable labels, then define the evidence, owner, lender requirement and exception path for each stage before automating reminders.

Post Settlements

Stages 25 and 26 collapse into the same event easily. Give each a distinct trigger and job, or combine them. Two labels for one event create unreliable reporting and duplicate contact.

For a deeper post-settlement workflow, see why brokers lose clients at refinance.

Use automation where the correct action is predictable.

Good candidates include:

• creating or updating an opportunity from a verified event;
• assigning an owner;
• recording the acquisition source;
• creating an internal task;
• sending an approved acknowledgement or reminder;
• stopping a sequence when a reply, booking or opt-out occurs;
• notifying a broker about an exception; and
• moving a record only when an observable condition is true.

HighLevel’s published documentation describes pipelines as stages in a sales or service process, and supports creating or updating opportunities through workflows. It also recommends making stages action-oriented and defining clear progression rules.

That vendor capability does not decide the right broker process. The brokerage still has to define the event, the owner, the evidence and the boundary.

Keep people responsible for the moments that shape trust or require judgement.

That includes:

• discovery and clarification of the client’s objectives;
• any discussion that could become credit assistance or product advice;
• vulnerability, hardship, complaints and urgency;
• explanations of why information is required;
• interpretation of nuanced replies;
• relationship outreach to warm contacts and referral partners;
• qualification decisions that affect how a person is treated; and
• any situation where the person asks for a human.

AI can draft, classify and summarise. A person should review the context and own the response.

The OAIC’s AI guidance emphasises due diligence, transparency, accuracy and human oversight when personal information is processed with commercially available AI products.

Do not automate all four pipelines at once.

1. Choose one acquisition channel with a clear offer and permission model.
2. Define its entry event, its stages and its exclusions.
3. Write one approved message for each stage that genuinely needs an external message.
4. Add reply, booking, opt-out and human-handover stop rules.
5. Assign every live stage to a person or a named queue.
6. Test with internal records across normal, duplicate, no-response and opt-out paths.
7. Review real conversations before expanding the sequence.
8. Add the second channel only once the first can be operated reliably.

Structure beats volume here.

A small sequence the team understands will sound more human than a large sequence nobody can explain.

Separate how a person was acquired from how their finance work is delivered.

Use paid, social, warm and cold pipelines to preserve context. Use the main broker pipeline once real work begins. Give automation the repeatable administration, and give the broker the conversation.

That is how follow-up stays consistent without becoming impersonal.