Email Notification Examples: 12 Types and How to Write Them

An email notification is an automated message triggered by an event in a product or account, telling the user that something changed or needs their attention. A good one states the event in the subject line, gives the one detail that matters, and offers one action. A usage alert says which limit was hit, a task assignment says who assigned what, and a sync failure says which integration stopped and how to fix it.

This page gives 12 product notification examples, each with when to send it, a subject line, original sample copy and what to include. They cover usage alerts, trial and renewal notices, digests, collaboration emails, incident updates and policy changes. For receipts, password resets, security alerts and mention emails, see our transactional email examples, which this post deliberately does not repeat.

The 12 Notification Types at a Glance

“Nature” below is our working classification under CAN-SPAM, covered in detail later. Treat it as a starting point for your own review, not a verdict.

Notification	Trigger	Urgency	Nature	Primary action
Usage or quota alert	Usage crosses 80% or 100% of a limit	Send now	Transactional	Review usage or upgrade
Trial ending reminder	3 days before trial end	Scheduled	Transactional if informational, mixed if promotional	Choose a plan
Subscription renewal notice	7 to 30 days before renewal	Scheduled	Transactional	Review billing
Activity digest	Daily or weekly schedule	Batch	Transactional if only account activity	Open the workspace
Task assignment	Someone assigns a task	Send now or batch	Transactional	Open the task
Due date reminder	24 hours before due	Scheduled	Transactional	Open the task
Workspace invitation	Teammate invites a user	Send now	Transactional	Accept invitation
Approval request	Item needs sign-off	Send now	Transactional	Approve or reject
Incident and status update	Outage starts, then resolves	Send now	Transactional	Read status page
Export or report ready	Background job completes	Send now	Transactional	Download file
Integration or sync failure	Sync fails repeatedly	Send now, then limit	Transactional	Reconnect
Terms or policy change	Legal terms update	Scheduled in advance	Transactional (relationship)	Read changes

The sample copy below uses a fictional project tool called Tideboard and the placeholder domain example.com. Adapt the wording to your own voice and variables.

Account and Billing Notifications

These four tell users where they stand with a plan. They affect money or access, so clarity matters more than charm.

1. Usage or Quota Alert

When to send it: when usage crosses a threshold such as 80% and again at 100%. Two stages give users time to act before anything breaks. Do not send a third reminder every day afterward.

Subject line: You've used 80% of your Tideboard storage

Hi Maya,

Your Tideboard workspace "Northwind Design" has used 8 GB of its 10 GB
storage limit (80%).

At your current pace you will reach the limit in about 11 days. Uploads
will pause at 100%, but existing files stay available.

Review storage: https://app.example.com/settings/storage

Include: the exact limit, the current usage, what happens at 100%, and an estimate only if you can calculate it reliably. Avoid: upsell language in the first message. If the user ends up in the upgrade flow, that is their choice.

2. Trial Ending Reminder

When to send it: a few days before the trial ends, and once on the final day. This is the notification closest to marketing, so keep it informational. For the wider onboarding picture, see our guide to lifecycle sequences.

Subject line: Your Tideboard trial ends on March 14

Hi Maya,

Your Tideboard trial ends on March 14, 2027 at 9:00 AM PST. After that,
your workspace becomes read-only until you pick a plan. Your projects
and files are kept for 30 days.

You created 3 projects and invited 4 teammates during the trial.

Choose a plan: https://app.example.com/billing/plans

Include: the exact end date and time in the recipient’s time zone, what changes, and what happens to their data. Avoid: countdown pressure and discount banners, which can turn an informational email into a commercial one.

3. Subscription Renewal Notice

When to send it: ahead of an automatic renewal, especially annual plans, so no charge comes as a surprise. If a card fails after renewal, hand off to your dunning emails rather than extending this one.

Subject line: Your Tideboard Team plan renews on April 2

Hi Maya,

Your Tideboard Team plan (annual, 12 seats) will renew on April 2, 2027.

Amount: $1,440.00, charged to the Visa ending in 4242.

To change seats, update your card or cancel before renewal, go to
Billing settings: https://app.example.com/billing

Questions? Reply to this email.

Include: plan, seats, amount, date, payment method, and a plain way to change or cancel. Avoid: burying the cancellation path. Hiding it invites chargebacks and complaints.

4. Terms or Policy Change Notice

When to send it: before updated terms or a privacy policy take effect, with enough lead time to read them. The FTC lists notifying a recipient “about a change in the terms or features of a membership, subscription, account, loan or other ongoing commercial relationship” as a transactional or relationship category, so this is a standard use.

Subject line: Updates to Tideboard's Terms of Service, effective May 1

Hi Maya,

We are updating the Tideboard Terms of Service and Privacy Policy. The
changes take effect on May 1, 2027.

What changed: we clarified how long deleted workspaces are retained
(now 30 days) and added a list of our data processors.

Read the full changes: https://example.com/legal/changes
You do not need to do anything to keep using Tideboard.

Include: the effective date, a plain-language summary of what changed, and a link to the full text. Avoid: marketing content in the same message, since it weakens the transactional classification.

Collaboration Notifications

Collaboration products send the highest volume of notifications, which makes these the best candidates for batching and preferences.

5. Activity Digest

When to send it: on a daily or weekly schedule, replacing many individual alerts. A digest is the main tool against fatigue, and it should be skipped entirely when nothing happened.

Subject line: Your Tideboard week: 14 updates across 3 projects

Hi Maya,

Here is what happened in your workspace since Monday, March 8.

Website relaunch
- 6 tasks completed, 2 new comments
Q2 planning
- 3 tasks assigned to you
Onboarding docs
- 1 approval waiting for you

Open your workspace: https://app.example.com
Change digest frequency: https://app.example.com/settings/notifications

Include: counts grouped by project, items that need the reader’s action first, and a link to adjust frequency. Avoid: feature promotion inside the digest. Mixed content raises the CAN-SPAM question covered below.

6. Task Assignment

When to send it: when someone else assigns a task to the user. Self-assignments should not trigger an email.

Subject line: Jordan assigned you "Review launch checklist"

Jordan Lee assigned you a task in Website relaunch.

Review launch checklist
Due: Friday, March 12, 2027

Jordan's note: "Can you check the redirects section before we go live?"

Open task: https://app.example.com/tasks/4821

Include: who assigned it, the task title, the project, the due date and any note. Avoid: sending one email per task during bulk assignment. Collapse them into one.

7. Due Date Reminder

When to send it: once, around 24 hours before the deadline, for tasks the user owns and has not completed. An overdue notice is a separate, rarer email.

Subject line: "Review launch checklist" is due tomorrow

Hi Maya,

"Review launch checklist" in Website relaunch is due tomorrow,
Friday, March 12 at 5:00 PM PST.

If the due date is wrong, you can change it from the task.

Open task: https://app.example.com/tasks/4821

Include: task, project and a deadline in the recipient’s time zone. Avoid: repeating the reminder at intervals. One reminder respects the user, three become noise.

8. Workspace Invitation

When to send it: immediately when a teammate invites someone. Invitation links should expire, and the email should say when.

Subject line: Jordan invited you to join Northwind Design on Tideboard

Jordan Lee ([email protected]) invited you to join the Northwind
Design workspace on Tideboard.

You will join as an Editor. This invitation expires on March 20, 2027.

Accept invitation: https://app.example.com/invite/k3x9
If you were not expecting this, you can ignore this email.

Include: the inviter’s name, the workspace name, the role being granted and an expiry. Avoid: a vague “You’ve been invited” subject. Recipients need to recognize a real person and team before they click.

9. Approval Request

When to send it: when an item is waiting on a specific person for sign-off. This is an action-required message, and it should name the decision plainly.

Subject line: Approval needed: Homepage copy v3 from Priya

Priya Shah submitted "Homepage copy v3" for your approval in Website
relaunch.

The release is scheduled for March 15, so a decision by March 12
keeps it on track.

Review and decide: https://app.example.com/approvals/772

Include: the requester, the item, any deadline that depends on the decision and a link straight to the review screen. Avoid: approve buttons that act on a single email click without confirmation, since mail scanners can trigger links.

System and Status Notifications

These messages report on the platform or a background job. Usually the reader needs to know quickly, so send them now rather than batching them.

10. Incident and Status Update

When to send it: once when an incident starts, once when it resolves, and at meaningful updates between. Send them to affected users only, and link to a status page for live detail.

Subject line: Tideboard incident: file uploads are delayed

We are investigating delays with file uploads in Tideboard. Started:
10:42 AM UTC. Existing files and comments are not affected.

We will email you when this is resolved. Live updates:
https://status.example.com

--- resolution email ---
Subject: Resolved: Tideboard file uploads are working again

Uploads recovered at 11:58 AM UTC. Files uploaded between 10:42 and
11:58 AM UTC may need to be re-uploaded.

Include: what is affected, what is not, the start time with a time zone and a resolution message. Avoid: speculating on cause or promising a fix time you cannot keep.

11. Export or Report Ready

When to send it: when a long-running job such as an export finishes. Skip the email if the user is still watching the progress screen.

Subject line: Your Tideboard export is ready to download

Hi Maya,

Your export "All projects (CSV)" finished. It contains 1,284 tasks and
is 2.1 MB.

The download link works until March 14, 2027 at 5:00 PM PST.

Download: https://app.example.com/exports/9f3a

Include: what was exported, size or row count, and the link expiry. Avoid: attaching the file to the email. Sensitive data belongs behind a signed, expiring link.

12. Integration or Sync Failure Alert

When to send it: after a sync fails repeatedly, not on the first transient error. Cap repeats so a broken connection produces one email, with a follow-up only if it stays broken.

Subject line: Tideboard lost its connection to your calendar

Hi Maya,

Tideboard could not sync with your Example Calendar account after 3
attempts. The last successful sync was March 9, 2027 at 8:14 AM PST.

Due dates are not appearing on your calendar until this is fixed.
This usually means the connection needs to be re-authorized.

Reconnect: https://app.example.com/integrations/calendar

Include: which integration, the last successful sync, the consequence and the fix. Avoid: error codes as the headline. Put them lower down for developers who need them.

How to Write a Notification Email

One event, one action: a notification should name what happened in the subject line, put the deciding detail in the first sentence, and offer a single primary action. Everything else is optional.

• Subject states the event. “Jordan assigned you a task” beats “Update from Tideboard”. Our guide to email subject lines covers length and testing.
• Lead with the detail. Put the deciding fact (amount, date, name) in the first line, not after a greeting paragraph.
• One primary button. Secondary links such as settings are fine, but only one should look like the action.
• Send a plain-text part. Litmus notes that “Spam filters like to see a plain text alternative. HTML-only emails are a red flag for spam filters.” Send both parts as multipart/alternative, which RFC 2046 defines, with the alternatives in “an order of increasing faithfulness to the original content.” See plain text vs HTML email for the tradeoffs.
• Choose a sender users can answer. A named sender with a working reply address gets replies and trust. See why to avoid a no-reply address for anything a user might need to answer, such as a billing question.
• Localize times and dates. Store timestamps in UTC and render them in the recipient’s time zone, with the zone abbreviation shown.

Avoiding Notification Fatigue

Nielsen Norman Group divides notifications into two kinds: action-required ones, which “alert the user of an event that requires a user action,” and passive ones, which “report a system occurrence that does not require any user action.” Treat that split as your batching rule. Action-required items (approvals, failures, expiring invitations) go out now. Passive items (comments, completions, activity) belong in a digest.

Practical limits that keep a notification program useful:

• Batch by default. Collapse bulk events into one email and offer a daily or weekly digest.
• Use thresholds. Alert at defined levels, once per level, not on every change.
• Cap repeats. One reminder, one follow-up, then stop.
• Offer a preference center. Let users choose what they receive, how often and on which channel, with sensible defaults rather than everything switched on.
• Skip empty sends. No activity means no digest.

Email is not always the right channel. A short-lived, in-the-moment signal (someone is typing, a teammate came online) fits in-app or push better, while anything that must persist or work offline, such as a receipt or an expiring link, fits email. We plan a dedicated comparison of the three channels.

Is a Notification Transactional or Marketing?

Under CAN-SPAM, what decides the category is the message’s primary purpose: an email containing only transactional or relationship content is transactional, and a notification that promotes a product is commercial. Most product notifications fall in the first group, and a feature announcement usually falls in the second.

The FTC’s CAN-SPAM compliance guide says that if a message “contains only transactional or relationship content, its primary purpose is transactional or relationship. In that case, it may not contain false or misleading routing information, but is otherwise exempt from most provisions of the CAN-SPAM Act.” Its list of transactional or relationship content includes messages that facilitate or confirm an agreed transaction, give security or safety information about a purchased product, notify about changes in terms or standing in an ongoing relationship, and deliver goods or services the recipient already agreed to.

The risk is mixing. The FTC says that if “a recipient reasonably interpreting the subject line would likely conclude that the message contains an advertisement or promotion for a commercial product or service or if the message’s transactional or relationship content does not appear mainly at the beginning of the message, the primary purpose of the message is commercial.” It also warns against assuming that “any message you send to recipients who have an ongoing commercial relationship with you” qualifies.

Message	Likely category	Unsubscribe link required by CAN-SPAM?
Quota alert, renewal notice, incident update	Transactional or relationship	No
Digest of the user’s own account activity	Transactional or relationship	No
Trial ending notice with discount offer	Mixed, may be commercial	Likely yes
Feature announcement or newsletter	Commercial	Yes

This is a general explanation, not legal advice. Even when no unsubscribe link is required, a notification preference link is good practice, and the law is one input next to provider policies and rules outside the US such as GDPR.

Sending Notifications From Your App

The pattern is the same for every example above: your app emits an event, a template fills in the variables, and your sending API delivers the message. Then delivery events come back so you can see what happened.

1. Event: the app records something such as task.assigned, with the data needed to render it.
2. Template: a stored template with variables like {{assignee_name}} and {{due_date}}, plus a plain-text version.
3. Send: an API call with the recipient, template and variables. Batch rules and rate limits are applied here.
4. Track: subscribe to delivery, bounce and complaint events using webhooks and suppress addresses that bounce.

This event-driven design is what makes these trigger emails, and it is the core of any transactional email setup. Coldletter’s template variables follow this same event-to-template model.

Frequently Asked Questions