> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/ai-agents/slack-telegram-email-and-mcp/using-agents-with-email.md).

# Using Agents with Email

JetAdmin agents can be used through email by enabling a dedicated email inbox for the agent.

Once enabled, agent receives its own email address. Anyone can interact with the agent by sending emails to that address, and the agent will automatically reply back to the sender.

This allows users to communicate with agents directly from any email client without opening JetAdmin.

### Before You Start

Make sure you:

* Created an agent in JetAdmin
* Have access to edit the agent settings

### Setup

{% stepper %}
{% step %}

1. Open your agent
2. Click **Add to**
3. Select **Email Inbox**
4. Click **Enable Email Inbox**

After enabling email inboxes, the agent will receive a dedicated email address.

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FwahExuhb5GtFcmzSSEs2%2Fimage.png?alt=media&amp;token=cf89429c-e91b-4b41-b5b3-1319b54858de" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Create or Edit Agent Email Address

After enabling the email inbox, a unique email address is automatically generated for the agent.

You can:

* Use the generated email address immediately
* Edit the email address and customize it&#x20;

This email address is used to receive messages sent to the agent.

After setup:

* **Use this Email address to message your Agent**

<figure><img src="https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FLIGBbFxAq2lmSVbePjkn%2Fimage.png?alt=media&amp;token=f432a2e6-28e2-4f4b-aa82-04e418ab44b8" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
After setup is complete, users can send emails directly to the agent’s email address. The agent will automatically reply to the sender’s email inbox.
{% endhint %}
{% endstep %}
{% endstepper %}

### Example Use Cases

| Use Case            | Description                                           |
| ------------------- | ----------------------------------------------------- |
| Customer Support    | Automatically answer customer questions through email |
| Internal Assistants | Help employees with internal requests and information |
| FAQ Automation      | Respond to common questions automatically             |
| Lead Qualification  | Collect and qualify inbound leads                     |
| AI Email Responders | Generate automated email replies                      |
| Request Handling    | Process operational or support requests               |


---

# 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.jetadmin.io/ai-agents/slack-telegram-email-and-mcp/using-agents-with-email.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.
