C1-DLQSENDCC

This algorithm creates a customer contact to send a letter (for example, dunning letter, warning letter, etc.). If the delinquency process is created for a person, this algorithm checks whether the Notify Group Customer Or Bill Groups Or Bill Accounts parameter is set to PG, BG, or BA. Depending on the value defined for the Notify Group Customer Or Bill Groups Or Bill Accounts parameter, this algorithm does the following:

  • If the Notify Group Customer Or Bill Groups Or Bill Accounts parameter is set to PG, this algorithm checks whether the person type of the person is set to Parent Customer or Bill Group. If the person type of the person is set to Parent Customer, this algorithm creates a customer contact for the parent customer. However, if the person type of the person is set to Bill Group, this algorithm derives the parent customer of the bill group (using the Person Relationship Type option type of the C1-ASOBLLNG feature configuration) and then creates a customer contact for the parent customer.

  • If the Notify Group Customer Or Bill Groups Or Bill Accounts parameter is set to BG, this algorithm checks whether the person type of the person is set to Parent Customer or Bill Group. If the person type of the person is set to Parent Customer, this algorithm creates a customer contact for the parent customer and for all those bill groups of the parent customer who are associated with the parent customer using the relationship type which is specified in the Person Relationship Type option type of the C1-ASOBLLNG feature configuration.

    However, if the person type of the person is set to Bill Group, this algorithm derives the parent customer of the bill group (using the Person Relationship Type option type of the C1-ASOBLLNG feature configuration) and then creates a customer contact for the parent customer and for the respective bill group.

  • If the Notify Group Customer Or Bill Groups Or Bill Accounts parameter is set to BA, this algorithm checks whether the person type of the person is set to Parent Customer or Bill Group. If the person type of the person is set to Parent Customer, this algorithm creates a customer contact for each account to which the parent customer and its bill groups are associated as the main customer. The system considers those bill groups of the parent customer who are associated with the parent customer using the relationship type which is specified in the Person Relationship Type option type of the C1-ASOBLLNG feature configuration. However, if the person type of the person is set to Bill Group, this algorithm derives the parent customer of the bill group (using the Person Relationship Type option type of the C1-ASOBLLNG feature configuration) and then creates a customer contact for each account to which the parent customer and the respective bill group are associated as the main customer.

However, if the delinquency process is created for an account, this algorithm checks whether the Receives Notification option is selected in the bill routing information of any person associated with the account. If the Receives Notification option is selected in the bill routing information of a person, this algorithm creates a customer contact for the person. Note that if the value is specified for the Account Relationship Type parameter, this algorithm will consider only those persons who are associated with the account using the given relationship type. Irrespective of whether the delinquency process is created for a person or an account, this algorithm also checks whether the Send Membership Level Notification Source field corresponding to the respective delinquency event type in the respective delinquency process type is set to Delinquency Process Type or Algorithm. If the Send Membership Level Notification Source field is set to Delinquency Process Type, this algorithm checks whether the Send Membership Level Notification field corresponding to the respective delinquency event type in the respective delinquency process type is set to Send Membership Level Notification Required or Send Membership Level Notification Not Required.

However, if the Send Membership Level Notification Source field is set to Algorithm, this algorithm invokes the C1-DERMLNBR algorithm attached to the Send Member Level Notification Option Derivation system event in the respective delinquency process type. For more information about the algorithm, see C1-DERMLNBR. If the value of the Send Membership Level Notification field is set to Send Membership Level Notification Required either in the delinquency process type or in the business rule depending on the send membership level notification source, this algorithm derives the memberships billed to the delinquent customer or account. It then checks whether the number of memberships derived is less than or equal to the number specified in the Member Level Notification Deferred Processing Threshold parameter. If the number of memberships derived is less than or equal to the specified value, this algorithm creates a customer contact for the main subscriber of each derived membership in the real time (i.e. immediately). In addition, the status of the delinquency event is changed to Complete.

However, if no value is defined for the Member Level Notification Deferred Processing Threshold parameter or if the number of memberships derived is greater than the specified value, this algorithm changes the status of the delinquency event to Pending Contact Creation.For more information on how the customer contacts are created at the membership level for such events, see Creating Customer Contacts for Group, Direct Billed Group Membership, or Individual Membership.

In addition, this algorithm does the following:

  • Creates a log entry for each customer contact in the delinquency process.

  • Stamps the delinquency process ID as a characteristic using the C1-DELPO characteristic type on the customer contact.

  • Stamps the account ID as a characteristic using the given characteristic type on the customer contact.

    Note:

    The account ID is stamped as a characteristic on the customer contact only when either of the following condition is met:

    • The delinquency process is created for a person and the Notify Group Customer Or Bill Groups Or Bill Accounts parameter is set to BA.

    • The delinquency process is created for an account.

  • Stamps the membership ID as a characteristic using the given characteristic type on the customer contact.

    Note: The membership ID is stamped as a characteristic on the customer contact only when the customer contact is created for the main subscriber of the membership.

This algorithm is invoked when the event is triggered manually from the user interface or automatically through the C1-DPMON batch. You can use this algorithm in a delinquency process type using which you want to create a delinquency process through which debt collection letters are sent to the delinquent customer or account. It should be attached to the delinquency event type which sends a warning or dunning letter.

Note: Once a customer contact is created, a record is added in the C1_​DELIN_​PROC_​EVT_​NOTIF table where the DP_​EVT_​NOTIF_​TYPE_​FLG column is set to CC and the DP_​EVT_​NOTIF_​ID column is set to the customer contact ID.

This algorithm derives the preferred contact method for the customer contact. While deriving the preferred contact method, the algorithm first fetches the main customer’s bill route type on the account and then fetches the bill routing method of the bill route type. Once the bill routing method is derived, the system considers the preference which is specified in the Routing Method – Contact Method Mapping option type of the DELINPROC feature configuration. For more information about the feature configuration, see Setting the DELINPROC Feature Configuration.

It then checks whether any preferred contact method is mapped to the bill routing method in the preference. If the preferred contact method is mapped to the bill routing method in the preference, the system stamps it on the customer contact. However, if the preferred contact method is not mapped to the bill routing method in the preference, the system considers the default contact method as the preferred contact method and stamps it on the customer contact.

This algorithm contains the following parameters:

  • Customer Contact Type – Used to indicate the customer contact type using which you want to create the customer contact. This parameter is mandatory. Here, you must specify a customer contact type with the appropriate letter template depending on the type of letter you want to send to the customer.

  • Customer Contact Class – Used to indicate the customer contact class to which the customer contact type belongs. This parameter is mandatory.

  • Default Contact Method – Used to indicate the contact method that you want to use when the preferred contact method cannot be derived for the routing method from the preference. This parameter is mandatory.

  • Notify Group Customer Or Bill Groups Or Bill Accounts – Used to indicate whether a customer contact should be created for a parent customer, bill group, and/or for each billing account (that meets the criteria). The valid values are:

    • PG – Used when you want to create a customer contact only for the parent customer.

    • BG – Used when you want to create a customer contact for the parent customer and for the bill groups of the parent customer. If the person type of the person is set to Parent Customer, the system creates a customer contact for the parent customer and for all those bill groups that are associated with the parent customer using the relationship type specified in the Person Relationship Type option type of the C1-ASOBLLNG feature configuration. However, if the person type of the person is set to Bill Group, the system creates a customer contact for the parent customer and the respective bill group.

    • BA – Used when you want to create a customer contact for the main customer of the account. If the person type of the person is set to Parent Customer, the system creates a customer contact for each account to which the parent customer and its bill groups are associated as the main customer. However, if the person type of the person is set to Bill Group, the system creates a customer contact for each account to which the parent customer and the respective bill group are associated as the main customer. Note that this parameter is only applicable for the fully insured group business.

  • Account Characteristic Type – Used to indicate the characteristic type using which you want to store the account ID on the customer contact. Here, you must specify a characteristic type where the characteristic entity is set to Customer Contact.

  • Membership Characteristic Type – Used to indicate the characteristic type using which you want to store the membership ID on the customer contact. Here, you must specify a characteristic type where the characteristic entity is set to Customer Contact.

  • Account Relationship Type – Used to indicate the relationship type using which the person is associated with the account. The system will then create the customer contacts only for those persons who are associated with the account using the specified relationship type. This parameter is optional. You can specify maximum ten comma-separated values for this parameter. If you do not specify the parameter value, the system will create customer contacts for all the persons who are associated with the account irrespective of their relationship type. Note that this parameter is only applicable for the fully insured individual business.

  • Member Level Notification Deferred Processing Threshold – Used to specify the maximum number of memberships for which customer contacts can be created in the real time (i.e. immediately). If the number of memberships billed to the delinquent customer or account exceeds the specified limit, a customer contact is created for the main subscriber of each derived membership in the deferred mode (i.e. through the C1-MBRNT batch control).