Email Builder and Broadcasts

The email module is two things that share an editor. The builder produces reusable templates (drag-and-drop layouts, saved sections, plain-text variants) that workflows, calendars, invoices and campaigns all draw on. The broadcast sends one of those templates to a chosen audience at a chosen time, as a deliberate act rather than an automated one.

The distinction matters because the two fail differently. A template fault repeats silently in every automated send until someone notices a broken link in a confirmation email. A broadcast fault is loud, immediate and public: the wrong segment, the wrong subject line, the unmerged first name sent to thousands of people at once and impossible to recall.

Underneath both sits the part that actually determines whether any of it works: the sending identity. A verified domain with properly published authentication records, a sending reputation built slowly, a clean list and a visible unsubscribe are what put mail in an inbox. Without them the prettiest template in the account lands in spam, and no amount of design work fixes it.

The builder

• Drag-and-drop sections, columns, spacers and dividers, with mobile behavior per block
• Text, image, button, video thumbnail, social icon and custom HTML blocks
• Saved sections and reusable headers and footers shared across templates
• Brand styling: fonts, colors, button shapes and global padding applied once
• Plain-text alternative, which some recipients and most filters prefer to exist
• Starting templates, cloning an existing email, and importing HTML built elsewhere
• Drafting and rewriting help from the AI content assistant for subject lines and body copy

Personalization and dynamic content

• Merge fields for contact, appointment, opportunity, invoice and custom values, each with a fallback
• Conditional sections shown or hidden by tag, field value or segment membership
• Dynamic links such as booking links, portal links, payment links and review links
• Trigger links that fire a workflow when clicked
• Preheader text, which is read by the recipient far more often than the designer expects

Broadcast setup

• Audience selection from lists, smart lists, tags or saved segments, with explicit exclusions
• Send now, schedule for a date and time, or send in each contact's own timezone
• Batching and throttling so a large send is spread rather than dumped in one minute
• Subject line and preheader testing, including A/B splits where the send is large enough to learn from
• From name, from address and reply-to address, which need not be the same
• Suppression of unsubscribed, bounced, complained and duplicate addresses
• Test sends to seed addresses, and a final preview across desktop and mobile widths

Sending infrastructure

• A verified sending domain or subdomain, with the authentication records published in DNS
• A dedicated or shared sending identity, and the warm-up ramp that follows
• Custom tracking domain so click links carry the client's brand
• A hosted preference or unsubscribe page, and what the unsubscribe actually does: all mail, or one category
• Separation of transactional and marketing sending where the client's volume justifies it

Reporting

• Delivered, opened, clicked, bounced, complained and unsubscribed per send
• Click maps by link, so you can tell which call to action did the work
• Per-contact engagement history visible on the record and usable in smart lists
• Hard and soft bounce separation, and automatic suppression of repeated failures
• Workflow triggers on email opened, link clicked, bounced and unsubscribed

1. Set up the sending domain before you design anything. Use a subdomain for marketing mail so the client's main domain reputation is insulated, and publish every authentication record the platform asks for.
2. Verify the records actually resolve from outside your own network, then send a test to addresses at more than one major mail provider and check the headers show the mail as authenticated.
3. Add the custom tracking domain so click links carry the client's brand rather than a generic host. Unbranded tracking links cost clicks and attract filtering.
4. Decide the from name, from address and reply-to, and make the reply-to a mailbox a human reads. A no-reply address on a small business's mail is a missed conversation and a deliverability signal.
5. Build the brand shell once: header, footer, colors, fonts, button style, address block and unsubscribe. Save it as the base every other template clones from.
6. Build the transactional templates first (appointment confirmation, reminder, invoice, password or portal access) because these are the emails that must never break.
7. Add merge fields with fallbacks and then test a contact whose fields are empty. Half the embarrassment in email marketing is an unmerged placeholder.
8. Create the plain-text alternative rather than letting it be generated badly, and read it. If it makes no sense without the images, neither does the email.
9. Clean the list before the first broadcast. Remove role addresses, obvious typos, long-dead domains and anything with no recorded consent, and keep the evidence of where the consent came from.
10. Warm the sending identity. Start with the most engaged contacts in small volumes and increase over days. A first send to an entire cold list is how a new domain gets burned.
11. For each broadcast, define the audience as a saved segment with explicit exclusions, then read the recipient count out loud and sanity-check it before going further.
12. Write the subject line and preheader as a pair, keep both short enough to survive a mobile inbox, and avoid the words that read as a sales shout.
13. Send seed tests to accounts on at least three mail providers and open them on a phone. Check images-off rendering, dark-mode rendering, every link and the unsubscribe.
14. Schedule with throttling, in business hours for the recipient, and never schedule a large send for a time nobody will be around to watch it.
15. Watch the first batch's delivery, bounce and complaint figures before the rest goes out, and be prepared to stop. A rising complaint rate early is a reason to cancel, not to continue.
16. Process the results: suppress hard bounces, review unsubscribes for a pattern, and feed clicks and opens into the smart lists that drive the next send.
17. Keep a sending calendar per account. Deliverability damage usually comes from frequency nobody planned, not from one bad email.

Email is the module almost everything else borrows. Calendars send confirmations through it, payments send invoices and receipts, memberships send access details, funnels and forms feed its lists, workflows send the sequences, and reporting reads its engagement data back into segmentation. In practice the template library is shared infrastructure: build it well once and every other module inherits a competent-looking business.

Lead magnet to nurture

A form on a funnel page delivers a download by email from a transactional template, then enrolls the contact in a short educational sequence. Clicks on a specific link tag the contact with the service they care about, and the final email offers the booking link for that service. The nurture exits the moment an appointment is booked.

Monthly newsletter that earns its place

A broadcast goes to a segment of contacts who have opened something in the last few months, excluding anyone with an appointment in the next week so the message does not collide with reminders. Conditional sections show different offers by service interest, and click data updates the segments that drive next month's send.

Invoice and receipt chain

Payments issues an invoice through an email template, a workflow chases politely at intervals if it is unpaid, and a receipt follows on payment. Because all three use the same brand shell and the same verified domain, the money emails look like they came from the same business as the marketing, which is exactly the point.

• Authentication records are not optional any more. Major mail providers now reject or bulk-folder unauthenticated mail from any sender at volume. If the records are not published and valid, nothing else you do matters.
• A broadcast cannot be recalled. Once it is sending, the only remedy is to stop the remainder and apologize. Read the recipient count and the subject line twice.
• Open rates are no longer reliable. Privacy features on major mail clients pre-fetch images, inflating opens and sometimes firing open-based automation for people who never read the message. Trigger on clicks and replies instead.
• Marketing volume on the main domain damages the client's business mail. A reputation hit can put their invoices and staff email in spam. Always send marketing from a subdomain.
• Dark mode and images-off break designs. Pale logos vanish, text on colored backgrounds inverts badly, and image-only emails become blank. Test both states.
• Images-heavy emails with little text look like spam to filters. Keep a real text-to-image balance and never put the offer only in a picture.
• Unsubscribe must be real and honoured everywhere. A contact who unsubscribes from marketing can still legitimately receive transactional mail, but confusing the two either suppresses necessary mail or breaks the law.
• Sending to an inherited or purchased list will burn the domain. Complaints arrive within minutes and the damage is slow to reverse. Decline the send rather than wear the consequence.
• Hard bounces must be suppressed, not retried. Repeated sending to dead addresses is one of the clearest negative signals a provider measures.
• Soft bounces hide real problems. A full mailbox and a blocked sender can look alike in the report. Watch the pattern by recipient domain, not by individual.
• Template edits propagate to live workflows. Changing a shared confirmation template changes it for every automation using it, including sequences people are mid-way through.
• Custom HTML can break the builder. Imported or pasted code often cannot be edited visually afterwards, and may render unpredictably across clients.
• Reply-to addresses nobody monitors lose business. People reply to marketing email with real questions, and those replies have to reach a person.
• Timezone-aware sending spreads the send over a day. That is usually desirable, but it means the report is incomplete for hours and a mistake keeps sending while you discover it.
• Deleting a template that workflows reference breaks those steps. The workflow often continues without warning and the contact simply receives nothing.