Onboard new users, convert trials, retain customers, and send transactional messages — all triggered by what users actually do in your product. AledaMail connects product events to email workflows without requiring you to build the email layer yourself.
SaaS products generate predictable events at every stage of the customer journey. Each event is an opportunity for a relevant, timely email. AledaMail lets you build automations that respond to these events without writing custom email delivery code.
Trigger a welcome sequence. Confirm the account. Start an onboarding drip. Event: user.created or trial.started
If the user has not completed key setup steps after 2 days, send a nudge. Personalise based on which steps are missing. Event: onboarding.step_skipped or time-based condition.
Celebrate the milestone. Suggest the next step. Deepen engagement at the moment of first value. Event: feature.used
Send a conversion sequence as the trial end approaches. Highlight what they will lose. Make upgrading easy. Event: trial.expiring (3 days, 1 day, day-of).
Confirm the upgrade. Welcome them to the new plan. Introduce features they now have access to. Event: subscription.upgraded
Notify immediately. Give clear instructions to update billing. Send reminders on day 3 and day 7 if not resolved. Event: payment.failed
If a user has not logged in for 14 days, trigger a re-engagement sequence. Remind them of value. Offer help. Event: time-based condition on last login date.
Respond with a save sequence. Address common objections. Offer a pause option if available. Event: subscription.cancel_requested
AledaMail accepts custom events from your application via API. An event triggers automations in real time — no batch processing, no waiting for a nightly sync.
User begins a free trial. Trigger onboarding welcome, day-2 check-in, and trial expiry sequence.
POST /api/tx/v1/events
User upgrades from trial or lower plan. Send upgrade confirmation and feature introduction.
POST /api/tx/v1/events
User uses a key feature for the first time. Celebrate and suggest the next action.
POST /api/tx/v1/events
Payment attempt fails. Trigger immediate notification and a dunning sequence.
POST /api/tx/v1/events
Trial ending in N days. Trigger conversion sequence with urgency and upgrade CTA.
POST /api/tx/v1/events
Define any event name your product generates. Build automations around your specific product milestones.
POST /api/tx/v1/events
Multi-step onboarding drips triggered by signup. Personalise based on user properties and which onboarding steps have been completed. Branch the sequence based on user behaviour.
Automated trial conversion sequences triggered by trial start. Time-based emails at day 3, day 7, day-before-expiry, and day-of. Personalised with plan details and upgrade links.
Password resets, receipts, account alerts, and system notifications via a REST API. Template-driven with variable substitution. Separate sending stream from marketing email.
Automated payment failure notification and dunning sequence. Configurable retry cadence. Stops automatically when payment is recovered.
Identify inactive users by last login or last activity date. Trigger a re-engagement sequence. Branch based on whether users respond.
Send product update newsletters and feature announcements to your user base. Segment by plan, signup date, or feature usage to target the right users.
Connect Amazon SES, SendGrid, Mailgun, or Postmark. At SaaS scale, BYOS delivery costs are substantially lower than bundled per-contact platform pricing.
Segment users by plan, trial status, feature usage, custom events, and any subscriber property your application sends. Target campaigns precisely.
SaaS products send two fundamentally different types of email: marketing (campaigns, lifecycle sequences, newsletters) and transactional (password resets, receipts, alerts). AledaMail manages both in one interface while keeping them on separate sending streams, domains, and suppression lists where appropriate.
Mixing transactional and marketing email on the same stream and domain is a deliverability risk. A marketing campaign that generates complaints can damage the reputation of the domain you use for password resets. AledaMail makes it straightforward to separate the two without requiring two entirely separate platforms.
Read more: managing transactional and marketing email together →Yes. AledaMail accepts custom events via API. Your application sends an event — trial.started, payment.failed, feature.used — and AledaMail triggers the matching automation. Event properties are available as variables in email templates.
Yes. AledaMail includes a separate transactional email REST API alongside the marketing platform. You can manage both from one platform while keeping them on separate sending domains and suppression lists — which is the recommended approach for SaaS products.
Customer.io has more mature enterprise lifecycle tooling, deeper customer data platform capabilities, and multi-channel support (SMS, push). AledaMail is more affordable, gives you control over sending infrastructure, and includes agency multi-workspace for teams managing multiple products. See the full comparison for an honest breakdown.
Yes. AledaMail is a BYOS platform — you connect your own Amazon SES, SendGrid, Mailgun, or Postmark account. At SaaS scale, this is typically much cheaper than per-contact pricing on bundled platforms. Your sending infrastructure remains yours if you ever switch platforms.
Connect your sending infrastructure. Build event-driven automations. Free to start.
Start free →