...
Reminder - TIXNGO - $$event.name$$ - Mobile ticket(s) available.
...
Dear Sir or Madam,
Thank you for choosing TIXNGO.
Your mobile ticket(s) for "$$event.name$$" is/are still waiting.
To download them and to be able to use them, please follow the instructions below:
- Using your mobile phone, click HERE to download the $$app.name$$ mobile app
- Open the $$app.name$$ app and Sign-up/Sign-in using your email address : $$spectator.email$$
- After your registration, your tickets will appear on your $$app.name$$ mobile app
We look forward to seeing you during "$$event.name$$" event.
Thank you,
The TIXNGO Team
https://www.tixngo.io
...
Event | $$event.name$$ |
Ticket ID | $$ticket.id$$ |
Email Address | $$spectator.email$$ |
**********************************************
You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application.
Dear Sir or Madam,
Thank you for choosing TIXNGO.
Your mobile ticket(s) for "Event A" is/are still waiting.
To download them and to be able to use them, please follow the instructions below:
- Using your mobile phone, click HERE to download the TIXNGO mobile app
- Open the TIXNGO app and Sign-up/Sign-in using your email address : user-a@yopmail.com
- After your registration, your tickets will appear on your TIXNGO mobile app
We look forward to seeing you during "Event A" event.
Thank you,
The TIXNGO Team
https://www.tixngo.io
Ticket Details
Event | Event A |
Ticket ID | 20210630 |
Email Address | user-a@yopmail.com |
**********************************************
You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application.
...
- Triggered when an Organizer deletes a ticket that
belongs to a Spectator. - Triggered as the same time as the Deletion.
...
Hello,
Your ticket was deleted.
The TIXNGO Team
[ticket id : 20210630]
...
- Triggered when the reciever opens the app and finalize
the transfer. - Triggered as the same time as the Transfer finalizes.
...
$$app.name$$ - Your ticket(s) was delivered
...
Email sent to spectator when he or she is using pin code to login
- Triggered at login time, and this account not yet have a ticket in wallet
...
Registration code
$$spectator.email$$
$$spectator.invitCode$$
Hello,
Thank you for downloading the $$Mobile Tickets App name$$.
Currently, there are no tickets associated to this e-mail address.
Double check your e-mail address
Please check you are using the same e-mail address which you used to purchase your tickets.
Yours sincerely,
$$organizer.name$$
...
Email sent to spectator when he or she is using pin code to login
- Triggered at login time, and this account already have at least 1 ticket in wallet
...
Your ticket was successfully transferred to $$spectator.name$$
...
You received a ticket from $$spectator.name$$ to attend "$$event.name$$" event.
...
Here is the list of default email and push notification templates
...
Email sent at ticket injection
- Triggered when a new ticket is injected to a spectator.
If more than one ticket is injected, only send one email. - A job is running on the backend to trigger emails for
newly injected tickets, every 2mn.
...
Dear Sir or Madam,
Thank you for choosing TIXNGO.
Your mobile ticket(s) for "$$event.name$$" is/are now available.
To download them and to be able to use them, please follow the instructions below:
- Using your mobile phone, click HERE to download the $$app.name$$ mobile app
- Open the $$app.name$$ app and Sign-up/Sign-in using your email address : $$spectator.email$$
- After your registration, your tickets will appear on your $$app.name$$ mobile app
We look forward to seeing you during "$$event.name$$" event.
Thank you,
The TIXNGO Team
https://www.tixngo.io
...
Event | $$event.name$$ |
Ticket ID | $$ticket.id$$ |
Email Address | $$spectator.email$$ |
**********************************************
You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application.
Dear Sir or Madam,
Thank you for choosing TIXNGO.
Your mobile ticket(s) for "ATLAS GLOBAL" is/are now available.
To download them and to be able to use them, please follow the instructions below:
- Using your mobile phone, click HERE to download the TIXNGO mobile app
- Open the TIXNGO app and Sign-up/Sign-in using your email address : user-a@yopmail.com
- After your registration, your tickets will appear on your TIXNGO mobile app
We look forward to seeing you during "ATLAS GLOBAL" event.
Thank you,
The TIXNGO Team
Ticket Details
Event | ATLAS GLOBAL |
Ticket ID | 20210710 |
Email Address | user-a@yopmail.com |
**********************************************
You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application.
...
- Triggered when a Spectator transfers a ticket to another
person (email address) who is not yet registered in the
app. - Triggered as the same time as the Transfer.
...
Dear Sir or Madam,
$$spectator.name$$ ($$sender.email$$) has transferred you a mobile ticket for "$$event.name$$".
To download it and to be able to use it, please follow the instructions below:
- Using your mobile phone, click HERE to download the $$app.name$$ mobile app
- Open the $$app.name$$ app and Sign-up/Sign-in using your email address : $$spectator.email$$
- After your registration, your tickets will appear on your $$app.name$$ mobile app
We look forward to seeing you during "$$event.name$$" event on $$event.date$$.
Thank you,
The TIXNGO Team
https://www.tixngo.io
...
Event | $$event.name$$ |
Ticket ID | $$ticket.id$$ |
Email Address | $$spectator.email$$ |
**********************************************
You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application.
Dear Sir or Madam,
User A (user-a@yopmail.com) has transferred you a mobile ticket for "Event A".
To download it and to be able to use it, please follow the instructions below:
- Using your mobile phone, click HERE to download the TIXNGO mobile app
- Open the TIXNGO app and Sign-up/Sign-in using your email address : user-a@yopmail.com
- After your registration, your tickets will appear on your TIXNGO mobile app
We look forward to seeing you during "Event A" event on 2023-05-31 07:25:00.
Thank you,
The TIXNGO Team
https://www.tixngo.io
Ticket Details
Event | Event A |
Ticket ID | 20210630 |
Email Address | user-a@yopmail.com |
**********************************************
You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application.
...
- Triggered when a Spectator transfers a ticket to another
Spectator (registered in the system) - Triggered as the same time as the Transfer.
...
Dear Sir or Madam,
$$spectator.name$$ ($$sender.email$$) has transferred you a mobile ticket for "$$event.name$$".
To download it and to be able to use it, please follow the instructions below:
- Using your mobile phone, click HERE to download the $$app.name$$ mobile app
- Open the $$app.name$$ app and Sign-up/Sign-in using your email address : $$spectator.email$$
- After your registration, your tickets will appear on your $$app.name$$ mobile app
We look forward to seeing you during "$$event.name$$" event on $$event.date$$.
Thank you,
The TIXNGO Team
https://www.tixngo.io
...
Event | $$event.name$$ |
Ticket ID | $$ticket.id$$ |
Email Address | $$spectator.email$$ |
**********************************************
You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application.
Dear Sir or Madam,
Moda Yoki (moda.yoki@yopmail.com) has transferred you a mobile ticket for "Event A".
To download it and to be able to use it, please follow the instructions below:
- Using your mobile phone, click HERE to download the TIXNGO mobile app
- Open the TIXNGO app and Sign-up/Sign-in using your email address : user-a@yopmail.com
- After your registration, your tickets will appear on your TIXNGO mobile app
We look forward to seeing you during "Event A" event on 2023-05-31 07:25:00.
Thank you,
The TIXNGO Team
https://www.tixngo.io
Ticket Details
Event | Event A |
Ticket ID | 20210630 |
Email Address | user-a@yopmail.com |
**********************************************
You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application.
...
Email sent at ticket transfer cancel
- Triggered when a Spectator cancels a ticket Transfer he
previously transferred to someone else. - Triggered as the same time as the Cancellation.
- For automatically canceled: Triggered when the time in Admin tool >> Organizer settings >> Amount of time (hour) after which the pending transfers... has been reached.
...
$$app.name$$ - $$event.name$$ - Mobile ticket transfer cancelled.
...
Dear Sir or Madam,
$$spectator.name$$ has cancelled the transfer of the mobile ticket for $$event.name$$
Thank you,
The TIXNGO Team
https://www.tixngo.io
...
Event | $$event.name$$ |
Ticket ID | $$ticket.id$$ |
Email Address | $$spectator.email$$ |
Dear Sir or Madam,
Moda Yoki has cancelled the transfer of the mobile ticket for Event A
Thank you,
The TIXNGO Team
https://www.tixngo.io
Ticket Details
Event | Event A |
Ticket ID | 20210630 |
Email Address | user-a@yopmail.com |
...
Dear Sir or Madam,
$$spectator.name$$ has cancelled the transfer of the mobile ticket for $$event.name$$
Thank you,
The TIXNGO Team
Ticket Details
Event | $$event.name$$ |
Ticket ID | $$ticket.id$$ |
Email Address | $$spectator.email$$ |
Dear Sir or Madam,
User B has cancelled the transfer of the mobile ticket for Event A
Thank you,
The TIXNGO Team
https://www.tixngo.io
Ticket Details
Event | Event A |
Ticket ID | 20210630 |
Email Address | user-a@yopmail.com |
...
Dear Sir or Madam,
Please be informed that the transfer of the ticket $$ticket.id$$ was canceled, because $$ticket.approval.cancel.delay$$ hours have passed without any response from recipients.
Ticket Details
Event | $$event.name$$ |
Event date | $$event.date$$ |
Ticket Id | $$ticket.id$$ |
$$ticket.details.main$$
Thank you,
$$organizer.name$$
Dear Sir or Madam,
Please be informed that the transfer of the ticket E0000001 was canceled, because 5 hours have passed without any response from recipients.
Ticket Details
Event | Event A |
Event date | 2022-09-16 18:00:00 |
Ticket Id | E0000001 |
Gate | D |
Block | 4 |
Row | 7 |
Seat | 2009 |
Gate open | 5:00 PM |
Opening Ceremony | 7:00 PM |
...
- Reminder email are triggers when a user who purchased
tickets did not sign-up in the app yet. - A backend job is running every hour to check for tickets
that would require a reminder. - Maximum number of reminder, interval between two
reminder, how long before the event to send a reminder
and time at which we should send reminder are
configurable in the TIXNGO Console.
Here is the list of default email and push notification templates
Table of Contents |
---|
Notification & Email templates
No | Description | Key | Value | Example | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Email sent at ticket injection
| email.invitation.inject.subject | $$event.name$$ - Mobile ticket(s) available | ATLAS GLOBAL - Mobile ticket(s) available. | ||||||||||||||||||||||
email.invitation.inject.body | Dear Sir or Madam, Thank you for choosing TIXNGO.
We look forward to seeing you during "$$event.name$$" event. Thank you,
********************************************** You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application. | Dear Sir or Madam, Thank you for choosing TIXNGO. Your mobile ticket(s) for "ATLAS GLOBAL" is/are now available. To download them and to be able to use them, please follow the instructions below:
We look forward to seeing you during "ATLAS GLOBAL" event. Thank you, The TIXNGO Team Ticket Details
********************************************** You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application. | ||||||||||||||||||||||||
2 | Email sent at ticket transfer to Unknown account
| email.invitation.approval.subject | $$app.name$$ - $$event.name$$ - Mobile ticket(s) transfer | TIXNGO - Event A - Mobile ticket(s) available. | ||||||||||||||||||||||
email.invitation.approval.body | Dear Sir or Madam, $$spectator.name$$ ($$sender.email$$) has transferred you a mobile ticket for "$$event.name$$".
We look forward to seeing you during "$$event.name$$" event on $$event.date$$. Thank you,
********************************************** You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application. | Dear Sir or Madam, User A (user-a@yopmail.com) has transferred you a mobile ticket for "Event A".
We look forward to seeing you during "Event A" event on 2023-05-31 07:25:00. Thank you,
********************************************** You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application. | ||||||||||||||||||||||||
3 | Email sent to recipient when ticket transfer to Unknown account (single email for bulk tickets) | email.invitation.bulk.approval.subject | $$app.name$$ - You have received $$ticket.quantity$$ mobile ticket(s) from $$sender.name$$ ($$sender.email$$) | TIXNGO - You have received 15 mobile tickets from Moda Yoki (moda.yoki@yopmail.com) | ||||||||||||||||||||||
email.invitation.bulk.approval.body | Dear Sir or Madam,
We look forward to seeing you on:
Thank you, | Dear Sir or Madam, We are pleased to inform you that Moda Yoki (moda.yoki@yopmail.com) has transferred you 15 mobile tickets for the following events: To download and use these tickets, please follow the instructions below:
We look forward to seeing you on:
Thank you, | ||||||||||||||||||||||||
4 | Email sent at ticket transfer to Known account
| email.information.approval.subject | $$app.name$$ - $$event.name$$ - Mobile ticket(s) transfer | TIXNGO - Event A - Mobile ticket(s) available. | ||||||||||||||||||||||
email.information.approval.body | Dear Sir or Madam, $$spectator.name$$ ($$sender.email$$) has transferred you a mobile ticket for "$$event.name$$".
We look forward to seeing you during "$$event.name$$" event on $$event.date$$. Thank you,
********************************************** You received this email because you have purchased one or more tickets and you have chosen to receive them on the TIXNGO mobile application. | Dear Sir or Madam, Moda Yoki (moda.yoki@yopmail.com) has transferred you a mobile ticket for "Event A".
We look forward to seeing you during "Event A" event on 2023-05-31 07:25:00. Thank you,
********************************************** You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application. | ||||||||||||||||||||||||
5 | Email sent to recipient when ticket transfer to Known account (single email for bulk tickets) | email.information.bulk.approval.subject | $$app.name$$ - You have received $$ticket.quantity$$ mobile ticket(s) from $$sender.name$$ ($$sender.email$$) | TIXNGO - You have received 15 mobile tickets from Moda Yoki (moda.yoki@yopmail.com) | ||||||||||||||||||||||
email.information.bulk.approval.body | Dear Sir or Madam,
Thank you, | Dear Sir or Madam, We are pleased to inform you that Moda Yoki (moda.yoki@yopmail.com) has transferred you 15 mobile tickets for the following events: We look forward to seeing you:
Thank you, | ||||||||||||||||||||||||
6 | Email sent at ticket transfer cancel
| email.information.cancel.subject | $$app.name$$ - $$event.name$$ - Mobile ticket transfer cancelled. | TIXNGO - Event A - Mobile ticket transfer cancelled. | ||||||||||||||||||||||
email.information.cancel.body | Dear Sir or Madam, $$spectator.name$$ has cancelled the transfer of the mobile ticket for $$event.name$$ Thank you,
| Dear Sir or Madam, Moda Yoki has cancelled the transfer of the mobile ticket for Event A Thank you,
| ||||||||||||||||||||||||
email.information.automaticallycancel.recipient.subject | $$app.name$$ - $$event.name$$ - Mobile ticket transfer cancelled. | TIXNGO - Event A - Mobile ticket transfer cancelled. | ||||||||||||||||||||||||
email.information.automaticallycancel.recipient.body | Dear Sir or Madam, $$spectator.name$$ has cancelled the transfer of the mobile ticket for $$event.name$$ Thank you, The TIXNGO Team Ticket Details
| Dear Sir or Madam, User B has cancelled the transfer of the mobile ticket for Event A Thank you,
| ||||||||||||||||||||||||
email.information.automaticallycancel.sender.subject | $$app.name$$ - Your ticket transfer for $$event.name$$ is canceled | TIXNGO - Your ticket transfer for Event A is canceled | ||||||||||||||||||||||||
email.information.automaticallycancel.sender.body | Dear Sir or Madam,
$$ticket.details.main$$ | Dear Sir or Madam,
| ||||||||||||||||||||||||
7 | Email sent to recipient when ticket transfer cancel by sender (single email for bulk tickets) | email.information.bulk.cancel.subject | $$app.name$$ - $$sender.email$$ has cancelled the sending of $$ticket.quantity$$ mobile tickets | TIXNGO - Moda Yoki (moda.yoki@yopmail.com) has cancelled the sending of 15 mobile tickets | ||||||||||||||||||||||
email.information.bulk.cancel.body | Dear Sir or Madam,
| Dear Sir or Madam, moda.yoki@yopmail.com has cancelled the transfer of 15 mobile tickets to you as following: Thank you, | ||||||||||||||||||||||||
8 | Ticket sent as reminder (User did not sign-up yet)
| email.reminder.subject | Reminder - TIXNGO - $$event.name$$ - Mobile ticket(s) available. | Reminder - TIXNGO - Event A - Mobile ticket(s) available. | ||||||||||||||||||||||
email.reminder.body | Dear Sir or Madam, Thank you for choosing TIXNGO.
We look forward to seeing you during "$$event.name$$" event. Thank you,
********************************************** You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application. | Dear Sir or Madam, Thank you for choosing TIXNGO.
We look forward to seeing you during "Event A" event. Thank you, Ticket Details
********************************************** You received this email because you have purchased one or more tickets and youhave chosen to receive them on the TIXNGO mobile application. | ||||||||||||||||||||||||
9 | Email sent at ticket deletion
| email.delete.subject | $$app.name$$ - Your ticket(s) was deleted | TIXNGO - Your ticket(s) was deleted | ||||||||||||||||||||||
email.delete.body | Hello, | Hello, Your ticket was deleted. The TIXNGO Team [ticket id : 20210630] | ||||||||||||||||||||||||
10 | Email sent at ticket transfer delivered (to Sender)
| email.sent.subject | $$app.name$$ - Your ticket(s) was delivered | TIXNGO - Your ticket(s) was delivered to original ticket owner | ||||||||||||||||||||||
email.sent.body | Dear Sir or Madam! | Dear Sir or Madam! Please be informed that the ticket below were successfully delivered: The person who received ticket (User A, user-a@yopmail.com) Match Event A and date of the match (2023-05-31 07:25:00) Ticket and seating details: - Ticket Id: 20210630 - Block: 1 | ||||||||||||||||||||||||
11 | Email sent to sender when ticket transfer delivered successfully (single email for bulk tickets) | email.sent.sender.bulk.subject | $$app.name$$ - Your mobile ticket(s) have been successfully delivered to $$receiver.name$$ ($$receiver.email$$) | TIXNGO - Your mobile ticket(s) have been successfully delivered to User A (user-a@yopmail.com) | ||||||||||||||||||||||
email.sent.sender.bulk.body | Dear Sir or Madam,
| Dear Sir or Madam! Please be informed that 15 mobile tickets have been successfully delivered to User A (user-a@yopmail.com) Thank you, | ||||||||||||||||||||||||
12 | Email sent to spectator when he or she is using pin code to login
| email.account.activation.noticket.subject | Your registration code $$spectator.invitCode$$ | Your registration code 215391 | ||||||||||||||||||||||
email.account.activation.noticket.body | Registration code | Registration code sample@tixngo.io 215391 Hello, Thank you for downloading the TIXNGO Tickets App. Currently, there are no tickets associated to this e-mail address. Double check your e-mail address Please check you are using the same e-mail address which you used to purchase your tickets. Yours sincerely, TIXNGO Team | ||||||||||||||||||||||||
13 | Email sent to spectator when he or she is using pin code to login
| email.account.activation.subject | Your registration code $$spectator.invitCode$$ | Your registration code 542214 | ||||||||||||||||||||||
email.account.activation.body | Registration code $$spectator.email$$ $$spectator.invitCode$$ Enter $$spectator.invitCode$$ on the App followed by your personal details to see your tickets. Yours sincerely, $$organizer.name$$ | Registration code sample@tixngo.io 542214 Enter 542214 on the App followed by your personal details to see your tickets. Yours sincerely, TIXNGO Team | ||||||||||||||||||||||||
14 | 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.subject | $$app.name$$ - Delete Account Confirmation | TIXNGO - Delete Account Confirmation | ||||||||||||||||||||||
email.account.deletion.confirmation.body | Dear Sir or Madam, You have chosen to permanently delete your account from [Name of Organizer] secure mobile ticket wallet, including all personal information and mobile tickets. We observed that there are still valid mobile tickets for upcoming events linked to your email address:
Could you please confirm your decision to erase your account, personal data, and mobile tickets? To confirm, click this link within the next 24 hours: Confirm delete account ($$account.deletion.link$$). This action will irreversibly delete your account, all personal data, and mobile tickets associated with your email. If you do not wish to proceed, simply disregard and delete this email. Best, [Name of Organizer] | Dear Sir or Madam, You have chosen to permanently delete your account from [Name of Organizer] secure mobile ticket wallet, including all personal information and mobile tickets. We observed that there are still valid mobile tickets for upcoming events linked to your email address:
Could you please confirm your decision to erase your account, personal data, and mobile tickets? To confirm, click this link within the next 24 hours: Confirm delete account. This action will irreversibly delete your account, all personal data, and mobile tickets associated with your email. If you do not wish to proceed, simply disregard and delete this email. Best, The TIXNGO Team | ||||||||||||||||||||||||
15 | Email sent to spectator to confirm that their account has been deleted for following cases:
| email.account.deleted.subject | $$app.name$$ - Account Deleted - Delete Account Confirmation Account Deletion Confirmed - Your mobile app account has been successfully deleted | TIXNGO - Account Deleted - Delete Account Confirmation Account Deletion Confirmed - Your mobile app account has been successfully deleted | ||||||||||||||||||||||
email.account.deleted.body | Hello, You have chosen to permanently delete your account from [Name of Organizer] secure mobile ticket wallet, including all personal information and mobile tickets. Your account, including all personal data and mobile tickets associated with your email address, has now been permanently deleted. If you wish to use our services again, you may create a new account by signing up for one of the [Name of Organizer] secure mobile ticket wallet. Best, [Name of Organizer] | Hello, You have chosen to permanently delete your account from [Name of Organizer] secure mobile ticket wallet, including all personal information and mobile tickets. Your account, including all personal data and mobile tickets associated with your email address, has now been permanently deleted. If you wish to use our services again, you may create a new account by signing up for one of the [Name of Organizer] secure mobile ticket wallet. Best, TIXNGO Test | ||||||||||||||||||||||||
16 | Notification sent at ticket injection | notification.inject.title | New Ticket | |||||||||||||||||||||||
notification.inject.content | You received a ticket for "$$event.name$$" | |||||||||||||||||||||||||
17 | Notification sent at ticket transfer (to Sender) | notification.sent.title | Ticket Sent | |||||||||||||||||||||||
notification.sent.content | Your ticket was successfully transferred to $$spectator.name$$ | |||||||||||||||||||||||||
18 | Notification sent at ticket transfer (to Recipient) | notification.received.title | New Ticket Received | |||||||||||||||||||||||
notification.received.content | You received a ticket from $$spectator.name$$ to attend "$$event.name$$" event. | |||||||||||||||||||||||||
19 | Notification sent at ticket deletion | notification.deleted.title | Ticket deleted | |||||||||||||||||||||||
notification.deleted.content | A ticket for $$event.name$$ has been deleted | |||||||||||||||||||||||||
20 | Notification sent at ticket activation | notification.activated.title | Ticket activated | |||||||||||||||||||||||
notification.activated.content | A ticket for $$event.name$$ has been activated | |||||||||||||||||||||||||
21 | Notification sent at transfer accepted (to Sender) | notification.acknowledge.accepted.title | Ticket Transfer Accepted | |||||||||||||||||||||||
notification.acknowledge.accepted.content | The ticket's transfer for $$event.name$$ was accepted by $$spectator.name$$ | |||||||||||||||||||||||||
21 | Notification sent at transfer rejected (to Sender) | notification.acknowledge.rejected.title | Ticket Transfer Rejected | |||||||||||||||||||||||
notification.acknowledge.rejected.content | The ticket's transfer for $$event.name$$ was rejected by $$spectator.name$$ | |||||||||||||||||||||||||
23 | Notification sent at ticket update (ex: update event info) | notification.update.ticket.title | Ticket | |||||||||||||||||||||||
notification.update.ticket.content | Your ticket for $$event.name$$ was updated | |||||||||||||||||||||||||
24 | Notification sent at ticket transfer cancelation (to Recipient) | notification.cancel.title | Ticket Transfer Cancelled | |||||||||||||||||||||||
notification.cancel.content | The transfer for a ticket for $$event.name$$ was cancelled | |||||||||||||||||||||||||
25 | Notification sent at mobile app logout:
| notification.logout.title | TIXNGO | |||||||||||||||||||||||
notification.logout.content | You have been successfully logged out. | |||||||||||||||||||||||||
26 | Notification to initiate logout of session:
| notification.logout.force.title | TIXNGO | |||||||||||||||||||||||
notification.logout.force.content | You have logged in with another device. | |||||||||||||||||||||||||
27 | Notification at ticket transfer has been auto canceled | notification.information.automaticallycancel.title | Ticket is canceled | |||||||||||||||||||||||
notification.information.automaticallycancel.content | Your ticket transfer for $$event.name$$ is canceled | |||||||||||||||||||||||||
28 | Push Notifications at delete resale pending
| notification.deleted.resale-pending.title | Ticket available for resale | |||||||||||||||||||||||
notification.deleted.resale-pending.content | The ticket for $$event.name$$ is now available for resale | |||||||||||||||||||||||||
29 | Push Notifications at delete resale cancelled
| notification.deleted.resale-cancelled.title | Ticket deleted | |||||||||||||||||||||||
notification.deleted.resale-cancelled.content | A ticket for $$event.name$$ has been deleted | |||||||||||||||||||||||||
30 | Push Notifications at delete resold
| notification.deleted.resold.title | Ticket deleted | |||||||||||||||||||||||
notification.deleted.resold.content | A ticket for $$event.name$$ has been deleted |
Ticket delete notification
- Copy one of the reasons listed below and place it into "Reason for deleting ticket", then a push notification with provided content for its following keys will be sent to your spectator.
- When you delete a ticket for another reason not pre-defined by TIXNGO, your provided content for the keys notification.deleted.title and notification.deleted.content will be sent as a push notification to your spectator.
- In case contents have not been provided yet, the default value will be sent to your spectator.
(You can find detail for the listed keys in Multilingual Settings)
No | S-360 Ticket: Cancellation Cause | TIXNGO | |||
---|---|---|---|---|---|
Name | Code | Reason | Triggered keys | Default value | |
1 | Others reason (any text) | notification.deleted.title | Ticket deleted | ||
notification.deleted.content | A ticket for $$event.name$$ has been deleted | ||||
2 | Blacklist - PNA requests to blacklist | com.secutix.service.ticketproduction. CancellationCauseEnum/OTHER_PNA_REQUEST_BL | OTHER_PNA_REQUEST_BL | notification.deleted.other_pna_request_bl.title | Ticket deleted |
notification.deleted.other_pna_request_bl.content | A ticket for $$event.name$$ has been deleted | ||||
3 | Blacklist - Security requests to blacklist | com.secutix.service.ticketproduction. CancellationCauseEnum/OTHER_SECURITY_REQUEST_BL | OTHER_SECURITY_REQUEST_BL | notification.deleted.other_security_request_bl.title | Ticket deleted |
notification.deleted.other_security_request_bl.content | A ticket for $$event.name$$ has been deleted | ||||
4 | Cancellation for customer name change | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_CUST_NAME_CHANGE | ITA_CUST_NAME_CHANGE | notification.deleted.ita_cust_name_change.title | Ticket deleted |
notification.deleted.ita_cust_name_change.content | A ticket for $$event.name$$ has been deleted | ||||
5 | Cancellation for service reason | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_SERVICE_REASON | ITA_SERVICE_REASON | notification.deleted.ita_service_reason.title | Ticket deleted |
notification.deleted.ita_service_reason.content | A ticket for $$event.name$$ has been deleted | ||||
6 | Cancellation for theft/ loss | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_THEFT_LOSS | ITA_THEFT_LOSS | notification.deleted.ita_theft_loss.title | Ticket deleted |
notification.deleted.ita_theft_loss.content | A ticket for $$event.name$$ has been deleted | ||||
7 | Cancellation for upselling | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_UPSELLING | ITA_UPSELLING | notification.deleted.ita_upselling.title | Ticket deleted |
notification.deleted.ita_upselling.content | A ticket for $$event.name$$ has been deleted | ||||
8 | Cancellation on customer request | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_CUSTOMER_REQUEST | ITA_CUSTOMER_REQUEST | notification.deleted.ita_customer_request.title | Ticket deleted |
notification.deleted.ita_customer_request.content | A ticket for $$event.name$$ has been deleted | ||||
9 | Cancelled - Refunded | com.secutix.service.ticketproduction. CancellationCauseEnum/REFUNDED | REFUNDED | notification.deleted.refunded.title | Ticket deleted |
notification.deleted.refunded.content | A ticket for $$event.name$$ has been deleted | ||||
10 | Cancelled by EBO | com.secutix.service.ticketproduction. CancellationCauseEnum/EBO_CANCELLED | EBO_CANCELLED | notification.deleted.ebo_cancelled.title | Ticket deleted |
notification.deleted.ebo_cancelled.content | A ticket for $$event.name$$ has been deleted | ||||
11 | Change card number | com.secutix.service.ticketproduction. CancellationCauseEnum/CHANGE_RFID | CHANGE_RFID | notification.deleted.change_rfid.title | Ticket deleted |
notification.deleted.change_rfid.content | A ticket for $$event.name$$ has been deleted | ||||
12 | Event cancellation | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_EVENT_CANCELLATION | ITA_EVENT_CANCELLATION | notification.deleted.ita_event_cancellation.title | Ticket deleted |
notification.deleted.ita_event_cancellation.content | A ticket for $$event.name$$ has been deleted | ||||
13 | Forbidden | com.secutix.service.ticketproduction. CancellationCauseEnum/FORBIDDEN | FORBIDDEN | notification.deleted.forbidden.title | Ticket deleted |
notification.deleted.forbidden.content | A ticket for $$event.name$$ has been deleted | ||||
14 | Invalid print | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_INVALID_PRINT | ITA_INVALID_PRINT | notification.deleted.ita_invalid_print.title | Ticket deleted |
notification.deleted.ita_invalid_print.content | A ticket for $$event.name$$ has been deleted | ||||
15 | Loss - Courier failure situation unclear | com.secutix.service.ticketproduction. CancellationCauseEnum/LOSS_COURIER_FAILURE | LOSS_COURIER_FAILURE | notification.deleted.loss_courier_failure.title | Ticket deleted |
notification.deleted.loss_courier_failure.content | A ticket for $$event.name$$ has been deleted | ||||
16 | Loss - Return back to organization distribution | com.secutix.service.ticketproduction. CancellationCauseEnum/LOSS_RETURN_DISTRIBUTION | LOSS_RETURN_DISTRIBUTION | notification.deleted.loss_return_distribution.title | Ticket deleted |
notification.deleted.loss_return_distribution.content | A ticket for $$event.name$$ has been deleted | ||||
17 | Mobile take back | com.secutix.service.ticketproduction. CancellationCauseEnum/MOBILE_TAKE_BACK | MOBILE_TAKE_BACK | notification.deleted.mobile_take_back.title | Ticket deleted |
notification.deleted.mobile_take_back.content | A ticket for $$event.name$$ has been deleted | ||||
18 | Courier Failure (excl. stolen) | com.secutix.service.ticketproduction. CancellationCauseEnum/OTHER | OTHER | notification.deleted.other.title | Ticket deleted |
notification.deleted.other.content | A ticket for $$event.name$$ has been deleted | ||||
19 | Printing issue - Low printing quality or paper jam | com.secutix.service.ticketproduction. CancellationCauseEnum/PRINT_KO | PRINT_KO | notification.deleted.print_ko.title | Ticket deleted |
notification.deleted.print_ko.content | A ticket for $$event.name$$ has been deleted | ||||
20 | Reprint | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT | REPRINT | notification.deleted.reprint.title | Ticket deleted |
notification.deleted.reprint.content | A ticket for $$event.name$$ has been deleted | ||||
21 | Reprint - App not working, change to paper ticket | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_APP_PAPER | REPRINT_APP_PAPER | notification.deleted.reprint_app_paper.title | Ticket deleted |
notification.deleted.reprint_app_paper.content | A ticket for $$event.name$$ has been deleted | ||||
22 | Reprint - Customer requests change to mobile ticket | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_CONTACT_MOBILE | REPRINT_CONTACT_MOBILE | notification.deleted.reprint_contact_mobile.title | Ticket deleted |
notification.deleted.reprint_contact_mobile.content | A ticket for $$event.name$$ has been deleted | ||||
23 | Reprint - Customer requests change to paper ticket | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_CONTACT_PAPER | REPRINT_CONTACT_PAPER | notification.deleted.reprint_contact_paper.title | Ticket deleted |
notification.deleted.reprint_contact_paper.content | A ticket for $$event.name$$ has been deleted | ||||
24 | Reprint - Destroyed or unreadable barcode | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_DAMAGED | REPRINT_DAMAGED | notification.deleted.reprint_damaged.title | Ticket deleted |
notification.deleted.reprint_damaged.content | A ticket for $$event.name$$ has been deleted | ||||
25 | Reprint - Organization requests change to mobile ticket | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_ORG_MOBILE | REPRINT_ORG_MOBILE | notification.deleted.reprint_org_mobile.title | Ticket deleted |
notification.deleted.reprint_org_mobile.content | A ticket for $$event.name$$ has been deleted | ||||
26 | Reprint - Organization requests change to paper ticket | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_ORG_PAPER | REPRINT_ORG_PAPER | notification.deleted.reprint_org_paper.title | Ticket deleted |
notification.deleted.reprint_org_paper.content | A ticket for $$event.name$$ has been deleted |
27 | Reprint - PNA requests to on-site collection | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_PNA_ON_SITE | REPRINT_PNA_ON_SITE | notification.deleted.reprint_pna_on_site.title | Ticket |
deleted |
notification |
.deleted.reprint_pna_on_site.content | A ticket for $$event.name$$ has been |
deleted |
The ticket's transfer for $$event.name$$ was rejected by $$spectator.name$$
Your ticket for $$event.name$$ was updated
28 | Reprint - Reseating after distribution | com.secutix.service.ticketproduction. CancellationCauseEnum/REPRINT_RESEAT | REPRINT_RESEAT | notification.deleted.reprint_reseat.title | Ticket deleted |
notification.deleted.reprint_reseat.content | A ticket for $$event.name$$ has been deleted | ||||
29 | Resale cancelled | com.secutix.service.ticketproduction. CancellationCauseEnum/RESALE_CANCELLED | RESALE_CANCELLED | notification.deleted.resale-cancelled.title | Ticket deleted |
notification.deleted.resale-cancelled.content | A ticket for $$event.name$$ has been deleted | ||||
30 | Resale pending | com.secutix.service.ticketproduction. CancellationCauseEnum/RESALE_PENDING | RESALE_PENDING | notification.deleted.resale-pending.title | Ticket available for resale |
notification.deleted.resale-pending.content | The ticket for $$event.name$$ |
Notification sent at mobile app logout:
- Triggered when a session is clear on the Admin tool.
20
Notification to initiate logout of session:
- Triggered when a device initiated a connection with your account.
notification.logout.force.title
notification.logout.force.content
Notification at ticket transfer has been auto canceled
Push Notifications at delete resale pending
- Triggered when ticket is deleted with delete reason RESALE_PENDING
is now available for resale | |||||
31 | Reseating | com.secutix.service.ticketproduction. CancellationCauseEnum/RESEAT | RESEAT | notification.deleted.reseat.title | Ticket deleted |
notification.deleted.reseat.content | A ticket for $$event.name$$ has been deleted | ||||
32 | Resold - Resale after distribution to mobile phone | com.secutix.service.ticketproduction. CancellationCauseEnum/RESOLD | RESOLD | notification.deleted.resold.title | Ticket deleted |
notification.deleted.resold.content | A ticket for $$event.name$$ has been deleted | ||||
33 | Stolen - Ticket stolen | com.secutix.service.ticketproduction. CancellationCauseEnum/THEFT | THEFT | notification.deleted.theft.title | Ticket deleted |
notification.deleted.theft.content | A ticket for $$event.name$$ has been deleted | ||||
34 | Printing Quality Low/Ticket Damaged | com.secutix.service.ticketproduction. CancellationCauseEnum/LOSS | LOSS | notification.deleted.loss.title | Ticket deleted |
notification.deleted.loss.content | A ticket for $$event.name$$ has been |
Push Notifications at delete resale cancelled
Triggered when ticket is deleted with delete reason RESALE_CANCELLEDdeleted | ||||
35 | Transaction not completed | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_TRANS_NOT_COMPLETED | ITA_TRANS_NOT_COMPLETED | notification.deleted. |
ita_trans_not_completed.title |
Ticket deleted |
notification.deleted. |
ita_trans_not_completed.content | A |
ticket for $$event.name$$ has been |
Push Notifications at delete resold
- Triggered when ticket is deleted with delete reason RESOLD
deleted | ||||
36 | Wrong data | com.secutix.service.ticketproduction. CancellationCauseEnum/ITA_WRONG_DATA | ITA_WRONG_DATA | notification.deleted. |
ita_wrong_data.title | Ticket |
deleted |
notification.deleted. |
ita_wrong_data.content | A ticket for $$event.name$$ has been |
deleted |
Possible keys in email template and push notification
Here is the list of possible keys to use for the email templates:
...
email.invitation.approval.body + email.invitation.approval.subject
-"spectator.name" - sender's first and last name.
-"sender.email" - sender's email.
-"receiver.email" - receiver's email.
-"spectator.email" - receiver's email.
-"event.name" - ticket's event name.
-"event.date" - ticket's event start time.
-"app.name" - ticket's initial app name (can be set base on appId in settings).
-"app.dl.link" - ticket's initial app download link (can be set base on appId in settings).
-"ticket.id" - ticket Id.
-"ticket.details.main" - ticket's main detail.
-"ticket.details.hidden.transfer-extra" - ticket's transfer-extra info.
email.information.approval.body + email.information.approval.subject
-"spectator.name" - sender's first and last name.
-"sender.email" - sender's email.
-"receiver.email" - receiver's email.
-"spectator.email" - receiver's email.
-"event.name" - ticket's event name.
-"event.date" - ticket's event start time.
-"app.name" - ticket's initial app name (can be set base on appId in settings).
-"app.dl.link" - ticket's initial app download link (can be set base on appId in settings).
-"ticket.id" - ticket Id
-"ticket.details.main" - ticket's main detail.
-"ticket.details.hidden.transfer-extra" - ticket's transfer-extra info.
email.information.cancel.body + email.information.cancel.subject
-"spectator.name" - sender's first and last name.
-"sender.email" - sender's email.
-"receiver.email" - receiver's email.
-"spectator.email" - receiver's email.
-"event.name" - ticket's event name.
-"event.date" - ticket's event start time.
-"app.name" - ticket's initial app name (can be set base on appId in settings).
-"app.dl.link" - ticket's initial app download link (can be set base on appId in settings).
-"ticket.id" - ticket Id
-"ticket.details.main" - ticket's main detail.
-"ticket.details.hidden.transfer-extra" - ticket's transfer-extra info.
...