White-Label Email (SMTP)
Send client-facing emails from your agency's own mail server and address.
By default, emails the platform sends on your behalf come from ds160.io. Connect your own SMTP server and your client-facing emails go out from your mail server and your From address instead — so the experience matches your brand end to end.
What you’ll need
- An active Business workspace.
- Owner or Admin access to that workspace.
- SMTP credentials from your email provider (host, port, username, and password), plus the From name and address you want clients to see.
Add your SMTP settings
Open Workspace Settings → Email Sending (SMTP) and fill in:
| Field | Notes |
|---|---|
| SMTP Host | Your provider’s outgoing mail server, e.g. smtp.yourdomain.com. |
| Port | Defaults to 587. Any port from 1–65535 is accepted; port 465 uses implicit TLS. |
| Username | The login for your SMTP account. |
| Password | The SMTP password. |
| From Name | The display name clients see, e.g. your agency name. |
| From Email | The address clients see in the From field, e.g. noreply@yourdomain.com. |
Click Save to store the settings.
Your password is write-only. It’s encrypted before it’s stored and is never shown again. When you edit other fields later, leave the password blank to keep the saved one — only type a password if you want to replace it.
Test the connection
Before relying on it, click Test connection. The platform opens a connection to your SMTP server and authenticates with the details you entered. You’ll get a green confirmation on success, or a red message with the server’s error if something’s wrong (wrong host/port, bad credentials, or a firewall blocking the connection).
What these settings power
Today your SMTP settings are used to send client intake link emails — when you email a client their secure intake link, it goes out through your server, from your address. See Emailing Clients Their Intake Link for that workflow.
Platform notifications (for example, account and billing emails) continue to send from ds160.io.
To also serve the intake form itself under your own domain, pair this with Custom Domains.