> For the complete documentation index, see [llms.txt](https://docs.empowergpt.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empowergpt.ai/workflows/workflow-usecases/smart-email-assistant.md).

# Smart Email Assistant

### Problem Statement

Consider a customer service professional who receives multiple emails throughout the working day.

The user needs to regularly check their inbox, read incoming emails, understand what each sender requires, and prepare an appropriate response.

Some emails may also require a meeting. In these cases, the user needs to check their calendar, identify available time slots, and include suitable meeting times in the response.

Repeating this process for every incoming email can consume a significant amount of time.

<figure><img src="https://2192711725-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fc2KRGWrkyRO0iZN5Lyeg%2Fuploads%2FXAwIpS2HEkwo0m7ZtJkL%2Fimage.png?alt=media&amp;token=c2991abb-b859-479e-a2bc-235585cf0b5b" alt=""><figcaption></figcaption></figure>

### Solution Using Workflows

The **Smart Email Assistant** automates the initial processing of incoming emails.

The workflow is triggered automatically when a new email is received. It reads the email, understands the request, and prepares a draft response.

When the email requires a meeting, the workflow also checks the user's calendar for available time slots and includes them in the drafted response.

The email remains a **draft**, allowing the user to review it before sending.

### Using Smart Email Assistant

Unlike manually executed workflows, the Smart Email Assistant works automatically once configured.

When a new email arrives:

1. The workflow is automatically triggered.
2. The workflow reads the email body.
3. It determines the appropriate response based on the contents of the email.
4. If a meeting is required, the workflow checks the connected calendar for available time slots.
5. The available meeting times are included in the drafted response.
6. If no meeting is required, the workflow prepares a reply without meeting availability.
7. The response is saved as a **draft in the user's inbox** for review.

### How It Works

The workflow follows two possible paths depending on the contents of the received email.

**When a meeting is required:**

**New Email → Read Email → Identify Meeting Requirement → Check Calendar Availability → Draft Reply with Available Times**

**When no meeting is required:**

**New Email → Read Email → Generate Response → Draft Reply**

For example, if a customer sends:

> Could we schedule a meeting next week to discuss the proposal?

The workflow recognizes that a meeting is required, checks the calendar for availability, and prepares a response containing suitable available times.

If the customer instead asks a question that does not require a meeting, the workflow prepares an appropriate response without checking for meeting availability.

### Result

The user no longer needs to manually prepare an initial response for every incoming email or repeatedly check their calendar when a meeting is requested.

The Smart Email Assistant prepares the response and, where necessary, includes available meeting times while keeping the final email as a draft for the user to review before sending.


---

# 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.empowergpt.ai/workflows/workflow-usecases/smart-email-assistant.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.
