# Deprecation notice email template

> Explore this deprecation notice email template for technology and software. Preview its status, three key details, and next action.

Source: https://design.moosewave.com/templates/deprecation-notice-email-template/

---

Transactional Alerts & status

# Deprecation notice email template

An old endpoint being retired with usage data for the customer.
Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.
**Best for**
: An old endpoint being retired with usage data for the customer
**Structure**
: State or event context · Plain-language explanation · Three labelled facts
**Style**
: manual · newsprint
**Industry fit**
: Technology & software
Responsive design preview

## See the message before you make it yours.

Compare the desktop and mobile compositions, or unfold the full design. The complete starting copy remains readable below.
Want to change the copy and style?

## Try one of the editable browser templates.

This page is a read-only reference. The five hands-on studios let you edit a local preview, compare desktop and mobile, and review every change before continuing.
Message anatomy

## A useful starting point, with the important parts named.

Rather than a general notice, here is your own usage. Two of your integrations account for all of it and both need a one-line change.

### What you can change

- Brand name
- Subject line
- Preheader
- Eyebrow
- Headline
- Supporting copy
- Primary action label
- Primary action URL

### What to keep clear

- State or event context
- Plain-language explanation
- Three labelled facts
- Primary and secondary action
- Support or privacy footer
Complete starting copy

## Read it as text, not only as a picture.

**From**
: Ovington Alerts
**Subject**
: You are still calling the old endpoint 4,100 times a day
**Preheader**
: It goes away in six months. Here is what to change.
Deprecated

### Four thousand calls a day to something that disappears in April

Rather than a general notice, here is your own usage. Two of your integrations account for all of it and both need a one-line change.

#### Your calls

About 4,100 daily

#### Removed

1 April

#### Sources

2 integrations
Moosewave MCP

## Give an agent the structure, the job, and a stopping point.

The brief asks for a new draft and stops before send.

**Read the complete brief**
Connected work

## Take the design beyond the canvas.

Keep exploring

## Related transactional templates

[001 Transactional Open preview ↗ Alerts & status Latency increased A performance regression reported with the honest cause Technology & software](/templates/latency-increased-email-template/)
[002 Transactional Open preview ↗ Alerts & status Queue backing up A processing backlog reported with the clearance estimate Technology & software](/templates/queue-backing-up-email-template/)
[003 Transactional Open preview ↗ Alerts & status Anomaly detected Unusual activity flagged with the reasoning shown Technology & software](/templates/anomaly-detected-email-template/)
[004 Transactional Open preview ↗ Alerts & status Backup failed A failed backup reported the same morning with the real exposure Technology & software](/templates/backup-failed-email-template/)