> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/tutorials/email-survey-design.md).

# Email Survey Design

Customize the design and branding of your email surveys

Customize the look and feel of the emails that deliver your Zigpoll surveys to match your brand.

#### Accessing the Email Designer

1. Go to **Surveys → Select your email survey**.
2. Click **Settings → Design**.
3. Select the **Email** tab.

#### What You Can Customize

* **Subject line** — The email subject your recipients will see
* **Body copy** — The contents of the email message
* **CTA button text** — The call-to-action button label
* **Logo** — Your brand logo displayed in the email
* **Colors** — The color scheme of the email template
* **Layout** — Choose whether to show a link to the survey as a button, or show the first question directly in the email

These changes apply to both manual email sends and automated webhook-triggered sends.

For more details on email surveys, see:

{% content-ref url="/pages/RNZ1XT4dEW5YQZsPeYGT" %}
[Email Zigpoll Surveys](/email-zigpoll-surveys.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigpoll.com/tutorials/email-survey-design.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.