Back to Notifications Main Page
| Excerpt | ||
|---|---|---|
| ||
Learn to configure Notification Types |
| Panel | ||||
|---|---|---|---|---|
| ||||
Table of Contents
|
Navigating to Notification Types
| Info |
|---|
CONFIGURATION > CRM APPLICATION > NOTIFICATIONS > SET UP TYPES |
What are Notification Types?
Notification Types define the behaviour and nature of each Notification. Multiple Notification Types can exist in the System but each one of them should have a unique Name and Alternative Code.and every time the required one may be used in order to generate the Notifications, used to communicate with your customers, through Notification Runs. Notification Types can have one of 3 Classifications, each of which serves a different business spectrum:
- Financial Notification Types: Used to notify customers on outstanding balances, curent balances, bills etc.
- Customer Care Notification Types: Used to notify customers on CRM matters, such as the hardware and services on their Subscriptions or a welcome message or even a new product campaign.
- Reward Offers Notification Types: Used to notify Reward Participants about new Reward Offers applicable to them.
- Navigate to Notification Types and explore existing entries via the Summary page.
- Click on the link (Name or Number) of the entry of your interest to enter the Data Entry page and see more detail.
- Use the Actions Menu to create a NEW Notification Type, modify (EDIT) or DELETE an existing one.
- Use the BACK to return to the Summary page and CANCEL to revert any unwanted changes made to the Notification Types.
- Click on the Audit Trail button to view a log of changes performed on the displayed Notification Types.
Check the Validations & Restrictions Table below for a list of available Actions when working with Notification Types, including each Action's related validations and additional information. View the Attributes Table for a comprehensive description of the Notification Types fields.
| Anchor | ||||
|---|---|---|---|---|
|
| Action | Validations | Additional Information |
|---|---|---|
| Create |
|
|
| Edit |
|
|
| Delete |
|
|
| Anchor | ||||
|---|---|---|---|---|
|
An * indicates a field is mandatory.
Name | Description | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Main Information | |||||||||||||||||||||
| Name* | The name of the Notification Type. | ||||||||||||||||||||
| Alternative Code | The alternative code of the Notification Type. Unless otherwise specified, the Alternative Codes for new entries default to the Name initials in capital letters. | ||||||||||||||||||||
| Description | A description of the Notification Type. | ||||||||||||||||||||
| Classification* | Notification Type Classifications are used to determine the behaviour of each Notification. The Notification Classification cannot be changed after the Notification Type is created. The supported Notification Classifications are the following:
| ||||||||||||||||||||
| Notification Information* | The information regarding which the customer will be notified, which is filtered based on the selected Notification Classification. The Notification information cannot be changed after the Notification Type is created. The available Notification Information for each Classification is listed below.
| ||||||||||||||||||||
Unified Code
| An auto-generated code which is used to group the various instances of the Notification Type. | ||||||||||||||||||||
Version
| An auto-generated number which is used to specify the version of each Run Definition. If the version is already in use by a Run, a new Run Definition Version is created each time the Definition is edited. "VIEW PREVIOUS VERSIONS" link allows you to search and view any previous versions of the Definition. | ||||||||||||||||||||
Validity Dates
| Defines the Effective Date and Expiration Date of each Notification Type Version. The dates are automatically set whenever a new Version is created. The current Version of a Notification Type has no Expiration Date set. | ||||||||||||||||||||
| Communication Information | |||||||||||||||||||||
| Communication Template* | The Template to be used for creating Communications for Notifications of this Type. The available Communication Templates should be 'Effective' and equal to one of the following Media:
| ||||||||||||||||||||
| Default Email Type* | Determines the Type of Contact Information Email that should be used to communicate with customers.
| ||||||||||||||||||||
| Default Phone Type* | Determines the Type of Contact Information Phone that should be used to communicate with customers.
| ||||||||||||||||||||
Communication Queue External System Settings
| Used to determine which external system will send the Notification. If not specified, then the Notification will be sent by email directly through CRM.COM. It is possible not to apply 'From' and 'To' email validation when creating a Communication, provided an external system is specified.
| ||||||||||||||||||||
Consider Presentment Preferences Communication Media
| Defines whether an account owner's Presentment Preferences will be considered during the Notification Run or not depending on the Communication Template's Media and the Presentment Preference's related media. Two options are available:
The mapping between the Presentment Preferences and the Communication Media is the following:
| ||||||||||||||||||||
Criteria
| |||||||||||||||||||||
Segments | |||||||||||||||||||||
| Included Segments | A list of Segments which are used to filter the Contact Information, Accounts Receivable or Notification Item (i.e. bill, subscription, e.t.c.) that will be notified.
Existing Segment can be selected but a new Segment can also be created through Notification Type. | ||||||||||||||||||||
| Excluded Segments | A list of Segments which are used to prevent Contact Information, Accounts Receivable or Notification Items (i.e. bill, subscription, e.t.c.) from being notified.
Existing Segment can be selected but a new Segment can also be created through Notification Type. | ||||||||||||||||||||
| Notification History Criteria | |||||||||||||||||||||
| Notified Previously | Defines a list of Notifications that should have already been generated for the criterion to be considered as met. It includes the following options:
| ||||||||||||||||||||
| Not Notified Previously | Defines a list of Notifications that should not already exist; i.e. the customers have not been sent these Notifications previously. Available options are the same as those of "Notified Previously". | ||||||||||||||||||||
Accounts Receivable Criteria
| |||||||||||||||||||||
| Accounts Receivable Balance | Filters the Accounts Receivable based on Balance. Two options are available, which can be used in tandem:
| ||||||||||||||||||||
| Accounts Receivable Outstanding Amount | Filters the Accounts Receivable based on Outstanding Amount and a specific due date. Two options are available, which can be used in tandem:
The due date can be specified in one of the following ways:
| ||||||||||||||||||||
| Accounts Receivable Classification | Filters the Accounts Receivable based on a list of Accounts Receivable Classifications. | ||||||||||||||||||||
Notification Criteria
| |||||||||||||||||||||
| Total Outstanding Amount per Notification | Filters the Notifications to be created based on the total outstanding amount of each Notification, calculated using associated respective invoices. Two options are available, which can be used in tandem:
| ||||||||||||||||||||
Wallet Criteria
| |||||||||||||||||||||
| Wallet Balance | Filters the Accounts Receivable based on the Balance of Wallets owned by that account. Two options are available, which can be used in tandem:
| ||||||||||||||||||||
| Wallet Estimated Consumption Days | Filters the Accounts Receivable based on the estimated consumption days of Wallets owned by that account. Two options are available, which can be used in tandem:
| ||||||||||||||||||||
| Wallet Product Estimated Consumption Days | Filters the Accounts Receivable based on the Product estimated consumption days of Wallets owned by that account. Two options are available, which can be used in tandem:
| ||||||||||||||||||||
| Wallet Amount Expiration Up To Date | Filters the Wallets based on the amount that will expire by a defined date.
Optionally, an amount to be expired by the specified date which is greater than or equal to a specified minimum (amount) can be used to filter the Wallets.
| ||||||||||||||||||||
Subscription Criteria
| |||||||||||||||||||||
| Subscription Types | Filters the Accounts Receivable based on the Type of Subscriptions owned by the Accounts Receivable. | ||||||||||||||||||||
| Billing Term Schemes | Filters the Accounts Receivable based on the Billing Term Schemes of Subscriptions owned by the Accounts Receivable. | ||||||||||||||||||||
Reward Offer Criteria
| |||||||||||||||||||||
| Classifications | Filters the Reward Offer Type's Classifications. | ||||||||||||||||||||
| Reward Offer Types | Filters the Reward Offers based on their Reward Offer Type. | ||||||||||||||||||||
| Reward Schemes | Filters the Reward Offers based on their Reward Scheme. | ||||||||||||||||||||
| Reward Offer Validity | Filters the Reward Offers based on their validity period if it is set. Only Reward Offers whose validity period falls withing the specified period will be retrieved. The available options are:
| ||||||||||||||||||||
| Reward Offers | Filters the Rewards Offers. Only Effective Reward Offers can be defined. | ||||||||||||||||||||
| Awarded State | Defines whether the Rewards Participants will be notified based on their awarded state. Two options are available:
| ||||||||||||||||||||
AuthorisationSettings
| |||||||||||||||||||||
| Apply Contact Information Data Protection for Direct Marketing | Determines whether the Authorisation Settings defined on the Contact Information for Direct Marketing will be taken into consideration when the Notification Run is executed.
| ||||||||||||||||||||
| Apply Contact Information Data Protection for Affiliate Marketing | Determines whether a contact's Authorization Settings for Affiliate Marketing will be taken into consideration when the Notification Run is executed.
| ||||||||||||||||||||
| Log Information | |||||||||||||||||||||
| Log Details | The standard set of Log Details information available in all entities. | ||||||||||||||||||||
| Note |
|---|
View Understanding Notifications for business examples related to Notification Types. |
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Related Areas
|
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Helpful Links
|