Operational email scope
Open Workspace settings → Email & templates → Delivery. These settings govern platform and supported operational module email. Reach campaign delivery and campaign mailbox access remain separate.
Use workspace administrative access. Provider availability and the fields shown in the editor determine the supported connection options. Connecting a mailbox for operational sending does not grant inbox access.
Configure delivery
- Choose the managed sender option or a supported customer-owned provider shown in Delivery.
- For a customer-owned account, enter its sender display name and From email. Set Reply-to if responses should go to another monitored address.
- Complete the provider’s required connection fields or use the Google Workspace or Microsoft 365 connection action shown on screen.
- Choose unified routing or, once the custom connection is ready, route supported modules individually.
- Review the module sender-name and reply-to overrides, then save the configuration.
Review the selected delivery provider and sender identity. Provider-specific setup must use your own authorized account.
Account details and configuration values are hidden.Routing and sender inheritance
Unified routing uses the selected provider and default sender for supported operational modules. Individual routing lets selected modules use the connected account while others retain their default sender.
For the managed option, the sender identity is controlled by the platform. Use the allowed reply-to control rather than trying to replace a managed From address. Blank Reply-to uses the From address.
Connect a customer-owned email account
For Google Workspace or Microsoft 365, enter a valid From email before selecting the connection action. Authorize only the intended sending account, then return to Delivery and confirm Connected. The workspace connection is for sending operational email, not reading the inbox or enabling Reach campaign mailboxes.
For Custom SMTP, obtain the host, port, username and password from your email provider. Set the connection-start TLS option according to that provider’s instructions. Enter credentials only in the protected settings form; do not include them in template content or screenshots.
If your account uses a customer-owned cloud email option shown in Delivery, use that provider’s verified sending identity and complete only the fields required by the editor. Availability in your workspace determines which choices you can use.
- A customer-owned From address must be valid for the connected account or verified identity.
- Microsoft account setup includes the tenant value shown in the editor; obtain the appropriate value from your account administrator.
- Keep the monitored reply destination independent from the account used to send if the business needs a separate support inbox.
- When a secret field is already configured, follow its retention guidance before replacing the stored credential.
Review the delivery path
Confirm the connection status and selected sender after saving. Check that the required modules are routed to the intended account and that reply destinations are monitored.
Previewing an email checks content and appearance; it does not prove delivery. Verify a permitted operational message with an approved recipient before wider use.
Resolve connection or routing problems
For a failed mailbox connection, check the account identity and provider authorization. Reconnect through the action shown in Delivery if needed.
For unexpected sender details, review unified versus individual routing and module overrides. If messages are not received, review the visible delivery status and the recipient’s mailbox filtering before retrying. Keep credentials out of support messages.
Related guides
Ask your workspace administrator for access or contact support with the page name and a sanitized error message.