[FEATURE] - Enhance the Triggered Email Functionality with Standard Salesforce Features

[rdblake21]

Have you shared this feature idea request in the Trailblazer Community?

No - This is an idea that's come up at various Sprints and also has some Stale branches on it where work has been done.

Is your feature request related to a problem? Please describe.

Currently the Summit Events Email object is a self-contained object with triggering functionality for Transactional Emails. The emails are created and built within the object and to use merge fields, you're required to know the API Name. At the same time, you're unable to use merge fields in the subject line, where we know you can in the Lightning Email Template.

Overall the user experience for the Summit Events Email isn't entirely user friendly and is limited to what you can do in a Rich Text field as well as requiring you use the Classic Letter Head functionality, which is only accessible in the Setup Menu.

Describe the solution you'd like

Salesforce has made significant improvements in email template functionality with Lightning Email Templates and Enhanced Letterhead. We'd love to leverage these solutions to build our email templates and letterheads. Although they offer similar features, the option to use direct HTML in the email templates and letterhead provides greater versatility in our content.

Currently, templates enable easy resending of emails from the registration record without needing to change the status to trigger the email again.

Ideally, we'd like to:

1. Select the sender, status/substatus, and event as we do now.
2. Independently select an Enhanced Letterhead and a Lightning Email Template.
3. Choose an Email Template that defaults to an Enhanced Letterhead unless otherwise specified on the Summit Events Email Record.

Additionally, it would be valuable to:

1. Preview the email template, even without data, to see its presentation.
2. Make changes to the email without saving the template, allowing reusable assets while maintaining the uniqueness of each Summit Event Email record.

This approach would help avoid creating numerous email templates while ensuring flexibility and reusability.

Describe alternatives you've considered

There are limited alternative versions:

1. A picklist of options to select a Summit Event Registration field and display the API name in merge brackets in plain-text (would required an LWC
2. Display commonly used fields on the lightning page layout
3. Leveraging an integration with an email marketing tool (which is always an option).

To help determine if a recipe may be more appropriate, please share other use cases, if possible, this functionality would benefit from.

Not Applicable as this is enhancing core Summit Events functionality. Might need to make consideration for people still leveraging Salesforce Classic.

Are you willing and interested in being engaged during the development and testing process?

Yes