# Known issue acknowledged email template

> Explore this known issue acknowledged email template for technology and software. Preview its status, three key details, and next action.

Source: https://design.moosewave.com/templates/known-issue-acknowledged-email-template/

---

Transactional Service & account

# Known issue acknowledged email template

A recurring bug admitted before the customer has to prove it.
Illustrative example. Replace the fictional sender, dates, amounts, locations, and account details before use.
**Best for**
: A recurring bug admitted before the customer has to prove it
**Structure**
: State or event context · Plain-language explanation · Three labelled facts
**Style**
: signal · bookish
**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.

Being told a widely reported bug is a local configuration problem is exhausting. It is not. It affects a specific browser version and we can reproduce it.

### 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**
: Michelmersh Support
**Subject**
: Yes, this is a real bug and you are the 41st to report it
**Preheader**
: Not your setup. Ours. Fix is in testing.
Known issue

### Forty-one reports, one bug, and it is genuinely ours

Being told a widely reported bug is a local configuration problem is exhausting. It is not. It affects a specific browser version and we can reproduce it.

#### Reports

41

#### Cause

Confirmed and reproducible

#### Fix

In testing
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 ↗ Service & account Account dormant An inactive account flagged before anything is deleted Technology & software](/templates/account-dormant-email-template/)
[002 Transactional Open preview ↗ Service & account Bio updated A public field updated with a note about visibility Technology & software](/templates/bio-updated-email-template/)
[003 Transactional Open preview ↗ Service & account Browser extension installed An add-on installed with its permissions explained plainly Technology & software](/templates/browser-extension-installed-email-template/)
[004 Transactional Open preview ↗ Service & account Daily digest instead of alerts Individual notifications collapsed into one summary Technology & software](/templates/daily-digest-instead-of-alerts-email-template/)