Automations

Build automations that react to what people do.

Ranla runs one-off campaigns first (segment, draft, ramp, holdout), then promotes what beats the control into always-on automations. Email, plus SMS steps on your Twilio account.

AutomationsNew automation
NameStatusTriggerUpdated
Finish their setup
Promoted from campaign
activeuser.signed_upToday
Welcome sequence
activeuser.signed_upMar 12
Trial ending soon
activetrial.ends_atFeb 28
Quiet account check-in
pausedusage.droppedJan 14
Win-back
draftsubscription.cancelled-
Campaigns

Prove what works before you automate it.

Behavior segments, several angles, a small ramp, and a holdout. You read revenue and lift, then decide what goes always-on.

What it writes

Ranla drafts three angles and recommends one.

Drafts in your voice, recommends the strongest, and you can edit a line before it sends.

Finish their setup3 angles · 1 recommended
Angle A
Angle BRecommended
Angle C
Two steps left in your setup

You signed up last month and stopped at the integration step. It trips up almost everyone. Here is the two-minute version…

How it sends

Every send starts small, with a holdout that gets nothing.

Most engaged people first, not the full list. Five percent get nothing. Same caps on every send.

Send planWaiting on your approval
Audience
4,120 people
First send
400 today · most engaged first
Daily cap
400 until the cohort is through
Holdout
5% get nothing
Stops if
Complaints pass 0.1%
When they write back

Ranla reads replies and drafts answers in your voice.

Safe questions can go out on their own. Refunds, churn, and anything sensitive land with a draft ready for you. Replies shape the next segment and the next send. Reply system →

Always-on

Turn winners into always-on automations.

Nothing goes always-on until it has beaten a holdout. Approving turns the send into a trigger. Declining leaves it as a campaign you can send again by hand. Welcome, activation, trial, win-back share cancel rules and frequency caps so campaigns and automations do not pile on the same person.

What you get

Approve it, and this is what Ranla builds.

A visual canvas with the trigger, the wait, the condition, and the email: same editor you would use if you built it yourself.

Automations/Finish their setup
active
SavePause
Triggeruser.signed_up
DelayWait 3d
Condition · stop if falseStop unless activated_at exists
Send emailFinish their setup
Step 4 · send email
Published templateFinish their setup
SubjectTwo steps left in your setup
Cancel whenactivated
What you already have

It works on your existing automations too.

Rewrites, retimes, and removes overlap

A welcome sequence written before half your product existed still describes the old one. Two automations firing on overlapping triggers send the same person two emails in a day. Both show up when something is actually reading them.

Suggestions come as changes you approve, not edits that appear one morning.

One frequency count across everything

Your automations, your campaigns, and Ranla's own sends share a single count per person. An automation that fired yesterday is why a campaign holds off today.

Run log

Every run is logged.

Automations fire on events, not on a send list, so you follow one person at a time. Who entered, which step they are on, and whether they converted.

Finish their setup847 people this week
Who got this
What happened
  1. Started by user.signed_upMar 4, 9:14 AM
  2. Waited 3 daysMar 7, 9:14 AM
  3. Condition matched, continuedactivated_at not set
  4. Email sentFinish their setup
Channels

Email first. SMS when a step needs it.

Lifecycle and transactional email share one sending path and one suppression list. Email → Connect Twilio under Integrations to send SMS from automation steps. You pay Twilio directly; Ranla orchestrates the send. Integrations →

FAQ

Automations questions

How do Ranla automations work?

Ranla runs campaigns first with a holdout, then promotes winners into always-on automations that fire on product behavior. Email, plus SMS steps on your Twilio account.

What is the difference between a campaign and an automation?

A campaign is a one-off send with a control group so you see lift. An automation is always-on for every user who hits that moment afterward. Both share one frequency count per person.

Can automations include SMS?

Yes. SMS steps run through your Twilio account. You pay Twilio; Ranla triggers the step inside the automation.

Get started

Put Ranla to work this week.

Connect a GitHub repo, or analytics. Then talk in the agent window: templates, campaigns, automations. It still asks before it sends.

Start free