Alerts

End users want to know what is happening with their finances at all times. Banno offers a variety of notifications to keep your end users up-to-date with what’s happening in their accounts. Once enabled for your institution by our Implementation Team, those users can configure custom notifications based on a variety of events.

End users can create as many or as few alerts as they want for their accounts. Each alert has a type, a threshold, and a delivery method. Alerts are associated with a specific account. Banno currently offers the following account alerts:

This notifies the end user when their balance goes above the set threshold.

Example:

This notifies the end user when their balance goes below the set threshold.

Example:

This notifies the end user when they receive a credit transaction with an amount above the set threshold.

Example:

This notifies the end user when they receive a debit transaction with an amount above the set threshold.

Example:

An end user can create multiple alerts of the same type for the same account, allowing the user to receive a notification across any of our available delivery methods: Email, SMS and push notification (mobile only).

If an end user needs alerts disabled for any reason, a financial institution representative can contact Banno support to do so.

Accountholders can receive alerts based on transfer activity. This functionality is not currently available to credit unions.

Transfer failed
A transfer was attempted and could not be completed.
Transfer expiring
A transfer is set to expire before completion.
Scheduled transfer expired
A transfer expired before being completed.
Scheduled transfer deleted
A scheduled transfer was manually removed.

Institutions using Ensenta for remote deposit capture have a few additional alerts available.

Check deposited
This notifies the end user when a check has been submitted for deposit to a given account.
Check accepted
This notifies the end user when a check deposit has been approved.
Check rejected
This notifies the end user when a check deposit has been rejected.

The Banno Platform runs a continuous cycle to see if alerts need to be sent for each account with alerts enabled. This cycle usually lasts just a few minutes, meaning alerts are sent as soon as possible.

Rather than using the same processes our apps use to get balances and transactions, the cycle retrieves only the data it needs to ensure alerts are generated as quickly as possible. This means that balance alerts don’t need to retrieve all of an account’s transactions, and this means the cycle doesn’t rely on a user opening the app to get new data.

The cycle runs in two parts: alerts that require checking transactions, and alerts that do not. As checking transactions is a relatively time-consuming process, we do not do so for accounts with only balance alerts set. This ensures that our cycle time is short, and that alerts are sent as fast as possible.

Some alerts can also be configured for a given end user, rather than a single account. These notify that user when something happens regarding their account as a whole.

This notifies the end user when a device that has not used the Remember this device toggle is used to log into a Banno app.

This notifies the end user when a Banno app has been used to change the email address on file.

This notifies the end user when a Banno app has been used to change the phone number on file.

This notifies the end user when a Banno app has been used to change the user’s password.

This notifies the end user when a Banno app has been used to change the username for this account.

Balance alerts are usually sent once per day, as per your institution’s timezone. These are checked for during each of the aforementioned alert cycles, and will be sent as soon as possible while taking into account designated late-night quiet hours.

Every cycle, each transaction pulled for accounts with transaction alerts configured is checked against each of those alert settings. An alert will be sent for each alert setting that transaction fulfills, meaning a single transaction can send multiple alerts if the user has configured their account to do so. This means end users may see alerts for a single transaction when it is memo posted and another when it is hard posted.

Alerts will send within an hour of a triggering event.


Related