Manage email templates, reminders, and delivery
Configure compliance communications and investigate delivery outcomes.
Table of Contents
In admin view, open System → Email. Email administration has seven sections: Emails, Sender, Branding, CC recipients, Approval reminders, Send controls, and Delivery records. The controls available to you depend on your permissions.
Find the right template and trigger
- In System → Email, open Emails.
- Search by name, or filter by Trigger and Status.
- Review Used by to see campaign dependencies or whether the message applies wherever its trigger fires.
- Open a platform-default row to inspect its sample message, trigger details, and dependencies. Preview names and values are illustrative.

A platform-default message is the fallback when no custom message has been selected. If no published email is available for a trigger, its Sending template control shows Built-in email and is disabled.
Choose the trigger that matches the event
| Trigger | What it is for |
|---|---|
| Approval Assignment | Notifies an approver of an assigned step that is not active yet. |
| Approval Request | Asks an approver to act on an active, pending approval step. |
| Approval Reminder | Reminds an approver about due pending approvals. Configure the cadence in Approval reminders; one email aggregates the requests due for that approver. |
| Campaign Reminder | Reminds recipients who have not completed an active campaign. Configure this in the campaign builder. |
| Manager Escalation | Escalates a campaign recipient's outstanding response to their manager through the campaign configuration. |
| Task Due Soon / Task Overdue | Notifies the task assignee about an approaching or missed task due date. These are distinct from approval reminders. |
A template does not create an event. Each email belongs to one trigger. Quantum does not send emails for Campaign Closed, Disclosure Received Confirmation, and Overdue Notice. Creating a template for these triggers does not cause delivery. Task Overdue is a separate trigger from Overdue Notice.
Create and review a custom template
- In Emails, select New template.
- Choose the Trigger for the event you want to communicate. Enter a recognizable Name; it initially defaults to the trigger name.
- Select Create template. Quantum opens a draft based on that trigger's platform-default message.
- Review the name and, if helpful, add a Description. The description is for internal use.
- In Template languages, select the source language. Edit the Subject and message body.
- Use Variable to insert available dynamic values, such as the record reference, rather than typing invented variable names. Review any action button and its destination using the Button control.
- Use the formatting toolbar for headings, lists, and emphasis. The logo, brand color, and footer belong to the shared branding shell; use Change in Branding to manage them centrally.
- Wait for Saved before leaving the editor. Saving keeps your work as a draft.

Review language versions
Use the language’s translation workspace to review the source and translated email content, including the email footer. Save draft wording, review it and approve the intended translation; check publication separately. See Manage languages and localization for the workspace and review workflow.
The language list shows the versions available in your workspace and their status. Review each language your recipients need. Draft all missing languages with AI can help create missing versions; review the resulting wording, variables, and action links before publication. Languages shown in the screenshot are examples and may differ in your workspace.
Preview, publish, and select the message
- Select Done to open the rendered preview. Done does not publish the draft.
- Check the subject, body, button, branding, and footer. The preview uses sample recipient and record values; it is not evidence that an email was sent.
- Use Edit email to make corrections. Repeat the review for the language versions you intend to use.
- When the content is ready, select Publish and verify the resulting status and version.
- Return to the relevant trigger's platform-default detail page and check Sending template. Select the intended published custom template where this control is available. For campaign messages, also check the template selected in the campaign configuration.
- After the relevant event occurs, use Delivery records to confirm the actual recipient, rendered message, and delivery status.

Saving, previewing, publishing, and selecting are different actions. A saved draft is not a sent email. Publishing makes the reviewed version available; the applicable selection and triggering event determine which message is used.
Configure the sender
- Open Sender and review What recipients see.
- Enter a Display name and approved Reply-to address, then select Save sender identity. The display name is the name on outbound email. If Reply-to is empty, replies go to an unmonitored mailbox.
- Under Sender identities, choose Domain or Email address to use an identity your organization owns.
- For a domain, use an approved subdomain and coordinate the displayed DNS records with IT. Domain verification is the recommended option. Email-address verification instead requires the mailbox owner to confirm by link; deliverability also depends on the domain's DMARC policy.
- Complete verification and check the identity's status before relying on it.
Use the records and addresses provided for your own workspace. Do not copy another environment's sender or DNS configuration.

Configure branding
- Open Branding.
- Set Logo URL, Primary color, Accent color, and Footer text.
- Review the Preview, which shows the shell of your compliance emails, then select Save branding.

Configure CC recipients
CC rules copy designated addresses on every email of a selected type. They are configured by email type, rather than for an individual delivery.
- Open CC recipients and find the relevant email type. Read its description to confirm the event.
- Select the row's Edit CC action.
- Enter one address per line, up to 10 addresses.
- Select Save CC recipients. To stop copying anyone for that type, clear the list and save.
Plan for volume and access: each individual message sends its own CC copy. A campaign email sent to 100 people can therefore generate 100 copies for each configured CC address. Choose only recipients authorized to receive the content of that email type.

Configure approval reminders
Each approver receives one reminder email listing the requests waiting for their decision.
- Open Approval reminders and enable Send approval reminders when ready.
- Set First reminder after (days): how long a request waits at the approver's step before its first reminder.
- Set Repeat every (days): the interval between reminders while the decision remains pending.
- Set Maximum reminders: the limit for each step an approver is waiting on.
- Select Save approval reminders.
Approval reminders follow Send controls. When reminders are suppressed, they are recorded but not sent. Campaign reminders are configured separately in the campaign builder.

Pause email with send controls
Open Send controls to temporarily withhold categories of email for the organization.
- Suppress transactional email: decisions, update requests, campaign launches, and collaboration notices are recorded but not sent.
- Suppress reminders: campaign reminders, approval reminders, manager escalations, and overdue notices are recorded but not sent.
- Enable the appropriate suppression switch or switches.
- Enter a Reason. This is required while either switch is on, and appears on withheld emails recorded in Delivery records.
- Select Save send controls.
- When the pause is over, turn off the relevant suppression switches and save again.
Exceptions: invitations and password resets always send.

Investigate delivery
- Open Delivery records. Search and use the Type, Status, and Recorded filters to find the relevant message. The list shows recipient, type, status, attempt, and recorded time.
- Open a row to review the Recipient, CC, Subject, Language, Attempt, and Content hash.
- Inspect the Rendered email and Delivery lifecycle. For example, a record can show Queued, Sent, and Delivered with separate timestamps. Sent and Delivered are distinct states; neither confirms the recipient read the message.
- If delivery is missing or withheld, check the triggering event, selected message, sender configuration, and Send controls, including any recorded suppression reason.
- If a resend is needed and your permissions allow it, review the intended recipient and content before selecting Resend and following the confirmation flow. A resend is another delivery attempt.
Delivery records are immutable: records cannot be edited or deleted. Use the record as evidence of the specific message and its lifecycle.

Troubleshoot common email questions
| What you see | What to check |
|---|---|
| The built-in message is still being used | Confirm that your custom template is published for the correct trigger, then check Sending template or the campaign's selected message. |
| A template exists, but no email arrives | Confirm that an active trigger occurred. Check sender verification, Send controls, and Delivery records. Inactive triggers do not send emails, even when a template exists. |
| An approval reminder has not arrived | Check whether approval reminders are enabled, the first delay and repeat interval, the maximum reminders per step, and reminder suppression. Remember that due requests are aggregated by approver. |
| A campaign reminder is not behaving as expected | Review the campaign's reminder settings and recipient completion state. Approval reminders does not configure campaign reminders. |
| A message was withheld | Review the suppression reason and Send controls. Ending a pause should not be treated as an automatic resend of earlier messages. |
| The record says Delivered, but the recipient cannot find it | Verify the recipient address and delivery lifecycle, then ask the recipient to check junk mail and their organization's mail filtering. Delivered does not prove the email was read. |
Expected result
Your program uses the intended message for each active trigger, an appropriate sender and email design, authorized CC recipients, an agreed reminder cadence, deliberate send-control settings, and delivery records that support troubleshooting.