Dylan P
My feedback
1 result found
-
83 votes
Hello,
We are looking to address full duplication of the template. One questions that sticks out is versions. If a template that also has versions is duplicated would the expectation that the versions are also duplicated in the copy?
Additionally what if we surfaced a unique identifier for a template to effectively allow for sending of the template across any sending domain. So in your API call you would be using the unique ID rather then the template name? That is to say as an option, we are not going to be breaking any integrations that are using the template name currently. Let me know what you think.
Travis
An error occurred while saving the comment
Re: the latest reply - glad to hear it's in the queue!
For our pretty straightforward use case (use the same visual elements across a bunch of different emails, without recreating them each time), neither of those features would be particularly necessary. The version history wouldn't be super important, and we only use one sending domain.