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

# Email

> Connect incoming support email to Voiceflow, choose a mailbox, receiving API or help desk and deliver reviewed replies with a developer-hosted relay.

## Overview

Use Voiceflow to answer incoming support email and continue the conversation when a customer replies. These installation manuals supply a developer-hosted text relay: it receives mail, runs the released agent, keeps sender/thread state and sends a reviewed response. Your team operates hosting, credentials, mail delivery and recovery.

Start with a [support agent](/docs/guides/usecases/customer-service/build-faq-agent) and approved [Knowledge](/docs/documentation/build/importing-data-sources). The sample handles public support questions; sender addresses do not authorize private account access. It holds attachments and ambiguous input for human review.

**Note:** 

**Sending a follow-up?** Use the existing [Gmail tool](/docs/documentation/build/tools/gmail-tool) or [conversation-summary guide](/docs/guides/integrations/gmail/send-conversation-summary). They send email during another conversation; they do not receive an incoming agent channel. The manuals below teach a hosted relay, not a managed Studio inbox connector.

<a id="planned-content" />

## Choose a connection

| Starting resource | Receiving path | Installation guides |
| --- | --- | --- |
| Existing supported user mailbox | OAuth mailbox API polling; preserve its read flags. | Gmail, Outlook or Zoho Mail. |
| Dedicated receiving address/domain | Signed/authenticated inbound webhook; SES uses receipt rules and S3 polling. | Amazon SES or one of the six receiving email APIs. |
| Existing support platform | Native email-to-ticket/conversation receiving, then API polling and reviewed native email replies. | Ten help desk manuals below. |
| Another mailbox host | TLS IMAP polling and authenticated SMTP; host must permit the supplied password/app-password method. | IMAP/SMTP. |

Keep receiving and sending independent: a successful send API call cannot prove the agent received the customer's message. Each connection manual includes its own permissions, exact inbound route, reply delivery, hosting and customer test.

| Connection | Receiving path |
| --- | --- |
| [Gmail / Google Workspace](/docs/guides/channels/email/gmail) | Gmail API Inbox polling. |
| [Outlook / Microsoft 365](/docs/guides/channels/email/outlook) | Graph Inbox polling. |
| [Zoho Mail](/docs/guides/channels/email/zoho-mail) | Zoho folder polling. |
| [Amazon SES](/docs/guides/channels/email/amazon-ses) | SES receiving MX + active receipt rule. |
| [Twilio SendGrid](/docs/guides/channels/email/sendgrid) | SendGrid MX. |
| [Mailgun](/docs/guides/channels/email/mailgun) | Mailgun receiving MX. |
| [Postmark](/docs/guides/channels/email/postmark) | Postmark generated inbound address. |
| [Resend](/docs/guides/channels/email/resend) | Resend receiving address. |
| [Brevo](/docs/guides/channels/email/brevo) | Brevo receiving MX. |
| [Mailjet](/docs/guides/channels/email/mailjet) | Mailjet generated Parse address. |
| [IMAP/SMTP](/docs/guides/channels/email/imap-smtp) | TLS IMAP polling with UIDVALIDITY/UID. |
| [Zendesk](/docs/guides/channels/email/zendesk) | Native support email + assigned ticket/conversation polling. |
| [Intercom](/docs/guides/channels/email/intercom) | Native email conversations; bot-email feature flag required. |
| [Freshdesk](/docs/guides/channels/email/freshdesk) | Native support email + assigned ticket/conversation polling. |
| [Help Scout](/docs/guides/channels/email/help-scout) | Native support email + assigned ticket/conversation polling. |
| [Front](/docs/guides/channels/email/front) | Native support email + assigned ticket/conversation polling. |
| [Gorgias](/docs/guides/channels/email/gorgias) | Native support email + assigned ticket/conversation polling. |
| [HubSpot Service Hub](/docs/guides/channels/email/hubspot) | Native support email + assigned ticket/conversation polling. |
| [Salesforce Agentforce Service](/docs/guides/channels/email/salesforce) | Email-to-Case + EmailMessage polling. |
| [Zoho Desk](/docs/guides/channels/email/zoho-desk) | Native support email + assigned ticket/conversation polling. |
| [Microsoft Dynamics 365 Customer Service](/docs/guides/channels/email/dynamics-365) | Queue/case email polling + tracking-token replies. |

Help desk examples keep review before sending enabled and use native assignment for human takeover. Their existing Integration docs retain tools, records, Knowledge and chat handoff.

## Guides

These shared workflows start after the connection receives and replies correctly:

- **[Answer support emails](/docs/guides/channels/email/answer-support-emails)** — use approved policy Knowledge and text-compatible instructions.
- **[Keep conversations together](/docs/guides/channels/email/keep-conversations-together)** — preserve useful context while separating new threads and senders.
- **[Review replies before sending](/docs/guides/channels/email/review-replies-before-sending)** — inspect, correct, approve or discard a cached response.
- **[Handle attachments safely](/docs/guides/channels/email/handle-attachments-safely)** — review original evidence without claiming automatic file interpretation.

## Test and release

Test from an inbox you control through the installed receiving address. Confirm the original mail, the intended runtime transcript, a reviewed provider send and the actual customer inbox. Then reply in-thread and check continuity. Exercise duplicate delivery, automatic responses, held files and interrupted processing before launch.

Keep three releases distinct: the published agent/Environment, your relay deployment/database and the provider's receiving/sending configuration. Repeat the complete test on the production address; a browser Run, health endpoint or saved webhook establishes only part of the path. Preserve pending work and a human support route during changes.

<a id="existing-documentation" />

## Related documentation

The [Chat agents APIs](/docs/api-reference/agent-runtime/chat) own exact session/action/response contracts. [Authentication](/docs/api-reference/authentication) owns credential boundaries; [Transcripts](/docs/documentation/measure/transcripts) helps inspect the agent exchange. Provider installation belongs in the manuals above, while [Gmail follow-up](/docs/guides/integrations/gmail/send-conversation-summary) retains its existing outbound workflow.
