Page tree

Overview

To streamline communication and enhance the user experience, we’ve introduced an email consolidation feature for bulk ticket actions (transfer/accept/reject/cancel). Organizers now have the flexibility to send a singular email for grouped ticket actions, reducing email clutter and providing a succinct overview of transactions.

Adjustable Ticket Quantity

Organizers can set a specific ticket quantity that triggers consolidated email communication for bulk ticket actions. 

If the action involves tickets equal to or exceeding this number, a single email will be sent.

For actions involving tickets below the defined quantity, the existing behavior (one email per ticket, including ticket details) will remain.

Note

Transfer messages, if enabled and utilized, will appear once in consolidated emails, even if they pertain to multiple tickets.

Examples:

  • If the targetted quantity is “3” and a spectator sends 3 or more tickets to someone else, a single email, using the new template, will be sent for all tickets involved in that action.
  • If a spectator transfers 1 or 2 tickets, individual emails (current behavior) will be sent for each ticket.

How to activate this feature

Enable the feature from the settings

In the Organizer settings, locate the setting Enable Single Email for Bulk Tickets Transfer feature (key: ticket.bulk-actions.quantity)

Update the value accordingly :

  • to totally disable this feature and use standard e-mail notifications, set 0
  • to use this feature as its maximum potential, define the ticket quantity that determines email consolidation

Configure the new e-mail templates for a branded experience

Newly crafted email templates facilitate the consolidated communication, providing clear and concise information for bulk ticket actions.

From the Multilingual Settings, adapt the following translations :

ContextSetting NameSetting Key
Initiating transfer to an unregistered recipientEmail subject sent to recipient when ticket transfer to Unknown account (single email for bulk tickets)email.invitation.bulk.approval.subject
Initiating transfer to an unregistered recipientEmail body sent to recipient when ticket transfer to Unknown account (single email for bulk tickets)email.invitation.bulk.approval.body
Initiating transfer to an already registered recipientEmail subject sent to recipient when ticket transfer to Known account (single email for bulk tickets)email.information.bulk.approval.subject
Initiating transfer to an already registered recipientEmail body sent to recipient when ticket transfer to Known account (single email for bulk tickets)email.information.bulk.approval.body
Finilizing transfer (success)Email subject sent to sender when ticket transfer delivered successfully (single email for bulk tickets)email.sent.sender.bulk.subject
Finilizing transfer (success)Email body sent to sender when ticket transfer delivered successfully (single email for bulk tickets)email.sent.sender.bulk.body
Finilizing transfer (failure)Email subject sent to recipient when ticket transfer cancel by sender (single email for bulk tickets)email.information.bulk.cancel.subject
Finilizing transfer (failure)Email body sent to recipient when ticket transfer cancel by sender (single email for bulk tickets)email.information.bulk.cancel.body
  • No labels