Use New System Templates in Any Folder

Thank you for posting this, @mobrien14! Seconded!

It would also be awesome if we were able to easily move or convert select templates to system templates without having to resort to copying the code and overwriting a default template, or rebuilding our templates from scratch.

For those of us with established email templates, it would allow us to clean up a lot of old templates we save for the express purpose of cloning and editing (with lorem ipsum text).

Having lorem ipsum templates for newsletters, support emails, etc. is especially necessary right now given the lack of any sort of custom email element library. It would be fantastic if we were able to templatize content blocks (ex: headers, footers, signatures, event information, product release updates, etc.) so we could easily build out emails without having to re-do significant amounts of formatting.

See the below screenshot for a new template I’ve been building out for a monthly newsletter. It’d greatly simplify my process if I was able to just drag and drop those different types of blocks into an email from a content library, rather than having to clone an old newsletter and update the information. It’d also reduce the likelihood of accidentally sending old information if it didn’t get updated. 

​@revathimenon, can we get some eyes on this one? It’d be fantastic to be able to modify/remove/add templates in the system templates folder.

One huge use case – setting the email type to operational or transactional, and selecting the Opt-Out page. We shouldn’t have to double or triple the number of templates we have, just because we need certain templates to use different setups.

​@mobrien14 create a new template using pre-built templates has been around for some time.

​@dayn.johnson Thanks for the feedback. Can you elaborate on this use case - for an operational email, why would you need an opt out page?

​@ssamarth responding to both points here.

BLUF

What would it take to give super users full control over System email templates?

1 (your answer to ​@mobrien14)

Yes, create new templates is an option – however, the System templates are something we would never choose to use. I think I can safely speak for most of us admins here – we have to build additional templates, and keep going back to them to clone our organization’s templates that we have built to align with our branding guidelines.

Based on this, there is no way for us to choose “Create new template” using one of our organization’s preferred templates. This results in confusion if someone else is building emails, messy organization, bloat, and an inefficient build process. Hence: Navigate to our preferred template > Clone > Move to necessary folder > Configure opt-out settings. 

Our ask: Give super admins full control over the ⚙ System templates.

We should be able to: edit, delete, add, change availability… all the things. This would allow us to configure new templates correctly (correct template choice, folder location, operational type) and would eliminate confusion for our end users.

This brings me to number 2.

2 (my response to your question re: opt-outs)

“For an operational email, why would you need an opt out page?”

Short answer? We don’t.

Longer answer:

This would be solved by our ask (full super admin control over System templates).

I build multiple categories of templates: Brand Standard (like using company letterhead), and Unique (such as newsletters, surveys, etc. that have the same sections each time). Part of this is due to newsletters and other emails that would benefit from saved content blocks, dynamic content, etc. – but some is also due to not being able to use these as System templates and being able to select the email type and opt-out category when initially creating a new template using these as our starting point.

It’s true – we don’t need an opt-out page for an operational email. But, we don’t want to clutter our template library with on-brand templates to solve for every opt-out category – and we don’t want to accidentally send a non-operational email with the wrong opt-out category.

Screenshots

I can only second this!
In our organisation we have multiple Global CS teams.
Each team in each region manages a segment of customers. SMB/Enterprise/Strategic

For renewal playbooks as an example, we need to create email templates per team. 
There are only slight differences in language. 

It would have saved me a lot of time if I could clone an email template I created and change each one and save as into a new template.