email_note

Sean Hanly

Updated April 13, 2023 13:58

Category: email
Key: email_note
Type: text
Internal setting: false
Scopes: [[:account, :subdomain, :program, :show, :event], [:account, :subdomain, :product], [:account, :ticket_price]]

Overview

When this setting is populated, the text set in the "email_note" setting will feed through to the 'email note' section in checkout mailers (order confirmation emails). This can be set at account, subdomain, program, show and event level, as well as within individual products and ticket prices.

The 'email note' section in the mailer will populate depending on which level of the setting is applicable to their order. I.e., account level setting will be sent in every checkout mailer, whilst set at show level it will only go out to those booking the show.

The HTML code (merge field) for email notes:

{{ order.email_notes }}

Email note text can incorporate HTML code for formatting such as bold, italics, bullet points and hyperlinks. For example:

Notes

There is a hierarchy of the "email note" setting, as there is a limit to how many different-level email notes will be pulled through to the checkout mailer. 'Account' is the lowest, and 'event', 'product', 'ticket price' are the highest.

The hierarchy

[
[:account, :subdomain, :program, :show, :event], 
[:account, :subdomain, :product], 
[:account, :ticket_price]]
]

Any text added to the setting at a higher level will overwrite any text set at a lower level within the same pathway - it will not add to it. E.g. text set at 'event' level will overwrite text set at 'account' level.

How it works

The feature collects two 2 notes at the ticket line item level:

1. From the 'ticket price' section:

[:account, :ticket_price]

2. From the 'event' section:

[:account, :subdomain, :program, :show, :event]

If there is an email note set at account level, but not at ticket price level, this section will roll up into the account level one and pull that into the email note section of the mailer. If there is also an email note set within the 'event' section (i.e., at subdomain, program, show or event level), the email note set within this section will also be included in the checkout mailer.

This means that you could end up with an account level email note (because there is not one at ticket price) and a subdomain/program/show/event level email note both being pulled into the checkout mailer. To avoid this, it is best not to set anything at account level and use subdomain instead.

Example

A customer buys one ticket to an event and a brochure product.

There is an email note set on the account, event, product and ticket price.

The customer will see email notes from the following sections:

ticket price - from [:account, :ticket_price]
event - from [:account, :subdomain, :program, :show, :event]
product - from [:account, :subdomain, :product]

But if the above were to happen, but without a ticket price email note, the account level email note will be pulled through in its place.

So if there is an email note set on the account, event and product (but not on the ticket price)...

The customer will see email notes for the following sections:

account - from [:account, :ticket_price]
event - from [:account, :subdomain, :program, :show, :event]
product - from [:account, :subdomain, :product]

By removing the account level email note, and instead setting at subdomain, event and product, we can stop the account level one being included by default.

So if there is an email note set on the subdomain, event and product (but not on the account or the ticket price)...

The customer will see email notes for the following sections: