Custom SMTP
AvailableSend customer email from your own domain and mail server. Verified with a real test send before it goes live.
What ChurnNote reads
- Nothing. SMTP is outbound only
What ChurnNote cannot do
- Read your inbox
- Send from an address you have not verified with a live test send
- Silently drop a message: a rejected send falls back to ChurnNote delivery and is logged
Permissions you grant
- SMTP host, port and security mode (SSL, STARTTLS or none)
- SMTP username and password
- The From name and From address you want customers to see
Setup
- 1Open Settings → Email sending and choose Custom SMTP
- 2Enter your server details and the address you want to send from
- 3Send the test email. Custom SMTP stays inactive until that test passes
- 4Once verified, every customer email goes out through your server
Security and key storage
- Your SMTP password is encrypted at rest and never displayed again
- Credentials are excluded from your data export and deleted with your account
- If your server rejects a send, ChurnNote falls back to its own delivery so the customer email is not lost, and records which transport was used
What this unlocks
- Customer email that comes from your domain, not a shared sending domain
- Your existing deliverability and sender reputation
Questions
If email sends from my domain, where do replies go?
Reply-To is always a ChurnNote inbound address, on every transport. That is what captures the reply, categorises it, and puts it in your dashboard. Changing it would break Reply Intelligence, which is the point of sending at all.
What if my SMTP server goes down?
The send falls back to ChurnNote delivery so the customer still gets the email, and the log records that it fell back.
Start with the free churn scan.
Connect Stripe or Lemon Squeezy and get the report before you pay for anything.
Run my free churn scan