• Mandatory Fields must be defined
• Name and Alternative Code must be unique

• Communication Templates are filtered; only 'Effective' Communication Templates of Media 'Email' and Direction 'Outgoing' can be selected.

• Mandatory Fields must be defined
• Name and Alternative Code must be unique

• It is possible to modify an existing Notification Type, although the Classification and Notification information cannot be changed after the Notification Type is created.

• Notification Types can be deleted only if they are not used by an 'Effective' Notification Run Definition. 

• Not Applicable

• Financial Notifications
• Customer Care Notifications
• AVAILABLE FROM CRM.COM R12.0.0 Reward Offers Notifications

• For Financial Notifications:
  
  • Subscriptions
  • Bills
  • Wallets
  • Wallet Product Consumption
• For Customer Care Notifications:
  • Subscriptions
  • Jobs
  • Activities
  • Leads
  • Rewards Participants
  • Award Transactions
  • Spend Transactions
  • Award Expiration Transactions
  • Service Requests
  • Payment Gateway Cards
  • Payment Gateway Requests
  • Payments
  • Buy in Advance Request
• AVAILABLE FROM CRM.COM R12.0.0 Reward Offers Notifications
  • Reward Offers

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.

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:

• Email
• SMS

Determines the Type of Contact Information Email that should be used to communicate with customers.

Determines the Type of Contact Information Phone that should be used to communicate with customers.

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.

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:

• Yes: Communications are created if the Communication Template's Media is enabled on the Accounts Receivable's Presentment Preferences.Otherwise no Communication will be created.
• No: Communications are always created regardless of the Customer's Accounts Receivable Presentment Preferences.

The mapping between the Presentment Preferences and the Communication Media is the following:

A list of Segments which are used to filter the Contact Information, Accounts Receivable or Notification Item that will be notified.

A list of Segments which are used to prevent Contact Information, Accounts Receivable or Notification Items from being notified.

Defines a list of Notifications that should have already been generated for the criterion to be considered as met. It includes the following options:

• Notification Typ
• Life Cycle State
• Created less than X UOT ago (measured in minutes, days, weeks, months or years)
• Created more than X UOT ago (measured in minutes, days, weeks, months or years)

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

Filters the Accounts Receivable based on Balance. Two options are available, which can be used in tandem:

• More than:checksforavalue that is more than or equal to the one specified (≥).
• Less than: checks for a value that is less than the one specified (<).

Filters the Accounts Receivable based on Outstanding Amount and a specific due date. Two options are available, which can be used in tandem:

• More than:checksforavalue that is more than or equal to the one specified (≥).
• Less than: checks for a value that is less than the one specified (<).

The due date can be specified in one of the following ways:

• Due in X Days: The System checks for Accounts whose outstanding amount is due up to a date equal to the current date + X (a user-defined integer representing a number of days). For example, if the current date is the 23rd of the month and X is set as 5, the System retrieves accounts with outstanding amounts due up to the 28th.
• Due X days ago: The System checks for Accounts whose outstanding amount was due up to a date equal to the current date - X (a user-defined integer representing a number of days). For example, if the current date is the 23rd of the month and X is set as 5, the System retrieves accounts that were due up to the 18th.

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:

• More than: checks for a value that is more than or equal to the one specified (≥).
• Less than: checks for a value that is less than the one specified (<).

Filters the Accounts Receivable based on the Balance of Wallets owned by that account.  Two options are available, which can be used in tandem:

• More than:checks for a value that is more than or equal to the one specified (≥).
• Less than: checks for a value that is less than the one specified (<).

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:

• More than:checks for a value that is more than or equal to the one specified (≥).
• Less than: checks for a value that is less than the one specified (<).

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:

• More than:checks for a value that is more than or equal to the one specified (≥).
• Less than: checks for a value that is less than the one specified (<).

Filters the Wallets based on the amount that will expire by a defined date.

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

• Minimum Expiration Amount

Determines whether the Authorisation Settings defined on the Contact Information for Direct Marketing will be taken into consideration when the Notification Run is executed.

• If 'No' is selected, the customer will receive a Direct Marketing Notification as the Contact Information Authorization Setting which is set to 'No' will not be taken into account.
• If 'Yes' is selected, the System will take into account the Authorization Setting on the Contact Information to determine whether a Direct Marketing Notification should be sent.
  • If the Setting is set to 'Yes', then a Notification will be created
  • If the Setting is set to 'No', then a Notification will not be created.

Determines whether a contact's Authorization Settings for Affiliate Marketing will be taken into consideration when the Notification Run is executed.

• If 'No' is selected, the contact will receive an Affiliate Marketing Notification as the Contact Information Authorization Setting which is set to 'No' will not be taken into account.
• If 'Yes' is selected, the System will take into account the Authorization Setting on the Contact Information to determine whether an Affiliate Marketing Notification should be sent.
  • If the Setting is set to 'Yes', then a Notification will be created
  • If the Setting is set to 'No', then a Notification will not be created.