> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating an email

> Write a branded, sendable email from a template and a brief, then review what came back.

You create an email by describing it to Mary, allGood's AI. The more of your setup you hand Mary, the less she has to invent: a template provides the layout, a component library provides the blocks, and the brand guideline provides the voice.

**Prerequisites**

* A verified sending domain. See [Set up an email domain](https://docs.allgoodhq.com/mk/settings/email/domains-setup.md).
* Optional but recommended: a published [email template](https://docs.allgoodhq.com/mk/content/email/templates/index.md), an [Email Components library](https://docs.allgoodhq.com/mk/content/email/components/index.md), and [brand guidelines](https://docs.allgoodhq.com/mk/content/brand-guidelines.md).

## Steps

**1. Start the email**

In **Content**, select **Create** and choose **Email Asset Generator**. Name the email and brief it: the goal, the audience, the key message, the call to action, and anything it must or must not say.

**2. Attach your template, components, and brand**

Choose the template to start from, and link your component library and brand guideline. You can skip this, and the email will still come out, but nothing checks it against your approved blocks.

**3. Review what came back**

You get the email, and its copy as a separate document. If your brief called for more than one version, you also get a [content router](https://docs.allgoodhq.com/mk/content/copy-and-variants.md), which decides who sees which version.

![An email asset: subject, preheader and the rendered message.](https://mintcdn.com/allgoodtechnologyinc/LW4p5NqCb6SZm7Lp/images/mk/content/email/emails/email-detail.png?fit=max\&auto=format\&n=LW4p5NqCb6SZm7Lp\&q=85\&s=ee8cd4b3eb2ec0b797bc22dd5a6533ff)

An email asset: subject, preheader and the rendered message.

**4. Preview it and send yourself a test**

See [Previewing and testing an email](https://docs.allgoodhq.com/mk/content/email/emails/previewing-and-testing-an-email.md).

**5. Publish it**

Publishing locks in the email's copy, template, component library, and brand at the versions you reviewed.

When this works, you will see the email in **Content** with a **Published** status, and its copy listed as a separate asset beside it. It is ready to send once your account setup is complete. See [Before an email can send](https://docs.allgoodhq.com/mk/content/email/emails/before-an-email-can-send.md).

## If the email will not save

If you build from a component library, allGood checks each section against its approved block. If a section no longer matches its block, the save stops and the message names the block and what differs. See [Component libraries](https://docs.allgoodhq.com/mk/content/component-libraries.md) for how the check works.

If you are still stuck, contact [support@allgoodhq.com](mailto:support@allgoodhq.com).

## Related articles

* [What an email is](https://docs.allgoodhq.com/mk/content/email/emails/what-an-email-is.md)
* [Personalizing an email](https://docs.allgoodhq.com/mk/content/email/emails/personalizing-an-email.md)
* [Editing an email's code](https://docs.allgoodhq.com/mk/content/email/emails/editing-the-code.md)
* [Email not sending or rendering wrong?](https://docs.allgoodhq.com/mk/content/email/emails/troubleshooting.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.