How should 'technical' or transactional emails be implemented.

We are having trouble deciding how we should implement transactional emails in our solutions. For example emails like the forgot password, for completing a registration or for an order on the website.

Currently we are overseeing the following two options:

  1. Sending with emails configured in the email channel
  2. Sending from within code

Both I think with its own pros and cons. Of course most of them are also debatable.

Email channel In code
Easily editable by content editors ✅ ❌
Easily controllable by developers ❌ ✅
Dedicated (non internal) API in Kentico ❌ ✅
Reuse of components between marketing and transactional emails ✅ ❌
Open and clicking tracking ✅ ❌
Reuse of the same sender and delivery settings between marketing and transactional emails ✅ ❌
Easiliy use dynamic data ❌ ✅
Versioning ❌ ✅
Not necessarily tied to contacts ❌ ✅
No additional license requirement (?) ❌ ✅

We also have found out that in the SaaS environment there isn't the possibility to have the same email domain as system domain and as channel domain. See point 5: (https://docs.kentico.com/documentation/developers-and-admins/configuration/email-configuration#custom-system-email-domains-in-the-saas-environment) That makes it not possible to use your website address e.g. kentico.com as your email domain that you can use for sending emails within code.

What are you using as the way to send this kind of transactional emails? What are your experiences?

Answers

I prefer channel managed emails for anything that is customer facing. These emails are content and fall under the ownership of marketers.

In the Kentico Community Portal, I've been using the .Internal APIs to programmatically send email channel-managed emails for several years now. Those APIs did change slightly when the Email Builder was introduced but I never lost the capability.

If those APIs were made internal, I'd be in a tough spot and have to have an agent refactor to code-managed emails (trying to use most of the Email Builder Razor component code if possible).

I don't fault you for your concern about using .Internal APIs - they definitely aren't supported and can be removed outside of major version changes.

There is another option - developer authored emails which pull in specific reusable content items to give marketers control over the messaging.

You could build an admin UI extension that renders these emails in the admin, pulling in the preview content items so that marketers have a preview of the email before publishing their content changes.

If these emails are truly transactional, then marketers won't need to restructure their layout - it's mostly about header, footer and some body content, while most of the body is dynamic and contextual to the recipient.


Re: SaaS limitation on domains

Unless I'm misunderstanding, I don't think this is true. The Kentico Community Portal runs in a standard SaaS environment and has the following domains:

Email channel
Service domain: domain which serves Content hub images in emails and executes link click tracking before redirecting to the destination URL. community.kentico.com
Sending domain: domain of the sending email address - relevant for domain reputation and deliverability. community.kentico.com
Website channel
Custom domain: the domain all visitors access the website channel from (language-specific domains are not yet supported in SaaS as of October 2026) community.kentico.com

Channel domains (email and web) are different than system domains. System domains (sending and service) are used for email notifications to marketers using the admin, because the /admin app is not a channel. The admin can be accessed over any channel domain, but it's a best practice to give it a separate domain and use that: e.g. admin.yoursite.com.

Channel domains are what your audience sees.

Thanks for your response Sean. Good thing to take into consideration. The additional options is also a good one to consider.


Regarding the SaaS domains, I have already had contact with support. I don't know how it works exactly and what the exact problem is, but it seems that the way of sending emails in code that we use that we needed a system sending domain and there comes the issue that it isn't possible to have the system domain the same as the main channel domain. It then gives back the following error: "The domain could not be created. This domain name is not available."

Have you considered using the content hub and a content types feeding code? Components can be reused between channel and transaction and updated by GUI users.


We have made an email workspace that has four relevant content types in our accelerator.

email header (background image, alt text, anchor hyperlink list (rich text list)), date, tags)
email footer (background image, alt text, Text column 1, column 2 and column 3 (rich text list)), date, tags)

email image (because any images in email need not to be edited ever once they are sent). In future I would love it if email images can be cloned but not edited EVER once published. Fastest way to break emails out there in the wild.

email content body.

These objects are then called by the code in transactional email code and compiled.

This is the best balance in my opinion of authorability and maintainability by producers and clients for clients that dont have an email channel.

If they have a channel then i would use that every day of the week, but still keep these objects in the content hub except for the body text, you should build channel layout widgets for that.

To response this discussion, you have to login first.