Understand incoming email, service email, and alerts
Keep three different email jobs separate so each has the right configuration and test.
- Know which email path you are configuring.
Step-by-step walkthrough
- 01
Identify whether the message is a customer conversation, an application notification such as an invitation, or a server-monitor alert. These are different delivery paths.
- 02
For application invitations and recovery, review the central Service email sender with the platform operator. Working SMTP proves an outbound service path, not inbound mailbox import.
- 03
For customer email, connect a supported live email channel and configure its receiving provider, webhook, and sending identity. The current release offers sandbox email and a Resend live connector; it does not provide a generic IMAP mailbox importer.
- 04
For operational alerts, confirm the separate monitor sender and recipient. A received monitor email does not prove that customer conversations or staff invitations are configured.
- 05
Test each path independently with an owned mailbox. Check provider acceptance, actual arrival, department routing, and reply threading where applicable.
Expected result
The correct delivery path is identified before configuration changes.
Important details
Sandbox email sends no external mail. Creating a hosted mailbox alone does not create a RelayDesk inbox channel.
Need help with this workflow? Contact the team and include this guide’s title.