Good day all,
We are currently only offering digital content to our patrons, and I'm wondering if you completely revamped your order confirmation email template to remove any hint of ticketing processes that they would need if attending an event in person, or if you kept your current format and added info specifically for digital content? Or is it possible to have multiple order confirmation templates? Or are you using the real estate on a PAH template for this? Or are there other (i.e. better) options?
We are trying not to scrap our current confirms/PAH templates completely, as we hope to be able to present a few very socially-distanced events this spring.
Thanks!
Lesley
As mentioned by Gawain, using the LTR_TNEW_DYN_EMAIL_CONTENT is the recommended way to delivery product-specific info in the order confirmation. We also have this page of recommendations specific to digital content; check out the section "Granting Access to Digital Content."
Hi Michael,
We are using an entry in the LTR_TNEW_DYN_EMAIL_CONTENT for a specific contribution type. It works fine if used online. When I email an order confirmation email from within the Tessitura client (using the same TNEW template), the entry in the LTR_TNEW_DYN_EMAIL_CONTENT is not included in the email. Should it be?
Thanks,
Sabina
Hi Sabina,
While Michael will certainly know for sure, I seem to recall during my research that the TNEW_DYN_EMAIL_CONTENT table only works when sent through TNEW, not the client.
I'm not sure what the comparable path is for email confirms sent from the client.
Lesley is correct. As noted in the documentation for that table, "Dynamic content is only displayed for confirmation emails generated for orders completed through your TN Express Web site. If you are using the same email formats for email confirmations sent from order placed in the Tessitura application, dynamic content will not apply."
You would need to use a customized order confirmation email to get the same dynamic behavior in emails sent from the client. An HTML Template Order Confirmation is the best solution for this. We will be adding a recipe to the HTML Template recipe book soon as an example of this.
Depending on what you plan to include in your dynamic text, you might have some other options, like including generic static text, sending a second email specifically to donors, or relying on the separate contribution acknowledgment functionality.
We've received some conflicting info around the HTML templates. Can you confirm if they currently work - we are on 15.1.16 - or will only work beginning in v16?
HTML templates sent from the application and from custom websites are supported in version 15.0 and 15.1, so you can begin using them right now for those situations. HTML templates sent from TNEW will be supported in version 16.
Thank you!