Behavior-Based Outreach Workflows for AI SDRs

A behavior-based outreach workflow changes the next message based on what the prospect did with the last one. Someone who replied "not now, try me in Q1" should get a different follow-up than someone who never answered. Most sequences ignore that and send step three to everyone on day nine.

This guide covers how we set up those branches when an OpenClaw agent runs outbound: which signals are worth acting on, which ones mislead, and what each branch should do. An earlier version of this page promised "5x sales," and the URL still says so. We have no controlled test that shows a multiplier, so we no longer make that claim.

Start with the signals you can trust

Not every engagement signal means what it appears to mean. Before building a branch on a signal, check how reliable it is.

• Replies. The only signal that is always a person. Read them, classify them, and let them drive most of your branching.
• Link clicks. Useful, with a caveat. Corporate security scanners open and click links before the recipient sees the email, so a click within seconds of delivery is usually a machine.
• Opens. Mostly noise. Apple Mail Privacy Protection preloads images for many recipients, so a large share of "opens" never involved a human. Don't send a "saw you opened my email" follow-up based on this.
• Site visits. You can only tie a visit to a person when they arrive through a link that identifies them. Anonymous traffic to your pricing page is not a trigger for a named prospect.
• Bounces and unsubscribes. Not engagement, but the most important branches you have. Both should stop the workflow immediately.

Sort replies before you branch on them

Because replies carry most of the information, the first job of the workflow is to put each one in a bucket. We use five:

• Interested: asks a question, asks for times, or forwards to a colleague. Hand off to a person or send a booking link the same day.
• Not now: gives a timeframe. Stop the sequence and schedule one check-in for the date they named.
• Wrong person: often names the right one. Ask permission before contacting the referral, and mention who pointed you there.
• Not interested or unsubscribe: stop, add the address to the exclusion list, and send nothing else.
• Out of office: pause until the return date, then resume where the sequence left off.

An agent can do this sorting well, but the ambiguous ones should go to a human. Ourguide to AI SDR reply handlingcovers the edge cases, and theexclusion list guidecovers what has to happen after an opt-out.

An example branch: the "not now" reply

Here is one branch written out in full, since this is the reply that sequences handle worst.

• Trigger: the reply contains a timeframe, such as "after the board meeting" or "check back in March."
• Step 1: end the active sequence for this contact.
• Step 2: send a two-line acknowledgment that repeats the date back to them.
• Step 3: create a task for the date they gave, with the original thread attached.
• Step 4: on that date, draft a short follow-up that quotes their reply. A person approves it before it goes out.

The approval step matters. Months later, the agent has no way of knowing whether the company was acquired, the contact left, or someone already signed with a competitor. A person can check in under a minute.

Personalize with facts, not merge fields

A template with [First Name] and [Industry] swapped in still reads like a template. What changes the reply rate is a sentence that could only be written to this person: a job post they published, a product they launched, a talk they gave. An agent can find those details, and the workflow should require one before a first email is sent.

Write down where each detail came from. When a prospect asks how you found them, you should be able to answer in one lookup. OurAI SDR audit log guideexplains what to record.

Test one change at a time

Branching makes testing harder, because each branch sees less traffic. A few rules keep the results readable:

• Measure replies and booked meetings, not opens.
• Change one thing per test, such as the subject line, the opening sentence, or the delay between steps.
• Wait for enough sends to mean something. At low volume, a gap of two or three replies is chance.
• Keep a log of what you changed and when, so a later drop in replies can be traced to a cause.

Where to start

If your current sequence has no branches, add three: stop on any reply, stop on a bounce or unsubscribe, and handle "not now" as described above. Those three cover most of the damage a fixed sequence does. Add click-based branches later, once you can filter out scanner traffic.