---
title: Email notifications
description: >-
  Understand automatic confirmation emails, decision review emails, in-app
  notifications, and staff reminder emails sent to applicants in Fuxam Apply.
sidebar:
  order: 2
---

Fuxam Apply sends email to applicants at key points in the admissions lifecycle. **Confirmation emails** acknowledge successful submission. **Review emails** communicate decisions and field-level feedback when staff change application status or complete review. **In-app notifications** reach applicants who have Fuxam accounts. **Reminder emails** let staff nudge applicants about outstanding conditional requirements.

Administrators do **not** configure separate email templates on the Apply settings page — emails are generated from built-in review and confirmation flows. Understanding what sends automatically — and what requires a manual [Send email](/docs/fuxam-web/apply/applicants/communicate-with-an-applicant) action — helps admissions teams set applicant expectations and avoid duplicate or conflicting messages.

## Why it matters

Applicants judge an institution partly by how clearly and promptly they are kept informed. Automated emails provide a consistent audit trail: receipt on submit, structured decision language on status change, and field comments when review used per-field feedback. That reduces "did you get my application?" inquiries and gives staff confidence that the official decision reached the applicant's inbox.

Because template content is system-generated, admissions training should focus on **when** emails fire (status values, **Complete review** confirmation) rather than editing wording in a settings screen. For messages outside those triggers — interview invitations, orientation logistics, informal clarifications — use manual communication documented separately.

There are three channels: automatic on submit, automatic on decision, and staff-initiated (manual email or **Pending requirements** reminders). Decision workflows are detailed in [Approve or reject](/docs/fuxam-web/apply/applicants/approve-or-reject); manual email in [Communicate with an applicant](/docs/fuxam-web/apply/applicants/communicate-with-an-applicant).

| Email type | Trigger | Administrator action required? |
|---|---|---|
| **Confirmation email** | Successful form submission | No — automatic |
| **Review email** | Decision status change or **Complete review** | Yes — staff sets status or confirms review |
| **In-app notification** | Status change or field deadline milestones | No — automatic for account holders |
| **Reminder email** | Staff action in **Pending requirements** | Yes — manual per applicant or batch |
| **Manual email** | **Send email** composer | Yes — staff composes message |

## Key concepts

| Term | Meaning |
|---|---|
| **Confirmation email** | Receipt sent once when the applicant successfully submits; duplicates are prevented automatically. |
| **Review email** | Decision notification with program name, form name, outcome, and field comments when applicable. |
| **Application status update** | In-app notification type when submission status changes. |
| **Application field deadline** | In-app reminder type for conditional requirements — set, 7-day, 1-day, and overdue variants. |
| **Pending requirements** | Campus Management view (when available) for tracking outstanding conditional items and sending reminders. |

Review emails are **not** sent for **Draft** or **Pending** statuses. Those values represent in-progress or not-yet-submitted work, not admissions decisions.

## Submission confirmation email

When an applicant **successfully submits** an application form through the Apply portal:

- Fuxam sends a **confirmation email** to the address they provided.
- The email confirms receipt and references next steps (also shown on the on-screen success page).
- Each submission receives at most one confirmation email (duplicates are prevented automatically).

No administrator action is required to trigger confirmation emails.

:::success
Confirmation email is the applicant's proof of submission. Direct them to check spam folders if they do not receive it, and verify the email field they entered on the form before resubmitting.
:::

The same confirmation behavior is referenced in [Configure program settings](/docs/fuxam-web/apply/application-programs/configure-program-settings) — it applies per published form regardless of program-level deadline configuration.

## Decision and review emails

When an administrator **changes application status** or **completes a field review**, Fuxam may send a **review email** to the applicant containing:

- Program and form name
- Decision outcome (accepted, rejected, needs update, etc.)
- Field-level comments when field review was used

Review emails are **not** sent for **Draft** or **Pending** statuses. Bulk status updates send individual review emails per affected submission.

Completing review from the applicant detail sheet prompts for confirmation before sending.

:::warning[Confirm before sending]
The confirmation step on **Complete review** is deliberate — it is the last check before decision language and field comments reach the applicant. Cancel if you need to revise feedback first.
:::

### When review emails send

| Administrator action | Review email? |
|---|---|
| Set status to **Accepted**, **Rejected**, **Needs update**, etc. | Yes — for decision statuses (not Draft or Pending) |
| **Complete review** after per-field review | Yes — after confirmation |
| Bulk status update on multiple rows | Yes — one email per affected submission |
| Manual **Send email** only | No — that is a separate manual channel |
| Status **Draft** or **Pending** | No |

For the full decision procedure and status selector behavior, see [Approve or reject](/docs/fuxam-web/apply/applicants/approve-or-reject) and [Bulk process applications](/docs/fuxam-web/apply/applicants/bulk-process-applications).

## In-app notifications

Alongside email, applicants with Fuxam accounts receive **in-app notifications** for status changes. Notification types include:

- **Application status update** — when their submission status changes
- **Application field deadline** reminders — when conditional requirements have due dates (set, 7-day, 1-day, and overdue variants)

Users control whether they receive these notifications in their personal notification preferences.

:::note
In-app notifications complement email; they do not replace it. Applicants without Fuxam accounts rely on email (and the **My Submissions** portal view) for updates until they create or link an account.
:::

Field deadline reminders tie to conditional requirements tracked during admissions — often after **Conditionally accepted** status. Submission deadlines configured on forms are separate; see [Configure program settings](/docs/fuxam-web/apply/application-programs/configure-program-settings) for application window behavior.

## Administrator reminders

The **Pending requirements** view (when available in Campus Management) lets staff send **reminder** emails to applicants with outstanding conditional items or extend field deadlines. These are manual actions separate from automatic status emails.

Use reminders when an applicant has accepted conditions but has not yet uploaded a document, signed a contract, or met another field-level requirement. Extending a deadline updates the timeline applicants see and may affect which **Application field deadline** in-app notifications they receive.

:::tip
Pair reminders with clear status context. If the applicant must edit their submission, set **Needs update** status (which triggers a review email) rather than relying only on a manual reminder — see [Review an application](/docs/fuxam-web/apply/applicants/review-an-application).
:::

## Automatic vs manual communication

| Situation | Recommended approach |
|---|---|
| Applicant just submitted the form | Automatic **confirmation email** — no action needed |
| Official accept, reject, or needs update decision | Change **Status** or **Complete review** — triggers **review email** |
| Informational message not tied to a decision | [Communicate with an applicant](/docs/fuxam-web/apply/applicants/communicate-with-an-applicant) — manual **Send email** |
| Outstanding conditional document or deadline | **Pending requirements** reminder (when available) |
| Bulk decision on many files | [Bulk process applications](/docs/fuxam-web/apply/applicants/bulk-process-applications) — individual review emails per row |

Manual email does not change application status and does not trigger review email wording. Decision by email alone — without updating status in Campus Management — leaves **My Submissions** out of sync with what the applicant was told.

## Best practices

- **Train staff on status values** — Review emails follow status changes. Using **Draft** or **Pending** when a decision is intended will not notify the applicant.
- **Use Complete review for field feedback** — Ensures field-level comments appear in the structured review email rather than only in internal notes.
- **Avoid duplicate messaging** — After a status change, do not immediately send a manual email repeating the same decision; check what the review email already includes.
- **Set expectations at submission** — The confirmation email and success page define "what happens next"; align internal SLA with that messaging.
- **Document reminder policy** — When **Pending requirements** is available, agree when staff send reminders vs when they escalate to **Needs update** or **Rejected**.

## Common pitfalls

- **No review email for Draft or Pending** — These statuses are intentionally silent. Move the submission to a decision status when applicants should be notified.
- **Bulk update surprise** — Bulk status changes send one review email per applicant. Preview your selection before confirming large batches.
- **Manual email mistaken for decision** — Applicants check **My Submissions** for official status. Email alone does not update the pipeline.
- **Missing email address** — Manual **Send email** is blocked when no valid addresses exist; verify contact data in the detail sheet during [review](/docs/fuxam-web/apply/applicants/review-an-application).
- **Assuming custom templates** — Wording is system-generated. Plan communications that work with standard review email content, or supplement with manual email for institution-specific detail.

## FAQ

**Can I edit confirmation or review email templates in Apply portal settings?**

No. Administrators do not configure separate email templates on the Apply settings page. Emails are generated from built-in confirmation and review flows.

**Will an applicant get two confirmation emails if they resubmit?**

Each submission receives at most one confirmation email, with duplicates prevented automatically. Resubmission behavior after **Needs update** follows the review workflow — see [Approve or reject](/docs/fuxam-web/apply/applicants/approve-or-reject).

**Do bulk status updates send one email or one per applicant?**

Bulk status updates send individual review emails per affected submission.

**What is the difference between review email and manual Send email?**

**Review email** is automatic when you set a decision status or complete field review. **Send email** is staff-initiated through the composer and does not change status or use the review email template.

**Do in-app notifications always mirror email?**

Not necessarily. Applicants with Fuxam accounts receive in-app notifications according to their personal preferences. Email and portal status remain the primary channels for applicants without accounts.

## Related pages

**[Approve or reject](/docs/fuxam-web/apply/applicants/approve-or-reject)**

When review emails are sent as part of admissions decisions.

**[Communicate with an applicant](/docs/fuxam-web/apply/applicants/communicate-with-an-applicant)**

Manual emails outside automated confirmation and review flows.

**[Configure program settings](/docs/fuxam-web/apply/application-programs/configure-program-settings)**

Submission deadlines tied to reminder and portal behavior.

**[Fuxam Apply overview](/docs/fuxam-web/apply/getting-started)**

Full admissions funnel including status pipeline and key concepts.
