Account Opening End-User Communications

For various Account Opening scenarios, there are automatic and optional end-user communications sent to Account Opening applicants. Emails are sent via the Narmi system and typically have a "from" address of no-reply@[financial-institution-domain] unless you have a default "from" email address specified in Institution Settings > Default From Email. For joint consumer and business applications, communications are sent to the primary applicant only. We require a secure connection with the receiving mail server to send all email communications.

For security, no usernames are included in these email communications by default. Your institution can choose to include usernames in end-user communications by contacting your Narmi Relationship Manager.

These emails are configurable in our Admin Platform. Under Institution Settings, on the left sidebar, select Digital Account Opening > Emails, then use the template specified below. Note: There are separate email templates for Consumer Account Opening (CAO) and Business Account Opening (BAO).

In UAT environments, for institution settings that configure email templates, you can select View sample email. This opens a new browser tab with a preview of the email as it appears to the end user and allows you to test the links within the email.

Automatic Emails

The Account Opening emails automatically sent to end-users are:

• Approved – We send this email upon successful opening of the account on the core. This applicant passed identity verification, successfully funded the account, and the account opened on the core. Use the Application Approved Template.

• Funding Failed – We send this email when identity decisioning was successfully processed, but the account did not proceed to the core banking system. (This can be due to several possible reasons, such as insufficient funds or an invalid credit card number. See Funding Failed for more information.) This email suggests to the applicant that they try a different funding method. Use the Funding Failed Template.

• Manual Review – We send this email when an applicant enters the "manual review" state after submitting an application. "Manual review" is an application outcome from Alloy which causes us to pause the application. The application must be manually decisioned by the financial institution in the Alloy platform.  Use the Manual Review Template.

• Denied (Consumers or owners/partners in an organization only) – We send this email when an applicant enters the "denied" state after submitting an application. "Denied" is an application outcome from Alloy, which causes us to stop the application from proceeding. Businesses are not auto-denied. Use the Application Denied Template.

• Documents Requested – If your financial institution is integrated with Vouched, we send this email when the applicant must upload additional documentation to complete their application. Use the Documents Requested Template. For more information on documents requested, go to Application Statuses.

• Email Confirmation – We send this email to confirm identity as part of the Account Opening flow, for example, when returning applicants want to continue an application. Use the CAO Email Confirmation Email Template or BAO Email Confirmation Email Template.

Optional Emails

There are optional emails that can be sent manually by your staff for other scenarios, such as continuing an application or sending reminder emails for retry funding, uploading documents, or accepting disclosures. Go to Application Actions and Staff-Led Account Opening Emails for more information on these optional communications.

For a complete list of communications sent from Account Opening and Digital Banking, go to End-User Communications.

Other Configuration

To include an FDIC or NCUA logo in the footer of these emails, go to Institution Settings > Member FDIC or NCUA Logo URL.

To edit the length of time in seconds that a link sent in an Account Opening communication is valid, go to Institution Settings > Email Link Validity. The default is 72 hours (3 days or 259200 seconds).