Course platform emails: Teachable, Thinkific, GetCourse deliverability

For a course creator, the deliverability of platform emails determines whether students complete the course. Lesson-drip emails that land in spam mean students don't see the next lesson and silently drop off. Completion certificates that don't arrive mean refund requests. Re-engagement emails that get filtered mean lapsed students never come back. The platform you choose is the platform you live with.

Per-platform sender setup

How each major platform handles outbound email:

• Teachable: sends from noreply@teachable.comby default. Higher tiers (Pro, Business) allow custom sender via white-label setup. Underlying ESP rotates; historically uses Mandrill / Mailgun.
• Thinkific: default sender is platform-owned. Custom domain SMTP available on Pro+ plans via SPF/DKIM configuration. Solid deliverability profile.
• Kajabi: uses its own infrastructure with custom- sender support. Decent at major providers, weaker at regional providers.
• GetCourse: Russian-origin platform, dominant in Russia / CIS. Strong deliverability at Yandex and Mail.ru, weaker at Gmail and Outlook for international students.
• Podia: uses Postmark under the hood. Generally strong deliverability inheriting Postmark's reputation.
• LearnWorlds: custom domain SMTP on most tiers. Quality depends on your own ESP setup if you use the custom-SMTP option.

Custom domain SMTP: when and how

If your platform offers custom-domain SMTP and you have any sending volume worth caring about, set it up. The benefits:

• Emails come from your brand domain, not the platform's. Recognition and trust improve.
• You inherit your domain's reputation rather than the platform's shared one.
• You can route sending through a transactional ESP you control (Postmark, SES) for better placement.
• Compliance and brand consistency — no platform watermarks in your student-facing emails.

The setup work: configure DNS records (SPF, DKIM) per the platform's instructions, sometimes a CNAME for tracking domains, and verify in the platform admin. 30 minutes of work for a meaningful ongoing improvement.

Lesson-drip emails: the highest-stakes category

Course completion correlates strongly with lesson-drip deliverability. A student who doesn't receive the Lesson 3 reminder doesn't open Lesson 3, doesn't complete it, and is far less likely to complete the course. Drip emails are the highest-leverage category in the entire course email programme.

Test the full drip end-to-end before launch. Sign up to your own course as a test student with seed inboxes at Gmail, Outlook, Apple iCloud, and the regional providers your students use. Let the drip run on its actual schedule (or simulate). Record placement of each email.

Common findings: Lesson 1 lands in Inbox; Lesson 2 lands in Promotions because it has a different template; Lessons 3-7 accumulate in Promotions and the student never sees them.

Completion certificates: link, don't attach

Many platforms email completion certificates as PDF attachments. Don't. PDFs trigger filtering at corporate Outlook 365 in particular, and the certificate often ends up in quarantine.

Better pattern: email the student a link to download the certificate from the platform. The link can lead to a platform-hosted page where the student can preview, share, and download. Adds engagement, removes the deliverability risk, and lets you track who actually downloaded.

For platforms that only offer attached certificates, escalate with the platform vendor — it's a recurring complaint and most platforms now have link-based options.

Re-engagement and dormant-student emails

Re-engagement emails to students who haven't logged in for 30+ days are particularly filter-prone. Long-inactive recipients have weak engagement signals; their mail provider treats new sends to them with suspicion.

Best practice:

• Send re-engagement from a personal sender (instructor name) rather than the course brand.
• Short, conversational copy. "Are you stuck? Reply and tell me where."
• Sunset students who don't respond after 2-3 re-engagement attempts. Continued sending to disengaged users hurts your sender reputation.

Seed-test methodology for course platforms

Standard methodology adapted for course platforms:

• Set up seed accounts at major providers (Gmail, Outlook, Yahoo, Apple iCloud, plus regional providers).
• Enrol each seed in your course as a test student.
• Let the drip sequence run on real timing or accelerated timing if your platform allows.
• Record placement of each email at each provider.
• Repeat monthly. Track time-series to catch degradation.

For platforms without an obvious accelerated-timing option, run the test on a real cohort schedule. Slower but more accurate.

Frequently asked questions