Templates and content

Work with the right context

Arrange template blocks around the actual message and call to action. Keep sender identity, plain-text content and preference links with the version being reviewed. A preview should help the reviewer understand the customer experience without sending a bulk campaign.

Keep the next action clear

When the content changes after review, prepare a new version. Existing send history keeps the exact subject and body that were submitted to the provider. That distinction makes later performance comparisons and customer enquiries understandable.

Coordinate the workflow

Review template. Email Designer submits a version with Status: Draft → Submitted. The independent Email Marketing Manager approves the exact content, sender context and required footer. An edit creates a new reviewable version. Internal test delivery cannot bypass the permitted test-recipient boundary.

Approve campaign. Email Marketing Manager submits the audience rules, purpose, approved template and schedule. Campaign Approver independently approves that Revision and the AudienceRevision. Changed content, audience or purpose requires fresh review. The scheduled command is rejected if approval no longer matches.

Email templates. The campaign uses the exact approved content and footer. Reject edits to approved content without a new version and review.

Email campaigns. An approved unchanged campaign creates one delivery intent. Reject self-approval or a changed audience using a stale approval.

Review the complete message

An email template brings together the subject, body, reusable blocks and footer. The designer prepares the version the campaign will use, then an independent marketing manager reviews it. Check the sender identity, links and preference destination in that specific campaign context. A polished body with an unrelated footer or an unsuitable sender can still produce a confusing customer message.

Reusable blocks reduce repeated editing, but an approved campaign needs a stable content version. Changing a shared block must not silently replace the content that was previously reviewed for a scheduled send. Prepare a new template version and return affected protected campaign content through its required approval before it is dispatched.

Check the destination as well as the copy

A customer selecting a preference link should reach the intended configured preference center and purpose. Review the visible wording and the destination together so an apparently narrow choice does not apply an unexpected scope. The template supplies the communication; the actual preference event records the customer’s resulting decision.

When a message uses subscriber information, verify the permitted data and the intended audience before scheduling it. Keep personal data out of reusable content where it would be exposed to unrelated recipients. A template preview helps the team inspect the composition, but its appearance is not evidence that a provider delivered the eventual message.

The finished template should give the campaign manager a clear approved version to select. Its content history explains later revisions, while send records identify which version was actually used for each campaign outcome.