Interactive Email Workflows for Agencies

Your tenth client email should take a fraction of the time the first one did. Save your best builds as private templates for the whole team, give each client its own company with its own plan, domain and payments, move between them from one login, and send from each client's own domain or through the ESP they already use.

Subject

Your weekend flash sale is live

Save your best builds as private templates for the whole team, run each client in its own company from one login, and deliver every email from the client's own domain or through the ESP they already use.

An agency's tenth interactive email should take a fraction of the time the first one did. The work worth keeping is the structure: the layout, the blocks and the way a campaign reaches its goal.

Save the structure, reuse it for every client

Open a finished build in the studio, click Save as template and keep it Private. Everyone on your team finds it under My team's templates when they start a new email. One-time details, such as a meeting's join link or a countdown's date, are cleared, so each client's version starts fresh. Change the theme in Design and every block takes the client's colors and fonts. See Templates.

Smaller pieces you reuse inside emails, such as a header or a coupon section, work the same way with Save as component.

One login, every client

Give each client its own company, with its own plan, contacts, sending domain and payments account. Your staff accept an invite to each company and move between them with the company switcher in the sidebar, from a single login. See Team collaboration.

Prefer one shared account? Departments give each client team its own emails and shared mailboxes, and a department lead can invite people into their own department.

Invite each person with the right role. Editors build, send and read results. Viewers review everything without changing it. Credentials, billing and the team itself stay with the account owner.

Deliver on the client's brand

Verify each client's domain and create a sender identity per brand, so every email comes from the client's own address. A custom tracking domain puts the client's domain on every link, and a custom portal domain does the same for landing pages and the member portal. Multi-brand sending for agencies walks through the setup.

When a client keeps its own ESP, Export compiles the email into one HTML file to paste there, and answers still come back to the email's Insights. See Export & send with your ESP.

Report back to the client

Each email's Insights shows opens, clicks, answers and orders, and downloads as a PDF report. On Business and above, the report carries the company's name instead of MailInApp's, so a client company's reports show the client's name.

Getting started

Build a shell, Save as template as Private, invite your team under Settings → Team, and set up a company or a department for each client. Then send from the client's domain or export to their ESP.

Watch: book calls and get client sign-offs by email

A creative agency connects its client list, its calendar and its team, then lets clients book a call, pick a direction and approve the work with one tap from the inbox, with every answer in Insights.

A typical build-and-send sequence

  1. 1

    Build the structure once

    Design a shell with your layout and blocks, then change the theme and copy for each client.

  2. 2

    Save it as a private template

    Click Save as template and keep it Private. Everyone on your team finds it under My team's templates.

  3. 3

    Set up each client

    Create a company per client, or a department per client team in one account, and invite your staff with the right role.

  4. 4

    Deliver on the client's brand

    Send from the client's verified domain and sender identity, or export the HTML for the ESP they already use.

Frequently asked questions

Who can see our private templates?

You and your teammates. A private template lives in your account, like your emails, and appears under My team's templates for everyone on your team.

What can a teammate do?

An editor builds, sends and reads results everywhere in the account. A viewer reviews everything without changing it. Credentials, billing and the team itself stay with the account owner.

Should each client have its own account?

Give a client its own company when it needs its own plan, its own Stripe account for checkout or its own sending setup. Your staff accept an invite to each company and move between them with the company switcher in the sidebar, from one login.

Can one account keep client teams apart?

Yes. Departments decide which emails and shared mailboxes each teammate sees, and a department lead can invite people into their own department.

How do we hand an email to a client's own ESP?

Export compiles the email into one HTML file to paste into the client's ESP, and answers keep coming back to the email's Insights. Each plan includes a number of exports a month.

Can client reports carry the client's name?

Yes. On Business and above, the PDF report of an email's Insights carries the company's name instead of MailInApp's, so a client company's reports show the client's name.

Should we publish agency templates to the community gallery?

Keep agency templates Private: they keep your merge-tag defaults and stay with your team. Public templates go to the community gallery after review, with merge-tag defaults blanked, which suits a template made for everyone.

Build this in the studio

Start on the free plan — every interactive block and the full fallback engine are included on every tier.