# eWizard (Viseven) — platform conventions

Structural vocabulary for the Email Drafter (Skill 4) when a template's **Target platform** is eWizard. This explains *how eWizard is built*; the brand-specific module set, placeholders, limits and mandatory wording live in `<Brand> Email Templates.docx`.

## How an eWizard email is built

- eWizard uses a **components → blocks → templates** model (Viseven describe it as a "nesting doll": templates are made of blocks, blocks are made of components).
- Emails are assembled in the **eWizard Editor** by placing **pre-approved, design-less content modules/blocks** into the layout via **placeholders** (drag-and-drop from a sidebar of components, blocks and placeholders).
- Content modules are **pre-approved** and reused across emails; styling/layout properties can be adjusted, and content sits in defined placeholders. eWizard integrates with the brand's **DAM** and downstream systems (e.g. Salesforce, Adobe Experience Manager) and can auto-assemble an email from approved modules.

## What this means for drafting

- **Compose within the brand's approved modules/blocks.** The drafter fills the placeholders of approved blocks; it must **not invent new modules or restructure** the template.
- **Respect each block's role and limits** (headline block, body/claim block, CTA block, ISI block, footer block, etc.) and the order the template defines.
- **Mandatory modules are fixed** — ISI / fair balance, sender, unsubscribe. Reproduce verbatim.
- If a needed message has no approved module/placeholder, surface it as a gap rather than fabricating a block.

## Capture these in `<Brand> Email Templates.docx` (eWizard template)

- The brand's **approved module/block set**, in order — block name, the placeholders it exposes, and any per-block word/character limit.
- The **mandatory modules** verbatim (ISI/fair balance, sender, unsubscribe).
- The **footer** (verbatim, or the approved footer module).
- **Image handling**: which blocks accept images and the image specs from the DAM.

Take these from the brand's **real, approved eWizard project/modules** — the module set and placeholders are project- and brand-specific and must not be guessed.

---

*Researched 2026-05-27 from Viseven's eWizard documentation/marketing pages. eWizard ships frequent releases, so verify the module model and editor behaviour against the brand's current eWizard project before relying on them.*

Sources:
- [Create Healthcare Email Templates with eWizard — Viseven](https://viseven.com/create-email-templates-ewizard-2/)
- [eWizard Content Experience Platform — Viseven](https://viseven.com/ewizard/)
- [Reinforce Pharma Messaging with Smart Email Fragments — Viseven](https://viseven.com/how-to-make-pharma-brand-messages-reinforce-one-another-with-email-fragments-2-practices/)