Sequences and automation

Email sequences that follow
what people actually did.

Welcome series, renewal reminders, and win-back emails that wait, branch, and follow up on their own. You get the automation the big-name platforms offer, and it sends through your own sending account.

Get started Take a tour
app.radarsend.com/t/kestrel-supply/sequences/come-back-to-kestrel
A sequence laid out from top to bottom: it starts, sends an email, waits, checks whether the person opened it, and splits into two paths depending on the answer.

A follow-up should depend on what the person did, not on a security scanner clicking a link in the email.

Start a sequence from almost anything a contact does.

A sequence can start when someone fills in a form, joins a list or segment, clicks a link, visits a page on your site, or reaches a date like a renewal. It can also start from something your own app reports, like a signup or a purchase.

From there you build the follow-up the way you'd describe it out loud: send the welcome email, wait three days, and if they haven't clicked, send a reminder. Along the way it can update a field, move someone to a new stage, or hand them to another sequence, and it stops as soon as they reach your goal.

Before you turn it on, run a preview. Tell RadarSend what an example contact does, and it shows the route they'd take and when each email would go out. Nothing is sent.

app.radarsend.com/t/kestrel-supply/sequences/come-back-to-kestrel
A sequence in preview: the canvas with the predicted route highlighted down the Yes path, beside a preview run panel with its assumptions and a predicted timeline of when the contact enters, gets each email, waits, branches, and completes.

A security scanner's click doesn't send anyone down the wrong path.

Many company inboxes run every link through a security scanner before a person sees the email, and some inbox previews open messages on their own. If a sequence counts those as a real open or click, a contact who never read the email gets the follow-up meant for someone who did.

RadarSend filters that activity out before a sequence checks it. If a click is still being checked, the sequence waits for the answer rather than guessing.

How RadarSend filters bots →
app.radarsend.com/t/kestrel-supply/sequences/come-back-to-kestrel/report
A sequence report: totals for enrolled, active, completed, converted, handed off and exited early, above a flow funnel showing how many emails each step sent, opened and clicked, split down the Yes and No paths after the branch.

See which step is working and where people drop off.

The report follows everyone through the sequence: how many reached each email, opened it, and clicked, which way each branch went, and how many reached the goal or left early. Bot opens and clicks are left out, so the numbers show how people responded.

One contact's enrollment in a sequence: converted, with the dates they entered and left and the reason, above the route they took. They were enrolled, sent an email they opened, sent down the Yes path because the open was recorded before the check, sent a follow-up, and left at the goal.

Know where each person is in the sequence, and how they got there.

Open any contact's enrollment and you'll see the route they took, the emails they got, which way each branch went, and why they left. If they're waiting, it says what for and when the next step happens.

Change a live sequence without starting over.

You can add a step, swap an email, or shorten a wait while people are partway through. RadarSend pauses the sequence while you edit, so nobody gets a half-finished version, and everyone picks up where they left off when you resume. You can also send a new step to people who already finished.

For a new sequence you'd rather watch closely, you can hold each email for review and approve it before it goes out.

Some jobs only need one step.

When a contact's lead score passes 70, send a webhook that posts to your sales team's Slack channel. When someone joins a segment, move them to a new stage or update a field. Automations handle one-step jobs like these without building a whole sequence.

app.radarsend.com/t/kestrel-supply/automations
The Automations page: two rules that fire when a customer's score passes 70, one posting a webhook to a Slack channel and one adding the contact to a list, above a log of webhook deliveries with each event, destination, time, and response.

Every sequence starts with what RadarSend already knows.

Sequences use the same contacts, segments, forms, and site activity as the rest of RadarSend, so there's no second copy of your list to keep in sync.

Sequences and automations come with every plan.

Get started Take a tour