Notifications are designed to notify your borrowers and employees of what changes may be made to the loans inside the LoanPro system. Notifications in LoanPro are separated into two categories: Event Based Notifications and Trigger Based Notifications. If preferred, you can choose which users within your company will receive these notifications on a per-agent-user basis. If you are new to the notifications settings in LoanPro, this article will explain the differences between the two types and how to customize them.
There are five ways that notifications in LoanPro can be sent: SMS, Email, System, Mail House, and Webhooks. While this article will describe how to set up notifications, it will not discuss the ways in which the notifications can be sent. The following articles will describe that process in more detail:
- Event Based Notifications – SMS
- Event Based Notifications – Email
- Event Based Notifications – System
- Event Based Notifications – Mail House
- Event Based Notifications – Webhooks
- Trigger Based Notifications – SMS
- Trigger Based Notifications – Email
- Trigger Based Notifications – System
- Trigger Based Notifications – Mail House
To see the notification settings within the LoanPro system, navigate to Settings > Company > Notifications within your company account. Here, you will have three tabs to choose from: Event Based Notifications, Trigger Based Notifications, and Sounds Manager.
If you would like to learn more about the Sounds Manager, it is covered in greater detail in a separate article.
Event Based Notifications
Event Based Notifications can be sent out when specific events occur in the system. For example, if you want to receive a notification whenever a customer makes a payment, an Event Based Notification can do so.
Creating a New Event Based Notification
Add a name and description for the notification to distinguish it from other Event Based Notifications you create. Next, choose whether the event will be based on a status change or a portfolio assignment by choosing either 'Loan Status Change' or 'Portfolio Change' from the 'Select Event' drop-down. Now, click 'Add Status Change' or 'Add Portfolio Change' to designate which changes will trigger the notification.
Existing Event Based Notifications
If you don't want to create a new Event Based Notification, LoanPro offers a range of existing events to choose from.
List of events that notifications can be based on
- Insurance Update – Executed when insurance information on an account is updated
- AutoPay Failed – Executed when Autopay execution fails.
- AutoPay Scheduled/Created – Executed when a loan Autopay is scheduled.
- Loan Settings Updated – Executed when a Loan Settings is updated.
- Loan Promise Created – Executed when a Loan Promise is created.
- Loan Collateral Updated – Executed when Loan Collateral is updated.
- Document attached to Account – Executed when Document is attached to Account.
- New Token Issued – Executed when the API endpoint is called with an expired token. Being a refresh method, this event occurs to issue a new token.
Transaction on Account
- Advancement Posted to Account – Executed when Advancement is posted to Account.
- Credit Posted to Account – Executed when Credit is posted to Account.
- Past Due Adjustment Posted to Account – Executed when Past Due Adjustment is posted to Account.
- Change Due Date Posted to Account – Executed when Change Due Date is posted to Account.
- Funding Transaction Posted to Account – Executed when Funding Transaction is posted to Account.
- Payment Posted to Account – Executed when a new payment is made.
- Payment Reversed – Executed when an existing payment is reversed.
- Loan Charge Posted – Executed when a Charge is posted to Account.
- Loan Charge Reversed – Executed when a Loan Charge is Reversed.
Account Setup & Lifecycle
- Archive Account – Executed when Account is Archived.
- Delete Account – Executed when Account is deleted.
- Account Created – Executed when an Account is created.
- Account Modified – Executed when an account is modified.
- Account Activated – Executed when a loan account is activated.
Customer Facing Website Activity
- Customer Logs into Customer Website – Executed when a customer logs in to the public site.
- Customer Website Document Upload – Executed when a customer uploads a document through the customer facing website.
Primary Customer on Loan Account Activity
- Customer Created – Executed when a Customer is created.
- Customer Updated – Executed when a Customer is updated.
- Payment Profile Added – Executed when a Payment Profile is added to a Customer.
- Employer Updated – Executed when Employer is updated.
- References Added – Executed when a References are added to a Customer.
Tenant Level Activity
- Agent User Created – Executed when an Agent User is created.
Status and Portfolio Changes
- Executed when a loan is changed form one status to another or is added or removed from a specific portfolio.
Edit a Notification
To edit the notifications created for any of these events, click the edit icon located to the right of the event listing.
When you edit an Event Based Notification, you can choose to update any or all of the notification types for the event you chose. The three notification sections have three groups of options. The first group lets you select who should receive the notification and how they should receive it. The second group lets you choose to restrict which loans can cause the notification to be sent. The third group involves the message that will be sent.
Trigger Based Notifications
Trigger Based Notifications are based on the rules that you can create within the system. For all intents and purposes, there are unlimited options when it comes to creating rules. These notifications are sent out daily when LoanPro updates your accounts. For example, if you create a rule to test whether an account is more than 5 days past due, you can create a notification using this rule. When the number of days past due gets updated each day (usually during the night), the system finds accounts that were 5 or more days past due and sends the notification to the customers on those accounts.
Since Trigger Based Notifications aren’t based on a hard-wired list of events, you can create and delete them. You also have the option to force a trigger evaluation at any time because changes to a customer account could cause it to qualify for a trigger at any time.
Here, you have the option to configure any of the notification types for the trigger you are adding.