Mail Settings

    Content of this article

    1. Preliminary remarks
    2. Activate the settings on the client level
    3. Overview of the system mails

    1. Preliminary remarks

    Mail templates are managed in the contracting company by default.

    It is possible to make the settings for mail templates in the client's Backend independently from the contracting company.
    In the plenigo system, various system mails are available for the automated and manual mail delivery to end customers. Individual system mails that are not required can be deactivated. The content and the design of the e-mails can be customized.
    If no adjustments are made, the system sends a standardized template which automatically adopts the company data.

    Note: If an external SSO is used for customer management, certain templates are not sent via the plenigo system and should therefore be implemented externally. These are all templates which are created via the source SSO.

    2. Activate the settings on the client level

    Tab Settings

    • Click on Edit.
    • Set the 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 mail to the following address can be filled in optionally.
      Different recipient addresses can be entered individually for each system e-mail in the table.

    Tab Manage PDF Attachments

    • Click on Edit.
    • Set slider Use these settings instead of holding settings to active.
    • Remove or set checkmark to set which PDF should be attached to private customer and company level.

    Test settings

    • Click on Test Settings in the action bar.


    • Enter the e-mail address to which the test mail should be sent.

    3. Overview of the system mails

    This table shows all currently available e-mail templates and provides an insight into how they work.

    System mail

    Information

    Change of payment method

    Trigger:
    when a new payment method is entered in the customer account

    possible sources:
    Merchant Backend & Self Service

    Confirmation of cancellation reversal

    Trigger:
    when a cancelation is withdrawn before the end of the current subscription interval

    possible sources:
    Merchant Backend & Self Service

    Email already used for registration

    Trigger:
    when an e-mail address already in the system is used for the registration

    possible source:
    SSO

    Email change confirmation 

    Trigger:
    when the process for changing an already existing e-mail address has been started

    Data:
    contains a security token

    possible source:
    Self Service

    Invitation to a multi user offer

    Trigger:
    when multi user access data has been sent to user

    Data:
    contains an invitation code

    possible sources:
    Merchant Backend & Self Service

    Invoice

    Trigger:
    after a successfully completed recurring payment

    Data:

    • contains PDF invoice
    • contains PDF order confirmation*

    *: In the case of an order that results in an invoice upon completion, the “Order” mail template is not sent.

    Instead, the “Invoice” mail template is sent and in this case contains both the PDF order confirmation and the PDF invoice.


    possible sources:
    Merchant Backend, Checkout & System

    Notification of a failed payment attempt

    Trigger:
    after every individual failed payment attempt in one accounting period

    possible source:
    System

    Notification of  a failed recurring payment

    Trigger:
    when all payment attempts within one accounting period have failed

    possible source:
    System

    Offer change due to sales-based rule

    Trigger:
    when an offer has been ended by using a sales-based rule

    possible source:
    Checkout

    Order

    Trigger:
    after a successfully made order, which

    • triggers no invoice or
    • contains free products

    Data:

    contains PDF order confimation 

    possible sources:
    Merchant Backend & Checkout

    Payment failed notification

    Trigger:
    when a customer actively withdraws a successfully completed payment or any comparable situation

    possible source:
    System

    Purchase in a cross sell

    Trigger:
    when an offer has been ordered through a cross sell

    possible source:
    Checkout

    Registration completion

    Trigger:
    when the registration process has been started

    Data:
    contains a security token (valid: 1 day)

    possible source:
    SSO

    Registration confirmation

    Trigger:
    when the registration process has been sucessfully completed

    possible source:
    SSO

    Reset password

    Trigger:
    when the forgot-password process has been started

    Data:

    contains a security token (valid: 15 minutes)

    possible source:
    SSO

    Reset passwort confirmation

    Trigger:
    when the password has successfully been reset and the forgot-password process has been completed

    possible source:
    SSO

    Subscription cancellation confirmation

    Trigger:
    when the subscription has been canceled

    possible sources:
    Merchant Backend & Self Service

    Subscription delivery pause was ended

    Trigger:
    when the function Delivery break has been deactivated

    possible sources:
    Merchant Backend & Self Service

    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 pause ended

    Trigger:
    when the function Pause subscription has ben deactivated

    possible sources:
    Merchant Backend & Self Service

    Subscription paused

    Trigger:
    when the function Pause subscription has been activated

    Time:
    when the pause is set even though the actual date for the pause is in the future

    possible sources:
    Merchant Backend & Self Service

    Voucher purchase

    Trigger:
    when a voucher offer has been purchased

    Data:
    contains a PDF voucher

    possible sources:
    Checkout & Merchant Backend

    Welcome email for customers created via the merchant backend

    Trigger:
    when a customer has been created manually in the Merchant Backend

    possible source:
    Merchant Backend
    Published