Email templates
Email templates are reusable templates you design once and that you can then use in all your campaigns: polished design, header with logo, consistent layout, signature.
Route: /app/templates/email
What it's forβ
Without email templates, each email campaign would be done with raw text, no formatting, no images, no call-to-action button. With templates:
- Visual consistency: all your campaigns look like your organization.
- Time saving: you don't redo the layout for each send β you just replace the variable content.
- Professionalism: a well-designed email is opened and read, a raw email is often ignored.
Typical cases:
- Monthly newsletter: a template with banner, title, paragraphs, image, button.
- Event invitation: a more visual template with date, time, location, RSVP.
- Donation solicitation: a targeted template with a large image and a Donate button.
- Community notification: a sober template, more institutional.
Anatomy of the pageβ
The page is organized in:
- Top bar: title My Email Templates, Examples and Add a template buttons.
- Card grid: one template per card, organized in responsive columns (1 on mobile, 2 on tablet, 3-4 on desktop depending on screen width).
If you have no template, an empty state displays with two large buttons: See examples and Create my first template.
Anatomy of a template cardβ
Each template displays as a card with:
| Zone | Content |
|---|---|
| Cover image | Auto-generated thumbnail of the template's visual rendering. If no rendering is yet available, a generic image with pale blue gradient is displayed. |
| Title | Template name, inline editable: click on the title to modify it directly, validate with Enter. |
| Creation date | Created on May 12, 2026 |
| Actions (at the bottom) | Three icons: Delete (red), Duplicate (blue), Edit (green) |
The three actions on a cardβ
Edit (green pencil icon)β
Click on the Edit icon β you leave the index page and switch to the visual editor of the template:
- Classic Editor (
EDITOR): route/editor/email?id=<id> - AI Editor (
AI): route/editor/ai/email?id=<id>β available in beta in some environments.
Duplicate (blue copy icon)β
Click on the Duplicate icon β opens a window to create a copy of the template. You give a new name to the copy, and an identical template is created.
Use case: you have a great Rosh Hashanah Newsletter template; you duplicate it as Passover Newsletter to start from a polished base and only adapt the visuals and the text.
Delete (red trash icon)β
Click on the Delete icon β a confirmation displays (Are you sure you want to Delete this Email Template?). On validation, the template is deleted.
Rename a templateβ
Click directly on the title of the card. The text becomes inline editable. Modify it, validate with Enter. The new name is saved.
Best practice: use explicit naming that recalls the context:
- β
Monthly Newsletter (Tishrei 5786) - β
Event Invitation β Havdalah - β
Donation Solicitation β Passover Campaign - β
Template 3 - β
Test
Create a templateβ
Click on Add a template (blue button at top right). A window opens with:
- 1
Template Name
Required field. The name that will appear in the grid and in the template selector of campaigns.
- 2
Editor type (visible outside PROD)
Choice between Classic Editor (
EDITOR) and AI Editor (AI). This selector is only visible in non-production environments (staging, test). In production, it's the classic editor by default. - 3
HTML Code (optional)
If you have an HTML email prepared elsewhere (for example retrieved from a third-party tool), you can paste it here. The content will be imported into the visual editor.
Leave empty if you want to start from a blank page.
- 4
Validate
Click on Validate. The template is created in the database. You will be redirected to the visual editor to design it.
Use the ready-made libraryβ
Discover ready-to-use templates opens the Unisoft library. Search and filter by language or category, then preview the subject, preheader, and personalized rendering with your organization's logo and details.
Choose Add to my templates to create an editable copy. Unisoft prevents importing the same library template twice. Adapt its wording, links, and variables, then send yourself a test before using it in a campaign.
Use a template in a campaignβ
Once a template is created and designed, you can use it in any email campaign:
- Go to
/app/messages/campagnes. - Click Create a Campaign (or modify a Draft).
- Choose the Email channel.
- In the Message Content block, the Email template field appears: select your template in the dropdown.
- The HTML rendering of the template will replace the raw Message field on send.
For details, see Create a message campaign.
Available variables in a templateβ
You can insert into a template personalization variables that will be replaced at send by the recipient contact's data.
Examples:
{{prenom}}β replaced by the contact's first name (David){{nom}}β replaced by their last name (COHEN){{mailing_unsubscribe}}β replaced by the personalized unsubscribe link
Special casesβ
- No categorization: templates are not classified in folders or categories. If you have many, count on disciplined naming to find your way around.
- No versioning: if you modify a template, the previous version is overwritten. No version history to restore. In case of risky modification, duplicate the template before.
- No HTML validation: the HTML you import is not syntactically checked. Malformed HTML can produce a broken email. Prefer the visual editor to avoid this risk.
- No integrated multi-language support: each template is in a single language. If your organization sends in English and Hebrew, create two templates (
Newsletter EN,Newsletter HE). - System templates editable: certain templates installed by default (tax receipts, payment confirmations) can be customized by administrators, but it's generally managed in other modules (Payments, Forms) β not from this page.
Going furtherβ
- Email template variables β the exhaustive list of variables by context
- Create a message campaign β how to use a template in a campaign
- Message Campaigns β the overview of the Campaigns module