Cresca Templates: Building Emails You Can Reuse
A template is worth building when you will send the same kind of email more than once. The value is not in saving the first hour; it is in removing the decision overhead every time the campaign comes around. This covers how templates work in Cresca and how to keep them from becoming a liability.
When a template is worth building
Build a template when all three are true: the email has a recurring purpose, its structure is stable even though its content changes, and more than one person sends it.
A monthly newsletter qualifies. A product update format qualifies. A one-off launch announcement does not, and a transactional receipt does not need a template so much as it needs to be reliably generated.
The anti-pattern is templating everything. A library of thirty templates that nobody can identify is worse than five that everyone knows, because the first step of every campaign becomes a search.
Structure versus content
The useful way to think about a template is that it fixes structure and leaves content free.
Structure is layout, block order, spacing, the position of the call to action. This should be consistent for a given email type, because consistency is what makes a recurring email recognisable.
Content is the headline, the body copy, the images, the link target. This changes every send.
Templates that try to fix content as well as structure produce the familiar problem of emails that read as slightly wrong versions of each other. Keep placeholders for content and make them obvious.
Generating a template
You can describe a layout and have Cresca generate it, which is useful for the first version of a recurring format. Describe the email's purpose and its intended reading order, then check the result on mobile before saving it. Most layout problems are mobile problems: a two-column block that looks balanced on desktop often stacks awkwardly, and a call to action that is prominent on a wide screen can end up below the fold.
The maintenance problem
Templates decay, and the failure is invisible until a send goes out wrong.
- Broken links. A call to action pointing at a campaign landing page that has been unpublished.
- Stale content. A template with a "join our webinar on March 3" block that nobody replaced.
- Brand drift. The logo changed, the template did not.
- Dead personalisation. A merge field for a data source that was disconnected.
All four are the same underlying problem: the template contains something that is only correct for a period, with nothing indicating when it expires.
Keeping templates healthy
Three habits prevent most of it.
- Keep anything time-bound out of the template. A dated announcement belongs in the campaign, not the reusable structure. If a block is only valid for a month, it should not be in a template that will be reused for a year.
- Review before reuse, not after a mistake. Send the template to yourself and click every link before building on it. This takes a minute and catches the broken-link failure entirely.
- Retire actively. When a recurring email stops being sent, delete its template. A library that only grows is how you end up with thirty.
Templates and AI generation together
The two work well in combination when the division is clear: generate the structure once, save it as a template, then use AI to draft content into it. That keeps the layout stable, which is what makes a recurring email recognisable, while the content stays genuinely new each time.
The reverse, regenerating the layout every send, produces emails that look different each month and reinforces nothing. Consistency in structure is most of the value of having a recurring email at all.
Pricing
Template generation and storage are available on every plan:
| Plan | Price | Contacts | Emails / month |
|---|---|---|---|
| Free | $0 | 50 | 50 |
| Professional | $29/mo | 5,000 | 5,000 |
| Premium | $49/mo | 25,000 | 25,000 |
| Ultra | $99/mo | 55,000 | 55,000 |
Templates and deliverability
A template has a small but real effect on whether mail is delivered, because the HTML it produces is what mailbox providers filter on.
Keep templates simple. Heavy nested tables, large background images and elaborate CSS all reduce the chance of clean rendering across clients, and some filtering looks specifically for those patterns in bulk mail. A template built from straightforward blocks renders predictably and filters cleanly.
Always maintain a plain-text version alongside the HTML. A multipart message has a materially lower spam score than an HTML-only one, and it is what recipients with text-only clients will see. If the template generates one automatically, check it once to confirm it reads sensibly rather than being a stripped tag soup.
Keep images small and hosted on a stable URL. An email whose images load from a temporary path will show broken placeholders in clients that block remote content, which is most of them by default.
Accessibility in templates
Accessibility in email is mostly a template concern, because it is the structural choices that determine whether a message works for someone using a screen reader.
- Real text, not text in images. Text baked into an image cannot be read aloud, resized or translated.
- Alt text on every meaningful image. Decorative images can be marked as such.
- Sufficient contrast. Light grey on white is the most common failure and affects everyone reading in bright light.
- Descriptive link text. "Read the guide" works; "click here" does not when read as a list of links.
- Large enough tap targets. A call to action that is a line of small text is hard to hit on a phone.
Baking these into the template means every campaign built from it inherits them, rather than each one needing a separate accessibility pass.
The short version
Template recurring emails with stable structure, not one-offs. Fix structure and leave content free. Keep anything time-bound out of a template, check links before every reuse, and retire templates when the email stops being sent.
Keep the underlying HTML simple, maintain a plain-text alternative, and build accessibility into the structure so every campaign inherits it. Use AI to generate the layout once and the content every time, never the reverse.
Continue learning
Related Cresca resources
External references