Skip to end of banner
Go to start of banner

Configuring Notification Types

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Back to Notifications Main Page

Table of Contents

Navigating to Notification Types

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. 

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

NOTIFICATION TYPES

Validations & Restrictions

Action ValidationsAdditional Information
Create
  • 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.
Edit
  • 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.
Delete
  • Notification Types can be deleted only if they are not used by an 'Effective' Notification Run Definition. 
  • Not Applicable

 Attributes

An * indicates a field is mandatory.

Name

Description

Main Information
Name*The name of the Notification Type.
Alternative CodeThe alternative code of the Notification Type. Unless otherwise specified, the Alternative Codes for new entries default to the Name initials in capital letters.
DescriptionA 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:
  • Financial Notifications
  • Customer Care Notifications
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.
  • 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
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:

  • Email
  • SMS
Default Email Type*

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

Default Email Type is mandatory if the selected Communication Template is of 'Email' Media.

Default Phone Type*

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

Default Phone Type is mandatory if the selected Communication Template is of 'SMS' Media.

Communication Queue External System Settings

APPLICABLE UP TO CRM.COM R9

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.

As of CRM.COM R10.0.0 the Communication Queue External System is retrieved from the Communication Template.

AuthorisationSettings

Available for 'Customer Care' Classifications only

 

 

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.

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

If either of the two settings for 'Affiliate' and 'Direct' Marketing is set to 'No' then Notifications/Communications will be not be created.

In order not to be affected by the Customer's preference for Affiliate Marketing and be able to create Notifications for Direct Marketing, the "Apply Contact Information Data Protection for Affiliate Marketing" Flag should not be checked.

A separate Notification Type should be created for 'Affiliate' and 'Direct' Marketing.

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.

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

If either of the two settings for 'Affiliate' and 'Direct' Marketing is set to 'No' then Notifications/Communications will be not be created.

In order not to be affected by the Customer's preference for Direct Marketing and be able to create Notifications for Affiliate Marketing, the "Apply Contact Information Data Protection for Direct Marketing" Flag should not be checked.


A separate Notification Type should be created for 'Affiliate' and 'Direct' Marketing.
Log Information
Log DetailsThe standard set of Log Details information available in all entities.

View Understanding Notifications for business examples related to Notification Types.

Related Areas

Helpful Links

  • No labels