Email Templates
Templates built from structured blocks, with variables pulled straight from the record, scoped to the object they belong to and rendered into proper email HTML on the server.
Illustrative UI only. Data and individuals shown are fictitious; any resemblance to real persons or data is coincidental.
Blocks, not raw HTML
A template is a sequence of typed blocks, from headings and text to tables, buttons and callouts (more than twenty kinds), so every message comes out consistent without anyone hand-coding markup.
Variables straight from the record
Fields interpolate directly from the record the message is about, and a missing value renders as nothing, so template syntax never leaks into a customer's inbox.
Proven in the everyday outbox
This is the engine behind the routine mail (claim nudges, expiry notices, welcome letters), so templates aren't a demo feature; they're how the platform already talks to customers.
Scoped and switchable
Each template belongs to a record type and carries an active flag. Retiring a message is a toggle that keeps the history, not a deletion that loses it.
Why we like this one
Email templates fail in production, in front of customers. The {{placeholder}} that survived to a policyholder's inbox is a small thing that reads as carelessness. This design gets the order right: templates declare the variables they need, the declaration is checked against the record, and the theme lives apart from the content, so a rebrand is one change, not a re-edit of every message you send.
Book a demo ➝