Lifecycle email

Lifecycle email for activation, retention, and win-back.

Lifecycle email is one of Ranla's six jobs. It writes campaigns and automations from what people do in your product, sends them from our own mail infrastructure, and measures each one against a holdout on the goal you named. Transactional mail shares the same stack and one suppression list.

Campaigns and automations

One-off campaigns for onboarding, activation, and win-back, each with a holdout so you know what earned. Winners become always-on automations. Automations →

Transactional

Password resets, receipts, and product mail on the same API and the same reputation. Transactional email →

Replies

When someone writes back, it classifies intent, drafts in your voice, and sends only above a confidence threshold. Replies inbox →

Measured against a holdout

Every send holds back a slice of people. Lift is read on activation, paid conversion, or the goal you set, not on opens. Analytics →

Guides to onboarding, activation, and win-back email →

One of six

Email is one job. The other five run beside it.

Same product events, same conversion goals, same brand kit. The segment a campaign mails is the segment Google Ads matches.

Engineering → · Paid advertising → · Search and AEO → · Social →

Modes

You choose Draft, Propose, or Autopilot.

Ranla writes the email, sets the ramp and the holdout, then does what your mode says. Draft leaves the send to you. Propose asks before each send. Autopilot sends inside the limits you set. Any audience over 5,000 people waits for your approval in every mode.

Questions

Email questions

Is email the whole product?

No. Email is one of the six jobs. Ranla owns the send path, so lifecycle and transactional mail share one API and one suppression list. It drafts and asks before it sends.

Can I send password resets and marketing from the same place?

Yes. Transactional and lifecycle go out the same way. A marketing unsubscribe never blocks a password reset. See the transactional page for API and SDK examples.

Do I need another ESP?

No. Lifecycle and transactional mail go out on this stack. Paid, search, AEO, social, and engineering run here too. It is not an agent bolted onto mail you already send elsewhere.