Send through your own email domain (SMTP)
Five fields and a test send, and every email HoldFast sends for you arrives from your address instead of ours.
An email from your own domain gets opened; an email from a platform nobody at the client recognizes gets squinted at. SMTP setup points every email HoldFast sends (invites, notifications, outreach sends) through your server, from your address.
Configure it
In Settings, open the SMTP section and fill five fields: host, port, username, password, and the From address. Your email provider publishes the first four (search "your-provider SMTP settings"); the From address is who your recipients will see.
Test it
Use the test email button before trusting it with a real send. A test that arrives is a configuration that works; a test that does not usually means a wrong port or an app-specific password requirement at your provider.
What is protected
Credentials are encrypted at rest and decrypted only at send time. And nothing breaks without SMTP: HoldFast falls back to its platform default sender, so email always flows. Your domain is the deliverability and trust upgrade, not a dependency.
With the sender sorted, the templates control what the messages say, and tracking tells you honestly what happened after send.
Questions
Are my SMTP credentials safe?
They are stored encrypted at rest. HoldFast decrypts them only at send time.
What happens if I do not configure SMTP?
Everything still works: HoldFast sends through its platform default. Your own domain is better for recipient trust and deliverability, but it is an upgrade, not a requirement.
Ready to try it?
Host video, collect frame-accurate review, and see who's watching. Free to start.
Start free