Email Branding

Every email your workspace sends can be branded consistently — logo, header, footer, and unsubscribe copy — without having to design each send individually. When you want more control, upload your own HTML template with slot markers and the platform injects the branding pieces in the right places. Reach the settings at SettingsEmail Branding. Admin or Owner role required.

Two modes: envelope wrap vs. custom template

There are two ways the platform assembles the final email body:

Envelope wrap (default). The platform stacks your branding around the AI body in a fixed order: logo → header → AI body → footer → unsubscribe. Zero setup — configure the Logo, Header, Footer, and Unsubscribe cards and every email comes out branded.
Custom HTML template. Upload your own designed HTML template with  slot markers. The template becomes the outer shell; branding pieces get injected into the markers wherever you place them. Use this when you have a specific design (Stripo / Beefree / Figma-to-HTML export, or hand-authored) that the envelope wrap can't match.

The two modes are mutually exclusive per workspace — toggle Use custom template in the Custom HTML template card to switch. The branding cards above (Logo / Header / Footer / Unsubscribe) apply to both modes: their values become the slot content when the custom template is in use.

Slot markers

Slot markers are HTML comments the platform recognizes and substitutes at send time. Only is required — every other marker is optional. Delete any you don't need, or move them to a different location; the platform substitutes each marker wherever it appears.

Marker	Required?	What gets injected
`<!--ABP:AI_BODY-->`	Required	AI-adapted body copy for the current channel.
`<!--ABP:LOGO-->`	Optional	Workspace logo as a centered `<img>` block.
`<!--ABP:HEADER-->`	Optional	Workspace header (text or image, per your Header card).
`<!--ABP:FOOTER-->`	Optional	Workspace footer. The `[UNSUBSCRIBE]` marker inside your footer text is still honored.
`<!--ABP:HERO_IMAGE-->`	Optional	First image from the promotion's source media.
`<!--ABP:UNSUBSCRIBE-->`	Optional	Per-connector unsubscribe link. If absent AND your Unsubscribe toggle is on, the CRM's default footer takes over.

Why HTML comments (not {{tokens}})

Email service providers use varied placeholder syntaxes at send time — Brevo {{ unsubscribe }}, Mailchimp *|UNSUB|*, EmailOctopus {{UnsubscribeUrl}}, MailerSend {$unsubscribe}, SendPulse {{unsubscribe_url}}, Mailjet [[UNSUB_LINK_EN]], and more. HTML comments never collide with any of these, are invisible in browser preview, and require no template engine to parse.

Uploading a template

Open the Custom HTML template card

Go to SettingsEmail Branding and scroll to the Custom HTML template card at the bottom.

Pick an intake mode

Three options: Upload file (a .html or .htm file, max 500 KB); Paste HTML (paste raw HTML into a textarea); Use starter (pick from shipped starter templates — the Basic starter is a hand-crafted reference showing all seven markers in a clean table-based layout).

Wait for validation

On upload, the platform sanitizes the HTML (widened email-safe allowlist — table-based layouts + inline styles preserved; <script>, <iframe>, on* handlers, and dangerous URL schemes stripped) and validates that  is present. Missing the required marker returns a 422 with the fix instruction.

Review the marker checklist + preview

The card shows which markers are detected and a sandboxed preview with placeholder content in each slot. Green checkmark = slot filled at send time; red X on AI_BODY = template is unusable.

Toggle Use custom template

Flip the switch to activate. The toggle is disabled while any required marker is missing. Turn it OFF at any time to revert to the default envelope wrap without losing the uploaded template.

Design constraints for cross-client rendering

Inline all styles. Gmail's web client strips <style> blocks entirely. Use style="..." attributes on individual elements.
Use tables for layout. Flexbox and CSS grid render inconsistently across email clients. Nested <table> with <tr> / <td> is the standard.
Max width 600px. Outlook and Apple Mail render 600px cleanly; wider layouts cause horizontal scrolling on some clients.
Cross-client attrs. bgcolor, align, valign, cellpadding, cellspacing, border, colspan, rowspan are preserved by the template sanitizer and needed for Outlook.
500 KB size cap. Templates larger than this are rejected at upload.

Interaction with unsubscribe placement

The Unsubscribe card's Custom placement inside my footer toggle continues to work with custom templates: put [UNSUBSCRIBE] anywhere in your footer text (the workspace-level Footer field, not the HTML template) and it gets swapped for the per-connector placeholder inside the  slot. Alternatively, place  anywhere in the template for a standalone unsubscribe line.

Some CRMs (Mailchimp, AWeber, Zoho Campaigns, MailerLite, SendPulse) append their own unsubscribe footer regardless of what we place in the body — for these connectors the  slot is silently left empty and the CRM footer handles it. See the per-connector matrix under the Unsubscribe card.

Per-promotion overrides

You can override any branding field — including the custom template and toggle — on a per-promotion basis from the composer's branding panel. Useful for one-off campaigns that need a different template than your workspace default. The override merge semantics: any field set on the override wins over the workspace default; unset fields inherit; setting a field to null clears it (e.g., to force envelope-wrap on a single send even though the workspace default is a custom template).