Ranla writes in your voice and shares one suppression list with transactional mail so a marketing unsubscribe never blocks a password reset.
Hey {{first_name}},
You signed up {{signed_up_at}} and stopped at {{last_incomplete_step}}. Last event I see is {{last_event}} on {{last_seen_at}}.
I finished that step. Your workspace is ready. Nothing left to configure.
If it's useful, pick up where you left off today.
Campaigns and automations for onboarding, activation, and win-back, with holdouts so you know what earned. Automations →
Password resets, receipts, and product mail on the same API and reputation. Transactional email →
When someone writes back, classify intent, draft in your voice, and send only when the confidence gate clears. Reply system →
2,000 most recent · 400/day · 15% holdout. Nothing sends until you approve.
Ranla waits here, not in your inbox.
Ranla writes the email, sets the ramp and holdout, then stops. Nothing goes out until you approve.
Ranla is the email platform. Lifecycle and transactional mail share one API and one suppression list. The agent is built in; it drafts and asks before it sends.
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.
No. Ranla is the ESP for PLG SaaS teams that need automations and audiences from product behavior, not an agent bolted onto mail you already send elsewhere.
Connect a GitHub repo, or analytics. Then talk in the agent window: templates, campaigns, automations. It still asks before it sends.