The next email waits for what each person does.
A path that pays attention to every person on it.
Waits that wait for the person.
Wait a set time, until a weekday and hour in each person’s own timezone, or until they do something: open the email, visit a page, log in or do an action in your product. They move on the moment they act, or when the limit you set runs out.
Only what a person did counts.
Apple Mail loading the images by itself is not an open, a security scanner following the links is not a click, and an out-of-office is not a reply. When it says when they are back, the path holds their emails until that date.
Every email knows the ones before it.
Each email Behavly writes is put together for one person as it sends, from what they did on your site and every earlier email on the path, with whether they opened or clicked it. It says something new each time, and Skip if they already did it leaves out what they have done.
The path reviews itself every Monday.
Once a campaign has sent 20 emails, Path review reads its results and suggests what to change: new instructions for a step, a different wait, an A/B test to start or end. Each suggestion says why, with the path’s numbers. Nothing changes until you apply it.
How automated follow-ups wait for each person.
Someone enters.
A path starts when a person joins a group, in a Pattern Campaign that runs once or always on, or the moment your product sends a trigger, in a Trigger Campaign. From then on, each person moves along it on their own.
Waits and branches react.
A wait can end the moment the person acts, not only when time passes. A branch checks whether they opened the previous email, clicked a link in it, logged in, visited a page, replied or did an action in your product within the days you set: yes goes one way, no the other once the days run out.
Each email is written as it sends.
An email Behavly writes is put together at send time from what that person did, in your sender’s voice. Instructions for Behavly Agent say what it is for, and Reply in the same thread sends the emails after the first as replies in one thread, like a follow-up from a colleague.
The goal is counted.
Name the Goal as an action in your product, such as upgraded, or a page visit. Behavly credits each person who reaches it to the last email they got, counting while they are on the path and for 7 days after their last email.
They leave when it’s done.
A reply ends the path by default, unsubscribing or bouncing always does, and reaching the goal can too. Once the campaign has sent 20 emails, Path review suggests changes every Monday, and nothing changes until you apply one.
The guardrails around it
- Across campaigns
- One person on several paths never gets an email from each. By default, different campaigns stay 24 hours apart, and nobody gets more than 3 emails in any 7 days.
- When they write to you
- A reply ends the path by default, and their other campaigns wait 3 days. Out-of-office replies don’t count.
- Priority
- Urgent emails, like a failed payment, never wait for the guardrails. Low ones, like newsletters, also wait 3 days after any other campaign’s email.
- Goal
- Name an action or a page, and each person who reaches it is credited to the last email they got, counted up to 7 days after their last email.
- Changing a live path
- Publish changes and newcomers take the new path, while people already on it finish the version they started.
- Review before sending
- Off by default. Turn it on to hold every email Behavly writes until you release it. Held emails never expire, and templates sent as designed always go on time.