Content of this article
- Preliminary remarks
- Activate the settings on the client level
- Overview of the system mails
1. Preliminary remarks
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
System mail |
Information |
Change of payment method |
Trigger: possible sources: |
Confirmation of cancellation reversal |
Trigger: possible sources: |
Email already used for registration |
Trigger: possible source: |
Email change confirmation |
Trigger: Data: possible source: |
Invitation to a multi user offer |
Trigger: Data: possible sources: |
Invoice |
Trigger: Data:
*: 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: |
Notification of a failed payment attempt |
Trigger: possible source: |
Notification of a failed recurring payment |
Trigger: possible source: |
Offer change due to sales-based rule |
Trigger: possible source: |
Order |
Trigger:
Data: contains PDF order confimation possible sources: |
Payment failed notification |
Trigger: possible source: |
Purchase in a cross sell |
Trigger: possible source: |
Registration completion |
Trigger: Data: possible source: |
Registration confirmation |
Trigger: possible source: |
Reset password |
Trigger: Data: contains a security token (valid: 15 minutes) possible source: |
Reset passwort confirmation |
Trigger: possible source: |
Subscription cancellation confirmation |
Trigger: possible sources: |
Subscription delivery pause was ended |
Trigger: possible sources: |
Subscription delivery was paused |
Trigger: possible sources: |
Subscription pause ended |
Trigger: possible sources: |
Subscription paused |
Trigger: Time: possible sources: |
Voucher purchase |
Trigger: Data: possible sources: |
Welcome email for customers created via the merchant backend |
Trigger: possible source: |