# How to do the HTML Email Setup
The "**Send Email**" option from the engagement form is the same as setting up an **HTML Email**.
The "**Send Message**" option in the Customer Engagement Form allows users to send messages to customers through **three mediums**: WhatsApp, SMS, and email. However, the "**Send Email**" option only allows sending messages through a **centralized email account** that is set up from the admin portal.
{% hint style="success" %}
This ensures that all messages sent by different users within a particular campaign where the "Send Email" setup is being done are **triggered** from the specified centralized email ID.
{% endhint %}
### Steps:
***
1. Log in to your **NeoDove account** ([ https://connect.neodove.com/](https://app.neodove.com/) )
2. Navigate to the **Settings option** located at the bottom-left corner of the screen on the **Dashboard**.
3. A page will appear with **ten sections** out of which we need to click on the "**Preference**" option.
4. Then we need to click on the "**Select an email provider**" option from the bottom of the screen. Post that we need to select the **email provider** first for the particular email id which we want to set it up as a **centralized email id** for the triggering of messages from all the users or agents added in the particular campaign.
5. After selecting the email provider, we need to **put** the email id in the left hand side space and for the password we need to set it up **temporarily** from that particular email id only.
6. Navigate to that **particular email id** which needs to be set as a centralized email for the triggering of messages for all the users added in the **particular campaign**.
7. Post that, we need to click on the top right corner of the email and then need to click on the "**Manage your Google Account**" option.
8. A new window will appear, there we need to click on the "**Security**" option from the left hand side of the screen.
9. A new screen will appear where we need to scroll a bit down and need to switch on the **2-step verification** by clicking on that option.
10. Then, we need to put our **actual password** for the particular email id and then need to click on the "**Next**" button to proceed further.
11. After that again a new screen will appear where we need to scroll a bit down and then need to click on "**App Passwords**" option at the extreme bottom of the screen.
12. Post that, we need to put the name of the **software** for which we are trying to generate the **App** **password** that is NeoDove and then need to click on the "**Create**" option.
13. Once clicked on the "**Create**" option, a pop up will appear with a new temporary app password only for **NeoDove** specifically.
14. Then the new speciifc **App Password** for NeoDove to be **copied** from the Email section and need to be **pasted** in the Preference section under the **Settings Page** of NeoDove.
15. After putting the password, then need to click on the "**Save Changes**" option from the top right corner of the screen to get the **centralized email id setup** done for the HTML Email setup or the Send Email setup from any of the **Engagement form** of any campaign.
{% hint style="success" %}
**Note:** After the HTML Email setup, we can do some **test and trial** from some specific users or agents device in order to trigger the message through the "**Send Email**" option to check whether the email is **getting triggered** to customers from that particular centralized email id or not whose **setup** has just been done.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.neodove.com/admin-portal/campaigns/how-to-do-the-html-email-setup.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
