Library · Emails
Design client emails that land right
A visual, HTML and plain-text builder with 14 block types, brand style tokens, UTM parameters, inbox-safe HTML export and saved blocks. Sign in to your library, or see how it works.
Library · Emails
Designing a client email usually means a separate ESP login per client and a builder that fights you on anything custom. The Email Builder in AI Marketing Dashboard supports visual design, hand-written HTML and plain-text authoring, with brand styling, UTM parameters and the email-client-safe export an agency needs to ship emails that look right in every inbox.
Build visually with a block editor when you want speed, paste and edit your own HTML when you need pixel control, or write a plain-text email when that is what converts — and switch an email between the three modes after creation without losing your work. Each mode keeps its own source, so changing your mind is reversible, not destructive.
It means the tool fits the email, rather than forcing every send into one rigid template editor: a polished campaign and a personal-feeling plain-text note both live here.
Compose visually from 14 block types — logo, heading, text, button, image, video, quote, navigation menu, two-column, divider, spacer, raw HTML, social links and footer — reordering by drag. Headings, text and quotes support inline rich text (bold, italic, underline, links and lists), so the copy reads the way it should without dropping to code.
Social blocks render real brand icons, image blocks take real uploads, and the whole thing previews at phone and desktop widths — so the email you design is the email that lands.
Set email-wide tokens — page and content background, content width, corner radius, body and heading fonts, and text, heading and link colors — then override per block where you need to: button colors and radius, image width, divider style, typography and spacing. A client's email looks like the client's brand, not a generic template.
Because the styling is structured, an email stays consistent as it grows and is fast to re-skin for the next send — the design system does the heavy lifting.
Set UTM parameters that are appended to every link on export, so traffic can be attributed in your configured analytics tools. The builder generates table-based HTML intended for broad email-client compatibility.
Open tracking, click tracking, and test delivery are not claimed until a delivery provider is configured.
Save any block, such as a branded header, a styled CTA, or a footer, to a saved-blocks library and reuse it in future drafts.
Delivery remains the responsibility of a configured external provider.
The preview pane is not an impression of the email; it is the generated HTML rendered in a sandboxed frame — the same markup the export produces — so what gets signed off is what a mail client will actually parse. A plain-text alternative is derived from the same blocks, which is the version some subscribers and some filters read instead.
When the draft looks right, send yourself a test. The builder delivers to real addresses through a sending domain the workspace has verified for that client, and says so plainly when no verified domain or from address exists yet rather than reporting a send that never happened. For handover, the email copies or downloads as a single HTML file — the artifact an ESP, a developer or a client's own platform can take without a rebuild.
A nurture sequence is part of a campaign rather than a loose document, so every email is stored under its client and the theme it was written for — next to the landing page it links to and the copy it borrows from. Nobody has to remember which of five near-identical subject lines was the one that actually shipped.
Switch account and the list redraws to that client's emails, and the email-campaign planner reads the same shelves — so a brief and the emails it commissions never end up in two different filing systems.
