Is your feature request related to a problem? Please describe.
When sending a message to attendees, there is no way to personalize the content dynamically. For example, it is not possible to address each attendee by their first name, which makes mass messages feel impersonal.
Describe the solution you'd like
Support personalization tokens in the message body, similar to the Liquid syntax already used in email templates (e.g. {{ attendee.first_name }}, {{ attendee.last_name }}, {{ ticket.name }}). These tokens would be substituted with each recipient's actual data before sending.
A reference list of available tokens could be displayed directly in the message editor.
Additional context
The attendee data (first name, last name, email, ticket type) is already available at send time in SendEventEmailMessagesService. The Liquid rendering infrastructure (LiquidTemplateRenderer) also already exists in the codebase — it is currently used for order confirmation and attendee ticket emails.
Is your feature request related to a problem? Please describe.
When sending a message to attendees, there is no way to personalize the content dynamically. For example, it is not possible to address each attendee by their first name, which makes mass messages feel impersonal.
Describe the solution you'd like
Support personalization tokens in the message body, similar to the Liquid syntax already used in email templates (e.g.
{{ attendee.first_name }},{{ attendee.last_name }},{{ ticket.name }}). These tokens would be substituted with each recipient's actual data before sending.A reference list of available tokens could be displayed directly in the message editor.
Additional context
The attendee data (first name, last name, email, ticket type) is already available at send time in
SendEventEmailMessagesService. The Liquid rendering infrastructure (LiquidTemplateRenderer) also already exists in the codebase — it is currently used for order confirmation and attendee ticket emails.