Preliminary Remarks
By default, the e-mail templates are managed by the contracting company.

It is possible to make the settings for e-mail templates individually for the client. Various system mails are available in the Frisbii Media System for automated and manual dispatch to end customers. Individual system mails that are not required can be deactivated. The content and design of the e-mails can be customized.
If no adjustments are made, the system sends a standardized template that automatically adopts the company data.
Note: If an external SSO is used for customer management, certain templates are not sent via the Frisbii Media System and should therefore be implemented externally. These are all templates that are created via the SSO source.
Activate settings at client level
Settings tab
Click on Edit.
Set slider Use these settings instead of holding settings to active.
Set the slider Activate this email setup to active to be able to make settings.
Send BCC mails to the following address can be filled in optionally.
Different recipient addresses can be entered individually for each system e-mail in the table.
Manage PDF attachments tab
Click on Edit.
Set slider Use these settings instead of holding settings to active.
Uncheck/check which PDF is to be attached at private customer and business customer level.
Define sender address
Under “Other Settings,” you can specify which sender email address to use. Frisbii Media offers three types of email delivery:
We also recommend limiting the sending of test emails in the staging environment to a specific recipient email domain to prevent test emails from being sent to “real” customers.
You can test the technical setup in the action bar by clicking “Test Settings.” The system checks whether the technical requirements for email delegation are correctly configured, particularly DNS and authentication settings such as SPF/DKIM, as well as the relevant connections. However, the test email is not actually sent via your defined email domain or infrastructure; it serves solely to confirm a valid technical configuration. For a complete end-to-end test, an actual email must be sent, e.g., by triggering a test order in the Frisbii Media Stage environment.

Overview of system mails
The table presents the currently available e-mail templates and provides an insight into how they work.
System mail | Information |
Subscription paused | Trigger: Time: Possible sources: |
Subscription cancellation confirmation | Trigger: when the subscription has been canceled Possible sources: |
Subscription pause ended | Trigger: Possible sources: |
Subscription delivery was paused | Trigger: when the function Delivery break has been activated even though the actual date for the delivery break is in the future Possible sources: Merchant Backend & Self Service |
Subscription delivery pause was ended | Trigger: Possible sources: |
Offer change due to cross-selling | Trigger: if an offer has been terminated through the use of cross-selling Possible source: |
Registration confirmation | Trigger: when the registration process has been successfully completed Possible source: |
Payment failed notification | Trigger: Possible source: |
Notification of a failed recurring payment | Trigger: Possible source: |
Notification of a failed payment attempt | Trigger: Possible source: |
E-Mail already used for registration | Trigger: Possible source: |
Order | Trigger:
Data: includes PDF order confirmation Possible sources: |
Confirmation of cancellation reversal | Trigger: Possible sources: |
Reset password confirmation | Trigger: Possible source: |
Email change confirmation | Trigger: Data: Possible source: |
Invitation to a multi-user offer | Trigger: Data: Possible sources: |
Voucher purchase | Trigger: Data: Possible sources: |
Purchase through up/down-selling | Trigger: Possible source: |
Reset password | Trigger: Data: Possible source: |
Invoice | Trigger: Data:
*: The "Order" mail template is not sent for an order that results in an invoice upon completion. Possible sources: |
Registration completion | Trigger: when the registration process has been started Data: Possible source: |
Welcome email for customers created via the merchant backend | Trigger: if a customer was created manually via the Merchant Backend Possible source: |
Change of payment method | Trigger: Possible sources: |
Multiuser Added User (new feature version) | Trigger: when an existing user account is added to a subscription. Possible sources: Merchant Backend |
Multiuser Invitation (new feature version) | Trigger: when a new customer (unknown to the system) is invited to use a subscription. Possible sources: Merchant Backend & Self Service |