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 and approved Knowledge. The sample handles public support questions; sender addresses do not authorize private account access. It holds attachments and ambiguous input for human review.
Sending a follow-up? Use the existing Gmail tool or conversation-summary guide. 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.
Choose a connection
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.
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 — use approved policy Knowledge and text-compatible instructions.
- Keep conversations together — preserve useful context while separating new threads and senders.
- Review replies before sending — inspect, correct, approve or discard a cached response.
- 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.
Related documentation
The Chat agents APIs own exact session/action/response contracts. Authentication owns credential boundaries; Transcripts helps inspect the agent exchange. Provider installation belongs in the manuals above, while Gmail follow-up retains its existing outbound workflow.