The Sleekplan app sends different types of emails that are important for the general functioning of the app.
If those messages land in spam – or don’t arrive at all – users get stuck, churn increases, and important user engagement could be lost.
That’s why Sleekplan is built on top of modern email authentication standards (SPF, DKIM, and DMARC via our provider Amazon SES). These standards help prove that:
The email really comes from your product,
The content hasn’t been tampered with, and
Inbox providers like Gmail or Outlook can trust and deliver it.
📋Types of emails Sleekplan sends
Sleekplan can send emails such as:
Authorization / login codes – for secure sign‑in to your workspace or customer portals.
Feedback notifications – when someone adds new feedback on a board.
Comment notifications – when users or teammates comment on posts.
Vote notifications – so you and your users know when ideas are gaining traction.
Post creation & status updates – keeping everyone in the loop when new ideas are created or moved through your roadmap.
Changelog & announcement emails – to broadcast product updates to your audience.
Admin & team invitations – so new team members can join your workspace quickly and securely.
All of these emails are transactional and directly tied to user activity, which inbox providers tend to treat more favorably when properly authenticated.
ℹ️How Sleekplan complies with email deliverability
When Sleekplan sends an email , several things happen in the background:
👉SPF – proving the sending server is allowed
Sleekplan uses Amazon SES to send mail. The domain’s SPF record includes Amazon SES ( include:amazonses.com ), which tells inbox providers:
“Amazon SES servers are allowed to send email for this domain.”
This helps prevent spoofing and tells providers that emails coming from SES IPs are legitimate for Sleekplan.
👉DKIM – proving the message wasn’t altered
Every outgoing Sleekplan email is signed with DKIM (DomainKeys Identified Mail).
By default, Sleekplan uses an address like: your_product_name@mail.sleekplan.com to send outgoing emails for your product. Sleekplan’s DKIM signature uses a key hosted under that domain.
Inbox providers verify that signature against the public key stored in DNS. If it matches, they know:
the message really came from Sleekplan
the content wasn’t modified in transit.
🔑Because the DKIM domain is aligned with the visible From: address (e.g., …@mail.sleekplan.com ), this is a strong positive signal for modern DMARC checks and for overall deliverability.
You can optionally use your own brand email address (for example updates@yourdomain.com ) so your users see your domain as the sender.
The DKIM signature also uses a key hosted under that custom domain. In this case, the user just needs to add the CNAME DKIM records provided by Sleekplan to their DNS provider (Setting up a custom email sending domain).
👉DMARC – policy at the organizational domain
Sleekplan also publishes a DMARC record at the organizational domain ( sleekplan.com ) to monitor authentication results and collect reports from providers. This helps us keep an eye on authentication health, spot potential abuse, and continuously improve deliverability over time.
🔗Putting it all together:
✅More emails land in the inbox Proper SPF and DKIM (and DMARC monitoring) significantly reduce the chance that important Sleekplan emails end up in spam.
✅Stronger trust with your users When login codes, notifications, and invites consistently come from a recognizable domain, users are less likely to ignore or mistrust them.
✅Brand consistency Using a custom sender address means every notification, changelog, and feedback update reinforces your brand – not just Sleekplan’s default domain.
✅Security and integrity DKIM ensures that critical messages like authorization codes and admin invites can’t be silently modified in transit without detection.