---
title: "Transactional Email as a Growth Channel (Not Just Notifications)"
description: "How to turn receipts, invites, usage alerts and digests into growth without breaking the rules for transactional mail: seven emails to improve, what to add to each, and how to send them with Reloop templates."
canonical: "https://reloop.sh/blog/transactional-email-as-growth-channel"
last-updated: "2026-05-12"
---

# Transactional Email as a Growth Channel (Not Just Notifications)

> For the site documentation index, see [llms.txt](/llms.txt). Docs index: [llms-docs.txt](/llms-docs.txt). Marketing corpus: [llms-full.txt](/llms-full.txt). Docs corpus: [llms-full-docs.txt](/llms-full-docs.txt). Product skill: [skill.md](/skill.md). Prefer markdown URLs (append `.md`) when available.

> How to turn receipts, invites, usage alerts and digests into growth without breaking the rules for transactional mail: seven emails to improve, what to add to each, and how to send them with Reloop templates.
Source: https://reloop.sh/blog/transactional-email-as-growth-channel
Published: 2026-05-12
**Transactional emails are the emails your users actually wait for and open: receipts, invites, password resets, usage alerts.** That attention makes them one of your best growth channels, as long as the transactional content stays the main point and the growth part is one small, relevant next step. Done right, an invite brings in a new user, a usage alert becomes an upgrade, and a receipt becomes a referral.

This guide covers seven transactional emails worth improving, what to add to each one, the line you shouldn't cross, and how to send them with Reloop.

---

## Why transactional email is underrated

Most teams treat transactional email as plumbing. Someone wires up a password reset during the first sprint, and nobody touches it again.

That's a missed opportunity, for three reasons:

1. **Expected.** The user just did something and is waiting for the email. It doesn't have to compete for attention the way a newsletter does.
2. **In context.** It arrives at the exact moment the user is engaged with your product.
3. **Reaches everyone.** Every active user gets transactional email. Many never read your marketing.

The goal isn't to stuff marketing into receipts. It's to make each transactional email do its job so well that the natural next step is obvious.

---

## The line you shouldn't cross

Transactional email is treated differently by law and by mailbox providers because it's something the user asked for. In the US, the FTC's guidance on CAN-SPAM uses a "primary purpose" test: if the message's main purpose is commercial, it's a commercial email and needs commercial rules, like an opt-out. Other countries have their own versions.

A practical rule of thumb:

| Keep it transactional | Crosses the line |
|---|---|
| Receipt plus "invite your team" link at the bottom | Receipt with a big banner for an unrelated product |
| Usage alert that mentions the plan that fits | "Flash sale!" subject line on a usage alert |
| Invite email that explains what the product does | Invite email that's mostly a feature tour |
| One relevant next step | Three promotions and a newsletter signup |

If you're unsure, ask: would this email still make sense if I removed the growth part? If yes, you're fine. Also keep marketing mail on a separate subdomain, so a campaign that draws complaints can't slow down password resets.

---

## Seven transactional emails to improve

### 1. Team invite

The invite is the only email from you that a brand-new person reads. It's an acquisition email that most teams write as an afterthought.

| Include | Why |
|---|---|
| Who invited them, by name | People trust colleagues, not products |
| What the product does, in one sentence | They've likely never heard of you |
| What they'll see when they accept | Removes uncertainty |
| A single "Accept invite" button | One action |

**Subject:** `Ada invited you to the Acme workspace on Acme Analytics`

### 2. Usage limit alert

When a user approaches a plan limit, they're getting real value. That's the best moment to talk about upgrading, because the reason is concrete.

**Subject:** `You've used 80% of your monthly events`

Show the number, the date it resets, and what happens at 100%. Then mention the plan that fits, with one link. Send at 80% and again at 100%, never more often than that.

### 3. Receipt

Receipts get opened and kept. After the line items, one short line is enough: a referral link, or "Add a teammate for $8/month."

**Subject:** `Receipt for your Acme Pro subscription, May 2026`

### 4. Weekly or monthly digest

A summary of what happened in the user's account ("312 new signups this week, up from 280") reminds people the product is working for them, even when they don't log in. It's one of the best inactivity defences there is, alongside the [churn sequences](/blog/email-reduce-churn-sequences) that react when usage drops.

Only send it when there's something real to report, and let users turn it off in a preference center.

### 5. Milestone

"Your 1,000th invoice sent." Milestones are tiny moments of delight, and they're shareable. A "share this" link or a short note about what power users do next fits naturally.

### 6. Activity notification

"Ada commented on your report." These bring people back into the product. The growth lever is the content: show the actual comment, not just "you have a new notification", so the email is useful on its own and clicking through is the obvious next step.

### 7. Password reset and magic link

Don't add anything here. These must be fast, plain, and only about signing in (our [password reset guide](/blog/password-reset-email-best-practices) covers what belongs in one). The growth play is reliability: a magic link that arrives in two seconds is part of a good first impression. One that [lands in spam](/blog/why-emails-land-in-spam-fix) loses the user.

---

## Measuring it

| Email | Primary metric |
|---|---|
| Team invite | Invite acceptance rate |
| Usage alert | Upgrades within 7 days of the alert |
| Receipt | Clicks on the referral or add-seat link |
| Digest | Logins within 48 hours of sending |
| Milestone | Shares or clicks |
| Activity notification | Click-through to the item |

Opens are unreliable because of privacy features like Apple Mail Privacy Protection, so measure clicks and the action that follows. Tag each send so you can split the numbers by email type.

---

## Send them with Reloop

Transactional growth emails carry per-user data: a name, a usage number, a date. The cleanest setup is one [template](/docs/learn/templates) per email, with variables, sent from your app at the moment the event happens.

### 1. Create a template with variables

In the Reloop dashboard, create a template for the usage alert, or [have AI draft it](/blog/ai-generate-transactional-email-templates) for you. Template variables use triple braces and can have a default:

```html
<p>Hi {{{first_name}}},</p>
<p>
  You've used <strong>{{{used}}}</strong> of your
  <strong>{{{limit}}}</strong> monthly events. Your usage resets on
  {{{reset_date}}}.
</p>
<p>
  At 100%, new events are queued until the reset.
  The {{{suggested_plan}}} plan includes {{{suggested_limit}}} events.
</p>
<p><a href="{{{upgrade_url}}}">Compare plans</a></p>
```

### 2. Send it when the threshold is crossed

```typescript

const reloop = new Reloop({ apiKey: process.env.RELOOP_API_KEY! });

  const percent = Math.round((usage.used / usage.limit) * 100);

  const { emailError } = await reloop.mail.send({
    from: "Acme <billing@mail.acme.com>",
    to: user.email,
    subject: `You've used ${percent}% of your monthly events`,
    template: {
      id: "tmpl_usage_alert",
      variables: {
        first_name: user.firstName ?? "there",
        used: usage.used.toLocaleString(),
        limit: usage.limit.toLocaleString(),
        reset_date: usage.resetsOn,
        suggested_plan: "Growth",
        suggested_limit: "1,000,000",
        upgrade_url: "https://acme.com/settings/billing",
      },
    },
    tags: [{ name: "type", value: "usage_alert" }],
  });

  if (emailError) console.error(emailError);
}
```

Call it from wherever you count usage, and store which thresholds you've already alerted on so each user gets the 80% email once per cycle.

### 3. Make retries safe

Usage checks often run in background jobs that retry. Add an `Idempotency-Key` so a retried job can't send the alert twice. With the REST API:

```bash
curl -X POST https://reloop.sh/api/mail/v1/send \
  -H "x-api-key: $RELOOP_API_KEY" \
  -H "Idempotency-Key: usage-alert-80-usr_123-2026-05" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Acme <billing@mail.acme.com>",
    "to": "ada@example.com",
    "subject": "You'\''ve used 80% of your monthly events",
    "template": { "id": "tmpl_usage_alert", "variables": { "used": "80,000", "limit": "100,000" } },
    "tags": [{ "name": "type", "value": "usage_alert" }]
  }'
```

See [idempotency](/docs/api/idempotency) for how long keys are remembered.

### 4. Send digests on a schedule

For a weekly digest, a cron job builds each user's summary and sends it with the same pattern: one template, variables for the numbers. Use `scheduled_at` if you want every digest to land at the same local time, for example Monday 9am in the user's timezone.

### 5. Give users control

Digests and milestone emails are optional. Put them in a [channel](/docs/learn/contacts/channels) (Reloop's subscription topics) so users can turn off "Weekly digest" in the preference center without unsubscribing from everything. Keep receipts, invites and security emails out of channels: users should always get those.

<Callout type="tip">
  Send transactional mail from its own subdomain (for example `mail.acme.com`) and marketing from another (`news.acme.com`). Reputation is tracked per domain, so a bad campaign can't drag down your password resets. Each subdomain needs its own [SPF, DKIM and DMARC](/blog/spf-dkim-dmarc-setup-guide) records.
</Callout>

---

## A quick audit you can do today

1. List every transactional email your product sends. Most teams find a few they forgot about.
2. For each one, write down its single job and its one possible next step.
3. Read them on your phone. Anything over a screen and a half is too long.
4. Check who they come from. Replace `noreply@` with a real `reply_to` where replies would be useful.
5. Make sure each has a tag, so you can measure clicks per email type.
6. Pick the two with the most volume (usually invites and receipts) and improve those first.

---

## FAQ

<AccordionGroup>
  <Accordion title="Can I put promotional content in a transactional email?">
    A small amount, if the transactional content is clearly the main point.
    In the US the FTC's "primary purpose" test applies; other countries have
    similar rules. Keep it to one relevant line or link, and check with your
    own legal counsel for anything more.
  </Accordion>

  <Accordion title="Do transactional emails need an unsubscribe link?">
    Purely transactional emails like receipts and password resets generally
    don't. Optional ones like digests should have one, and are best managed
    through subscription channels so users can opt out of just that type.
  </Accordion>

  <Accordion title="Should transactional and marketing email come from the same domain?">
    Use subdomains of the same brand domain, one for each. Recipients still
    recognise you, and reputation problems in one stream don't spill into
    the other.
  </Accordion>

  <Accordion title="Templates or HTML in code?">
    Templates. They let someone improve the copy without a deploy, and the
    same template can be sent from your app, an automation or the dashboard.
  </Accordion>
</AccordionGroup>

<Cta
  title="Send better transactional email"
  description="Templates with variables, tags, idempotent sends and subscription channels, on a free tier."
  href="/dashboard/signup"
  label="Get started"
/>