Integrations (BYOK)
Custom Transactional Email: Resend, Brevo, SendGrid & SMTP
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.
Choosing a Provider
| 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 |
Connecting Resend, Brevo, or SendGrid
- Create an account with your chosen provider and verify your sending domain (this involves adding DNS records like SPF and DKIM — the provider will give you exact instructions).
- Generate an API key from that provider's dashboard.
- In Koursely, go to Settings → Integrations → Email, select your provider, and paste in the API key.
- Set your "from" name and email address — this must match a verified domain on your provider account, or emails may be rejected or land in spam.
Connecting Custom SMTP
- Gather your SMTP host, port, username, and password from your email host (this is often the same provider hosting your business email, like Google Workspace or Microsoft 365).
- In Koursely, select SMTP as your email provider and enter these details, along with the security mode (SSL, TLS, or Auto-detect).
- Send a test email to confirm the connection before relying on it for real student communication.
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.
Frequently Asked Questions
What happens if I don't connect an email provider?
Transactional emails still send, but from a shared Koursely sending domain rather than your own — functional, but not fully white-labeled.
Can I use my personal Gmail account for SMTP?
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?