# Customer emails in Marketing

Customer emails are personal emails you send for a Marketing release in
[Marketing](/user-guide/product/marketing). Reading them needs **Contacts: Read** as well as
**Marketing: Read**, and sending them needs **Marketing: Create**.

**Customer emails** lists every customer behind a feature request or a bug report the Marketing
release covers, with the email Productmind wrote for them. Who that is comes from the sources:
- the people behind a feature request you attached;
- the people behind a feature request built into a feature you attached;
- the people behind the feature requests and bug reports a release you attached delivered;
- the people behind the feature requests and bug reports linked to customer feedback you attached.

Customer feedback that led to no feature request or bug report adds no one. At the top, a checklist
shows which public release notes the drafts sum up (and which version), whether the attached
releases are **Released**, when a release is attached, and whether the drafts are written.

Each customer's row shows their name, their account and email address, how many of their items the
Marketing release covers (for example **2 requests · 1 fix**) and a status:

| Status | Meaning |
| --- | --- |
| **Not sent** | Nobody has emailed them about this Marketing release yet. |
| **Sent** and a date | They were emailed about this Marketing release on that date. |
| **Failed** | The last email to them couldn't be delivered. You can send it again as a first email. |
| **Unconfirmed** | Sending was interrupted, so the email may have gone out. Sending again asks you to confirm. |
| **No email** | The contact has no email address. Add one to the contact to email them. |
| **Invalid email** | The contact's email address isn't valid. |
| **Opted out** | They stopped these emails, or your team turned them off. |

Customers with no email, an invalid one or who opted out are listed but can't be selected. A
request from an account with no contact is listed under the customers, since there is nobody to
email.

## To write the drafts

1. In **Marketing**, open the Marketing release and choose **Customers** under **Customer emails**
   in its menu.
2. Choose **Write drafts**.
3. Choose which public release notes the emails sum up. The most recently published ones are
   chosen for you.
4. Confirm.

Or choose **+** beside **Customer emails** in the Marketing release's menu, then **Write drafts**.

Productmind writes a short paragraph about what's new for each request and each bug the Marketing
release covers, then puts each customer's email together from their own items. Until the drafts are
written, an email uses each item's title, marked **Not written yet**. Choose **Stop** to stop.

The public release notes you choose must be published, and not unpublished since: the summary of
the rest comes from them. Writing the drafts doesn't wait for the attached releases: only sending
does.

## To edit a customer's email

1. Choose the customer.
2. Change the subject (saved when you leave it) or the text under **Text** (saved as you type).

**Preview** shows the email as the customer gets it. You can comment and ask **@pm** as on the notes.

To add an image, choose **Insert image** in the toolbar, paste one, or drag a file into the text
(PNG, JPG, GIF or WebP, up to 10 MB). Images start private, and an email carries only its **public**
images: select an image and choose **Make public** to include it. **Preview** shows exactly the
images that will be sent, and says how many private images won't be.
An email nobody changed is sent as Productmind wrote it, signed by whoever sends it.

**Reset to the written draft** brings back the email Productmind wrote, and keeps its comments. Writing the drafts again
never replaces an email you edited: when newer drafts are written after your edit, the customer shows
**Use the new draft**, which replaces your edit with the new one.

## To send the emails

1. Select the customers to email. Customers already emailed about this Marketing release start
   unselected.
2. Choose **Send** (it says how many customers).
3. Check the list. Customers you already emailed are marked **Send again**. If an email may name
   another customer, confirm you checked it. An email with private images is marked: those images
   are left out of what the customer gets.
4. Confirm.

Each customer gets their own email. The results show who was emailed and, for anyone who wasn't, why.
You can send at most 50 emails at a time.

Sending needs every attached release to be **Released** (with no release attached, nothing waits),
the public release notes the drafts sum up to be live, and no drafts being written.

## To read the send log

Choose **Send log**. Choose an email to read exactly what was sent.

## How customers stop these emails

Every email ends with **Stop these emails**. It opens a page with one button, so a customer's mail
scanner can't unsubscribe them by opening the link; after it, **Undo** turns the emails back on.
Their mail app's own **Unsubscribe** button works too. On the contact, your team can switch
**Release update emails** off or on, and see when and how they were stopped. See
[Contacts](/user-guide/feedback/contacts).

## Troubleshooting

### Customer emails says to publish the notes first

Each email sums up the rest from published public release notes. Publish the Marketing release's
notes, then choose **Write drafts**.

### Customer emails says the release notes were unpublished

The notes the drafts sum up were unpublished, so nothing can be sent. Open those notes and choose
**Republish version** with its number, or publish your changes. Or choose **Write drafts** again and
pick notes that are published.

### A customer is missing from Customer emails

Customers come from the feature requests and bug reports the Marketing release's sources cover:
- their interest must be linked to a contact, not only to an account;
- the request must be attached, built into a feature you attached, delivered by a release you
  attached, or linked to customer feedback you attached;
- customer feedback that led to no feature request or bug report adds no one;
- work under a [private feature](/user-guide/product/private-features) is never included.

### Send is unavailable

A release you attached isn't **Released** yet, the notes the drafts sum up aren't live, drafts are
being written, or no customer is selected. Or your role doesn't include **Marketing: Create**.

### A customer wasn't emailed

The results say why: for example, someone else emailed them meanwhile, their email changed since you
reviewed it, it names another customer and you didn't confirm, or they were already emailed and you
didn't choose **Send again**.

## Related topics

- [Marketing](/user-guide/product/marketing)
- [Blog posts in Marketing](/user-guide/product/marketing-blog-posts)
- [Contacts](/user-guide/feedback/contacts)
