Starter templates & your own library
Every new project can start from a real template instead of a blank canvas — either one of MailInApp's own, or one you or a teammate saved earlier.
Browsing starter templates
From the dashboard, + New email opens a two-step picker. First, choose a topic: survey, promotion, newsletter, event, transactional, dashboard, classroom, or sports team. Then browse that topic's 3-4 starter templates one at a time in a carousel. What you see is a real, large preview of the actual email, not a mockup, rendered through the same pipeline that produces the email your recipients get.
Step through with the ‹ › arrows and click Use this template when one fits, or pick Start blank on the first step to skip templates entirely. Either way it's just a starting point: every block stays fully editable. Picking a template only sets the project's purpose, which headline metric your Responses dashboard leads with — it never restricts which blocks you're allowed to use.
Saving your own
Built an email worth reusing? Open it in the studio and click Save as template in the toolbar. Give it a name and description, and choose who can see it:
- Private — visible only to you and your team, right alongside the built-in topics in the My team's templates entry of the picker. If you've invited teammates (see Team collaboration), they see it too — there's no separate sharing step.
- Public — submitted to MailInApp's community gallery, browsable by every user under Community templates. Public templates need a MailInApp admin to approve them first, so it won't appear immediately; you'll see it as soon as that happens.
Either way, a few things are cleared automatically because they wouldn't make sense to reuse. That includes a product block's real delivery code, a meeting block's real join link and dial-in, and any date on a countdown, assignment, or calendar-event block. Publishing publicly also blanks your merge-tag variables' default values — those are meant as blank placeholders for whoever uses the template next, not a way to carry your own defaults out to everyone else.
Tip: a saved template is a snapshot, not a live link back to the project — editing the original afterward never changes the template, and there's no "update" action. To refresh one, save a new template from the project's current state and delete the old one.
The community gallery
A public template stays out of the gallery until an admin reviews it — the same manual check MailInApp already uses for things like disputed payments, rather than automated content scanning. Once approved, anyone can report a template that shouldn't be there; enough reports pull it back out of the gallery automatically pending another look. Publishing counts against a per-plan limit — see pricing for how many public templates each tier allows.
Reusable components vs. templates
Don't confuse this with Save as component in the Inspector's Actions tab (see Reusable components) — a component is one saved piece (a header, a coupon section) you drop into a project you're already building. A template is a whole starting project, picked once, at creation time.