Watchful lets you use your own SMTP server to send client reports from a custom email address. This helps you maintain a consistent brand identity when sharing reports with clients, especially when you use Watchful’s white-label reporting features.
You can configure your SMTP connection in your Watchful account settings.
How to configure custom SMTP settings
Before you begin, obtain your SMTP server details from your email provider. You’ll need the server hostname, port, username, password, and security protocol.
To configure your SMTP settings:
- Log in to Watchful.
- Select
Settingsfrom the left sidebar. - Open the
Generaltab. - Scroll down to the
Send email settingssection. - Complete the following fields:
Sender name: The name you want recipients to see when they receive your reports.Sender email: The email address you want to use when sending reports.Username: The username required to authenticate with your SMTP server. This is often your email address.Password: Your SMTP password or an app-specific password, if required by your provider.Host: The hostname of your SMTP server, such assmtp.example.com.Port: The SMTP port specified by your provider.Security protocol: SelectSSLorTLS, according to your provider’s requirements.
- Click
Save email settingsto save your configuration.
Once configured, Watchful can now use these settings when sending email.
Resetting your SMTP settings
If you no longer want to use a custom SMTP server, you can restore Watchful’s default email settings.
- Navigate to
Settings > General. - Scroll to the
Send email settingssection. - Click
Reset & Save email settings.
Watchful clears your custom SMTP settings and saves the default configuration. Future client reports will use Watchful’s default email delivery settings instead of your custom SMTP server.
Sending client reports using your SMTP server
Watchful uses your custom SMTP settings to send client reports from your chosen sender address.
This is especially useful for agencies that want reports to appear under their own business name rather than Watchful’s branding.
For more information about creating and sending reports, see Create client reports.
Troubleshooting SMTP email delivery
If Watchful cannot send reports using your custom SMTP server, check the following settings.
Verify your SMTP credentials
Confirm that your SMTP username and password are correct. Some providers require an app-specific password instead of your normal account password.
Also, make sure your account has permission to send email through the SMTP server.
Check the SMTP host and port
Verify the hostname and port with your email provider.
Common SMTP configurations include:
| Security protocol | Common port |
|---|---|
| TLS (STARTTLS) | 587 |
| SSL | 465 |
Use the configuration recommended by your email provider. Some providers support other ports or connection methods.
Check your security protocol
Watchful supports SSL and TLS options in the SMTP settings.
If the connection fails, confirm that your selected protocol matches the configured port and your provider’s requirements.
Using Gmail or Google Workspace
Google no longer supports the legacy Less Secure Apps authentication method.
If you’re using a compatible Google account with two-step verification, you may be able to create an app password for SMTP authentication.
However, some Google Workspace accounts restrict app passwords or require OAuth-based authentication, which may not be available through Watchful’s SMTP settings.
Consult your Google account administrator or email provider for the supported authentication method.
Using a transactional email provider
If you’re using a service such as SendGrid, Mailchimp Transactional (Mandrill), or Amazon SES, make sure you have:
- Verified your sending domain or email identity.
- Entered the correct SMTP credentials.
- Configured any required SPF, DKIM, or other email authentication records.
- Enabled SMTP sending for your account.
These steps can help prevent authentication failures and improve email delivery.