Advocate Emails (Legacy): Overview
Advocate emails are automatically sent in response to actions taken within advocate accounts and play a crucial role in the functioning of the portal. These emails are created and controlled through the Duel Dashboard.
🗓️ Update, October 2026: this article covers the original (legacy) Duel email system. Most programmes now use Automated Flows: see Advocate Emails: Automated Flows Setup Guide and What Gets Sent and When. For newsletters and digests you design and target yourself, use the Communications Hub if it's switched on for your programme.
If you'd rather send emails from your own CRM, you'll still need Duel's emails for account emails like verification and password resets. Speak to your Brand Partner about what's possible for your programme.
Getting There
Go to Advocates › Groups › Group profiles › select the group profile › Automated Flows.
🚨 See an Emails V2 toggle at the top right? Your programme is still on the legacy emails described here. Ask your Brand Partner before you switch it. If there's no toggle, your programme already uses Automated Flows, so follow the Automated Flows Setup Guide instead.
System Email Breakdown
The table below lists the legacy system emails, what each one does, whether it can be sent from your integrated CRM, and where to find it in Automated Flows. All emails include a CTA to the portal unless otherwise specified.
| Email Name | Function | Outsource to CRM? | In Automated Flows |
|---|---|---|---|
| Digest | Sent to all advocates opted in to communications. It can update advocates on active challenges and recent rewards, or be used for announcements. | ✅ | Digest emails › Digest (only sends when switched on). With the Comms Hub, send digests as campaigns instead. |
| Account verification | Sent to advocates who have submitted the sign-up form, with a link to verify their email address. Sign-ups are queued, so it can arrive after a short delay. | 🚫 | Account emails › Account verification |
| Verification reminder | A follow-up if the advocate hasn't verified their email in time. Same CTA as above. | 🚫 | A reminder on Account verification |
| Password reset | Sent when an advocate asks to reset their password from the login page or inside the portal. | 🚫 | Account emails › Account password reset |
| Email change | Sent when an advocate asks to change their email address from within the portal. | 🚫 | Account emails › Account email change |
| New advocate | Sent to advocates who have signed up, verified their email address and (if enabled) been accepted by your moderation team. | ✅ | Application emails › Application accepted |
| Rejected application | If application moderation is on, lets applicants know they haven't been successful. A link to your FAQs can be added. | 🚫 | Application emails › Application rejected (some programmes have a separate email for each rejection reason) |
| Inactive advocate | Sent when an advocate hasn't completed a challenge within the set timeframe. | ✅ | Account emails › Account inactive |
| Tier up | Sent to advocates who have earned enough points to reach the next tier. | ✅ | Tier emails › Generic tier unlocked, plus an optional override for each tier |
New in Automated Flows: Application resubmission request (sent when an application can't be processed and the advocate is asked to reapply), Advocate details updated, and the Music notice under Challenges emails. See What Gets Sent and When for the full list.
Editing Legacy System Emails
On the legacy system there are two ways to edit these emails.
Edits to default template
Edit the existing template by changing the text or making minor styling adjustments. You don't need HTML knowledge, so there's no need to involve a front-end developer.
Advocate Emails (Legacy): Editing Default Copy
Advocate Emails (Legacy): Digest Copy & Examples
Build from scratch
Create the emails from scratch by removing the default HTML and adding your own code, for complete control over design and layout. This applies to legacy emails only: Automated Flows emails are built from blocks and don't accept raw HTML, apart from a custom digest template.
Using Variables
If you design emails from scratch, you can use the built-in variables to add data dynamically, such as [user:display-name] or [program:name]. Each email lists the variables it supports under its subject line and HTML box.

The legacy email editor, with a custom HTML template selected.