Integrations (BYOK)
Support articles, setup guides, and troubleshooting docs
Integrations (BYOK)
Send enrollment confirmations, password resets, and certificates from your own domain instead of a shared one.
Every action a student takes — enrolling, resetting a password, completing a course — can trigger a transactional email. Connecting your own email provider means these arrive from your domain, improving both deliverability and brand consistency.
| Provider | Good Fit If... |
|---|---|
| Resend | You want the simplest modern setup with a generous free tier |
| Brevo | You also want marketing email/CRM features from the same provider |
| SendGrid | You're already using SendGrid elsewhere or need enterprise-scale sending |
| Custom SMTP | You want to use your existing email host's SMTP credentials directly |
Domain verification (SPF/DKIM) is not optional for good deliverability. Skipping it is the single most common reason transactional emails land in spam — set aside time for this DNS step, not just the API key connection.
Transactional emails still send, but from a shared WeMakeSuccess sending domain rather than your own — functional, but not fully white-labeled.
Technically possible with an app password, but not recommended for anything beyond testing — personal Gmail accounts have low sending limits and aren't built for transactional volume.
Was this article helpful?