Email branding and templates

Where: Setup → Email Branding and Setup → Email Templates

Sender name and address

What recipients see before they read anything.

Set the From Name to your event or organisation — something the recipient recognises. Set the From Address to a monitored mailbox, because people reply to it whatever you tell them.

A fresh event ships with working defaults, so email sends before you configure anything. Those defaults are generic. Replace them before launch.

Subject prefix

Text prepended to every subject line.

It aids recognition and costs subject-line space, which is scarce on a phone. If your event name is long, a prefix can push the actual subject out of view. Use a short form, or nothing.

Logos and footer

Header left and right logos, and a footer logo.

They render small. A logo with fine detail or small text becomes noise at email size — test it before assuming it works.

A header band appears only once you set logos; an event with none sends a clean, header-free email rather than a broken one. That is deliberate, and it is a reasonable look if you have no good small logo.

The footer carries the organisation handle, social icons and a "powered by" line, each of which can be configured.

Templates

Each message type has its own template. Edit the content, and preview it before saving.

Preview with real data. Templates read very differently with a real name and real numbers than with placeholder text, and it is the only way to catch a token that is not resolving.

Tokens

Placeholders fill in real event and participant data — names, dates, totals, links.

A token with nothing behind it renders empty

It does not fail loudly. You get a sentence with a hole where a number should be, sent to every participant. Never write a sentence that only makes sense once a token resolves, and always preview with real data.

Community and progress tokens pull live figures — the event total, the number of participants. They mirror what the public site shows.

Links in email

Always full URLs including https://. A bare domain is read as a relative path in email and produces a broken link.

This is the single most common defect in event email, and it is invisible in a preview that does not click the link.

Before you launch

Send yourself each of the important templates — confirmation, achievement, any fundraising message — and read them on a phone, where most will be read.

Check the sender, the subject, whether the logo renders, and click every link.