Email notifications

Understand automatic confirmation emails, decision review emails, in-app notifications, and staff reminder emails sent to applicants in Fuxam Apply.

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 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.

How it fits

The sequence shows 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; manual email in Communicate with an applicant.

Key concepts

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.

The same confirmation behavior is referenced in 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.

When review emails send

For the full decision procedure and status selector behavior, see Approve or reject and 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.

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 for application window behavior.

Administrator reminders

The Pending requirements view (when available in OrgHub) 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.

Automatic vs manual communication

Manual email does not change application status and does not trigger review email wording. Decision by email alone — without updating status in OrgHub — 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.
• 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

Related pages