Cloning emails - keep the operational checkbox 'CHECKED'

[Anonymous]

Hi there - we have had this issue with our operational emails when we want to clone them. Each time we clone an operational email, we have to manually CHECK the operational email checkbox. I would think that if you 'clone' that all settings (including operational settings) would translate.

While we are hyper aware of this, it has been problematic if we miss that detail.

Please look into building a more robust cloning function to support operational emails.

[Anonymous]

Hi Annie,

I'm not sure this is the best idea. In Europe, Australia, and I'm sure many other places, there are very strict spam regulations, and I think it's better to force everyone to manually tick that box than to leave it ticked when cloning.

That being said, an alternative may be a message during the cloning process telling you that you'll need to recheck that box. It's definitely inconvenient that they don't tell you, but the process is correct - as most companies would much rather stick on the safe-side when we're talking about spam regulations.

Regards,
Brody

[Anonymous]

Hi Annie,

When you email is part of a campaign and you close the campaign the operational checkbox setting is cloned as well and the email is still set to be operational - this might help you out.

Regards
Bart

[Anonymous]

I think this is actually a bug.  We have a list of things like this in a queue to fix.  We will fix it as soon as possible, but for the time being, just make sure to double-check.

[Anonymous]

We've been caught cloning programs with Operational emails, and the subsequent email goes out unintentionally operational. In todays environment I would vote to have ALL emails clone as not operational to be safe. It's easier to get in the mindset of always choosing to intentionally make an email operational - I'd rather risk missing a few unsubscribes than emailing them in error. We can always send out a supplimental if necessary - we can't take back emails sent errantly.