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.
| Name | Status | Trigger | Updated |
|---|---|---|---|
Finish their setup Promoted from campaign | active | user.signed_up | Today |
Welcome sequence | active | user.signed_up | Mar 12 |
Trial ending soon | active | trial.ends_at | Feb 28 |
Quiet account check-in | paused | usage.dropped | Jan 14 |
Win-back | draft | subscription.cancelled | - |
Treated converted at 2.5× the holdout. Opens do not count.
312 skipped · 112 unsubscribed · 98 suppressed · 102 frequency cap
Behavior segments, several angles, a small ramp, and a holdout. You read revenue and lift, then decide what goes always-on.
Drafts in your voice, recommends the strongest, and you can edit a line before it sends.
You signed up last month and stopped at the integration step. It trips up almost everyone. Here is the two-minute version…
Most engaged people first, not the full list. Five percent get nothing. Same caps on every send.
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 →
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.
A visual canvas with the trigger, the wait, the condition, and the email: same editor you would use if you built it yourself.
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.
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.
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.
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 →
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.
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.
Yes. SMS steps run through your Twilio account. You pay Twilio; Ranla triggers the step inside the automation.
Connect a GitHub repo, or analytics. Then talk in the agent window: templates, campaigns, automations. It still asks before it sends.