Introduction to V4 Email Content Management
Instead of customizing native TIXNGO Emails content directly from the Multilingual screen, content will now be managed from the Communication Templates dedicated Email’s screen.
New Email templates list view
Overview
The list of the default Email Templates will be now visible in the Email tab.
Closer look on an Email template row
To ease understanding during template’s customization Email Templates are now supporting extra contextual information.
Email template | Breakdown | Description |
|---|---|---|
 | Email sent to the ticket owner when a ticket has been deleted. | User-friendly description of the email’s purpose. |
email.ticket.deleted | Standardized email template key following the | |
 | Ticket Transfer | Straight to the point Context of the email. |
 | DEFAULT | Audience targeted by this e-mail template, here DEFAULT. This column may contain other values (defined by the organizer), if the “Audience-based emails” ticket.email.custom feature is enabled. |
New V4 Emails Templates
We leveraged the new communication engine in V4 to rename template keys and streamline email configuration by reducing the number of templates.
Context | V3 Email Template Key | V4 Email Template Key | V4 Audience-based Email Support |
|---|---|---|---|
Email sent at ticket injection | email.invitation.inject | email.ticket.injected | Yes |
Email sent at ticket deletion | email.delete | email.ticket.deleted | Yes |
Email sent at ticket transfer to Known account | email.information.approval | email.ticket.transfer.initiated | Yes |
Email sent at ticket transfer to Unknown account | email.invitation.approval | email.ticket.transfer.initiated.unknown | Yes |
Email sent to recipient when a transfer is automatically cancelled by the system | email.information.automaticallycancel.recipient | email.ticket.transfer.autocancelled.recipient | Yes |
Email sent to sender when transfer is automatically cancelled by the system | email.information.automaticallycancel.sender | email.ticket.transfer.autocancelled.sender | Yes |
Email sent to recipient when a transfer is cancelled by sender | email.information.cancel | email.ticket.transfer.cancelled | Yes |
Email sent to sender after a successful/accepted transfer | email.sent | email.ticket.transfer.accepted | Yes |
Reminder Email when the user did not sign-up yet | email.reminder | email.ticket.signup.reminder | Yes |
Email sent to recipient when ticket transfer to Known account | email.information.bulk.approval | Not existing anymore in V4. Thanks to the new Transfer Group concept, we will use only one email template email.ticket.transfer.initiated for single or multiple ticket transfer. | N/A |
Email sent to recipient when ticket transfer to Unknown account | email.invitation.bulk.approval | Not existing anymore in V4. Thanks to the new Transfer Group concept, we will use email.ticket.transfer.initiated.unknown for single or multiple ticket transfer. | N/A |
Email sent to recipient when transfer is cancelled by sender | email.information.bulk.cancel | Not existing anymore in V4. Thanks to the new Transfer Group concept, we will use email.ticket.transfer.autocancelled.recipient for single or multiple ticket transfer cancellation. | N/A |
Email sent to sender after a successful/accepted transfer | email.sent.sender.bulk | Not existing anymore in V4. Thanks to the new Transfer Group concept, we will use email.ticket.transfer.accepted for single or multiple ticket transfer acceptance. | N/A |
Email sent to spectator for account deletion confirmation If the email address has valid future mobile tickets (the confirmation link is valid for 24 hours) | email.account.deletion.confirmation | email.spectator.deletion.confirmation | No |
Email sent to spectator to confirm that their account has been deleted | email.account.deleted | email.spectator.deletion.completed | No |
Email sent to spectator to obtain the registration or login pincode | email.spectator.activation | email.spectator.pincode | No |
Email sent to spectator to obtain the registration or login pincode | email.spectator.activation.notickets | email.spectator.pincode.without.tickets | No |
Create Email Template
ONLY available if the “Audience-based emails” (ticket.email.custom) feature is enabled.
Click the button 
A new popup appears, to allow you to select the base of the Email Template to be copied, in order to customize it for a specific audience.
Select a Template Key from the list and click “Add template” button
You’ll be redirected to the “New email template” screen containing a clone of the DEFAULT email template and create a new one for the Audience.
From this screen, you
must define an Audience name (to be reused against multiple templates)
can customize the Email subject and/or body to suit your needs.
can manage directly translation of this Email Template by Adding a language and customizing the Email subject and/or body to suit your needs.
Edit Email Template
By clicking on the inline Edit button of an existing template, you’ll be redirected to a new dedicated screen to edit your Email Template.
From this screen, you can either :
Button | Action |
|---|---|
| Edit the template for a specific language |
| Preview the template for a specific language |
| Add a new language and customize the template |
New Variables for Email templates
We leveraged the new communication engine in V4 to
provide a consistent naming convention for Variables used in Emails & Standard Push Notifications
provide a consistent set of Variables used in Emails & Standard Push Notifications
Ticket injection
Type | Template key | Supported Variables |
|---|---|---|
email.ticket.injected |
Keys to display a list of tickets ticket.list , table with these information
| |
PUSH | push.ticket.injected |
|
© TIXNGO 2023 - Login