OpenSend docs
Template Version History
Template version history lets teams understand how content changed over time. Use it to audit edits, compare a published version with a draft, and recover the intent behind a campaign or automation message.
Operating model
Treat published templates as production dependencies. For larger content changes, duplicate the template or create a draft, test previews, and publish only after review.
Incident use
When a recipient reports incorrect content, check the email timestamp against the template version that was published at that time. Then inspect logs and payload variables to determine whether the issue came from template content or caller data.