Communications
Email Templates
Email templates are the reusable designs behind every email Forge sends: registration confirmations, waitlist notices, reminders, and one-off announcements. You manage them in the template library at Communications > Templates (also reachable from Global Options > Email Templates and from Manage Templates on an event's Compose tab) and attach them to events from the event's Communications tab.

Template content (subject, preheader, and the email's HTML) is stored in Forge, not in Salesforce. Salesforce receives only a small stub record (the template name and its event) when you switch on an automatic email for an event. Personal data such as names and emails is not stored in the template; it is filled in from Salesforce at the moment each email is sent.
The template library
| Control | What it does | Recommendation |
|---|---|---|
| New Template | Opens the new template page. Enter a Template name and Save; you are taken straight to the editor. | Give each template a descriptive name such as Registration Confirmation - Conference. Only the name is required, so you can save a blank draft and design later. |
| Folders | Lets you group templates, for example by event or lifecycle stage. Click a folder to filter; Rename and Delete work on a folder; All templates and No folder are built-in filters. Deleting a folder that still holds templates asks you to confirm. | Make one folder per campaign or event series so people can find templates fast. |
| Source filter | Filters by where the template came from: All sources, Forge, or Salesforce. A badge on each card shows its source. | Leave on All sources. |
| Template card | Shows the name, a sync status badge (Synced, Syncing, Error, or Draft), the last updated date, the subject line, and a folder picker. Actions are Rename, Edit (opens the editor in the same window), and Delete. | Use the folder picker to file a template without opening it. |
| Select and Delete selected | Tick several cards to delete them together after confirming. | Check that a template is not used by an event's automatic email before deleting it. |
| Packaged templates | Show packaged templates lists the starter templates (confirmation, reminder, receipt, and others). Add puts a copy in your library; a starter you already added shows Added. | Add the starters you need, then edit the copies. Every org can add them, whenever it started using templates. |
Creating a template
- Go to Communications > Templates and choose New Template.
- Enter a Template name and choose Save. The editor opens on the Details step.
- On Details, set the Subject line, optional Preheader, From, Reply-to, and Folder (see the table below). Use Insert merge to personalize the subject and preheader.
- Choose Next: Design Email and build the email in the visual editor.
- Use Preview with data to render it for a real attendee or event, and Send test to receive it. Then Save. Unsaved changes are flagged.
| Setting | What it does | Recommendation |
|---|---|---|
| Template name | An internal name used in pickers across Forge. Required. | Describe the purpose and event, not the subject. |
| Subject line | The subject recipients see. Merge fields are allowed, for example Your ticket for {{EVENT_NAME}}. | Keep it short and specific. Put the event name in so people can tell events apart. |
| Preheader | Optional preview text shown after the subject in most inboxes. | Use one short sentence that adds information, not a repeat of the subject. |
| From | Default (tenant settings) uses the From name and address set in Admin > Email. Custom address lets this template use its own friendly name and sender email. | Leave on Default. Use Custom only for a template that must come from a different address, and make sure that address is verified. |
| Reply-to | Optional address for replies. Blank means replies go to the From address. | Set a monitored shared inbox if the From address is a no-reply. |
| Folder | Organizes the template in the library. | Use folders; the library grows quickly. |
The visual editor
Templates are designed in a drag-and-drop email editor. Add rows and content blocks (text, images, buttons, dividers, and more), style them, and see a live preview. A brand kit from Admin > Email > Brand Settings supplies your logo, colors, and font. Templates created before the current editor open in a legacy block editor with an Upgrade to the visual editor prompt.
- Insert merge: a merge-tag menu in the editor and in the subject and preheader boxes inserts tokens. Tokens are listed in Merge fields below.
- Special links: Unsubscribe and Manage Preferences links are available as special links in the editor. Add them where you want them; if a template has no Unsubscribe link, Forge appends one at the bottom when sending.
- Dataset grids: drop in event data tables for Speakers, Sponsors, Sessions, Invoice header, Invoice line items, Attendee tickets, and Session attendees. They fill from the event chosen at send time, show at most 15 rows, and show a clear message when the data is missing or fails to load.
- Add to calendar: a calendar block adds Google, Outlook, and Yahoo buttons plus an ICS download. The buttons work when the email is tied to an event with start and end times.
- Preview with data and Send test: render with a real attendee or event. Test sends are not personalized, so use Preview to check merge fields.
Merge fields (personalization tokens)
Merge fields are written between double curly braces and filled in when each email is sent. There are three ways to write them, and all of them work.
| Style | Examples | Recommendation |
|---|---|---|
| Friendly names | {{ATTENDEE_FIRST_NAME}}, {{ATTENDEE_LAST_NAME}}, {{ATTENDEE_NAME}}, {{ATTENDEE_EMAIL}}, {{EVENT_NAME}}, {{EVENT_START}}, {{EVENT_END}}, {{EVENT_LOCATION}}, {{REGISTRATION_LINK}} | Use these for most templates; they are the ones in the editor's tag menu. |
| Dotted names | {{Attendee.FirstName}}, {{Attendee.LastName}}, {{Attendee.Email}}; the same pattern works for Event and Session fields | Pick them from the Insert merge menu, which lists fields from Attendee, Event, and Session. |
| Salesforce field names | {{conference360__Event_Name__c}} | Use only for a field the menus do not offer. |
| Token | Inserts |
|---|---|
| {{ATTENDEE_FIRST_NAME}}, {{ATTENDEE_LAST_NAME}}, {{ATTENDEE_NAME}}, {{ATTENDEE_EMAIL}} | The recipient's first name, last name, full name, and email. |
| {{EVENT_NAME}}, {{EVENT_START}}, {{EVENT_END}}, {{EVENT_LOCATION}} | The event's name, start, end, and location. |
| {{REGISTRATION_LINK}} | The recipient's personal registration link (their Attendee Link). |
| {{AttendeeLink}} or {{conference360__AttendeeLink__c}} | The Attendee Link. Required in any template used for the Registration confirmation trigger. |
| {{TICKET_NAME}}, {{REGISTRATION_ID}} | Ticket and registration details, offered in the editor's tag menu. |
| {{INVOICE_NUMBER}}, {{INVOICE_TOTAL}}, {{INVOICE_DUE_DATE}}, {{INVOICE_BALANCE}} | Invoice details, offered in the editor's tag menu for receipt-style emails. |
| {{UNSUBSCRIBE_LINK}}, {{MANAGE_PREFERENCES_LINK}} | Per-recipient unsubscribe and preference links. |
| {{SESSIONS_LIST}}, {{LINE_ITEMS_TABLE}} | A per-recipient list of sessions and a table of order line items. |
A token Forge does not recognize is left in the email exactly as typed, so a typo shows up in the inbox. Always run Preview with data before enabling an automatic email. Values are inserted as safe text, so HTML typed into a field is not rendered.
Merge fields are filled from Salesforce at send time and are not stored. Avoid putting sensitive financial or health details in email copy.
Using templates
- Automatic emails: on the event's Communications > Notifications tab, choose a template for each trigger (registration confirmation, waitlist, cancellation, and so on).
- One-off and scheduled sends: choose the template on the Compose tab's Message step.
- A Registration confirmation template must contain the Attendee Link merge field; templates without it are not offered for that trigger.
- A template has one language. To email in several languages, create one template per language and pick the right one per event or send.
Two people editing the same template at once is not locked: the last save wins. Agree who edits a template before changing one that is in use.
Shared templates
Templates are shared across your whole organization. When you open an existing template, the editor shows Used by N, which lists every event, scheduled email and journey that uses it. If you save a template that other events or scheduled emails use, Forge asks you to choose Apply to all events or Save a copy for this event only. The copy moves only this event's emails to the new template; other events keep the original. The prompt names any scheduled email the change would affect. Opened from an event, the template library also has Copy for this event on each template.