Setting Up Severance Event Types

Severance event types control what is done by a given severance event. Open Admin > Credit & Collection > Severance Event Type > Add to define your severance event types.

Fastpath:

For more information refer to Designing Your Severance Procedures.

Description of Page

Enter a unique Severance Event Type code and Description for the severance event type.

Enter the Severance Event Type. Permissible values are: Affect Credit Rating/Cash-Only, Send Letter, Generic Algorithm, Create To Do Entry, Create Field Activities, Expire Service Agreement. The following discussion describes the parameters that must be defined for each type of severance event.

The Affect Credit Rating/Cash-Only collection event type causes a credit rating demerit record to be linked to the account. This record is constructed using the following Parameters:

  • account debt monitor.
  • Use Cash-Only Points to define this event's affect on the account's cash-only score. This should be a positive number. When an account's cash-only score exceeds the cash-only threshold score defined on the installation record, the account is flagged as cash-only during payment processing and on Control Central.
  • Use Cash-Only Points to define this event's affect on the account's cash-only score. This should be a positive number. When an account's cash-only score exceeds the cash-only threshold score defined on the installation record or the account’s CIS Division, the account is flagged as cash-only during payment processing and on Control Central.

The Send Letter severance event type causes a customer contact to be generated that, in turn, generates a letter. Enter the following Parameters for this type of event:

  • Select the Contact Class used to categorize the customer contact.
  • Use Contact Type to define the type of customer contact to create. The type of customer contact controls the type of letter that is generated.

The Generic Algorithm severance event type causes the algorithm defined in the Sev. Event Algorithm to be executed. You use this type of algorithm when the standard types of severance events won't do what you need done.

The Create To Do Entry severance event type causes a To Do entry to be created. Refer to The Big Picture of To Do Entries for more information about To Do entries (refer to the To Do type TD-SEVT for the type of To Do entry that's created).

The Generate Field Activities severance event type causes one or more field activities to be generated. Enter the following Parameters for this type of event:

  • Select the Customer Event associated with the field activity. Valid values are: Cut For Non-Payment (CNP), Disconnect Warning (Disc Warn), Reconnect for Payment (Reconn), Start Service (Start) , Start/Stop Service (Start/Stop), Stop Service (Stop), Reread (Reread).
  • The system uses the Customer Event to select the appropriate field activity type(s) from the field activity type profile associated with the service points linked to the service agreement.
Warning:

The field activity types are NOT specified directly on the severance event type. Why? Because each service point linked to the service agreement being severed could necessitate a different type of field activity. Therefore, the system uses the type of service point, its state (e.g., connected, meter off) and the desired customer event (e.g., Disconnect Warning, Cut For Non-Payment) to determine which field activity type(s) to generate. Refer to Setting Up Field Activity Type Profiles for how to set up the specific disconnect field activity types for your various types of service points.

The Expire Service Agreement severance event type causes the service agreement to be moved to the pending stop state (it also populates the service agreement's stop date). Refer to Finalizing Pending Stops for how the system will eventually stop the service agreement (and then final bill it). There are no parameters for this type of event.

Note:

Cut for non-payment field activities are special. The Expire Service Agreement severance event type also makes any "cut for non-payment" field activities created by earlier severance events available to stop service. Specifically, it changes the linkage type of the field activities from Severance Activity to Stop Activity. You can see a service agreement's service points' field activities and their respective linkage type on Service Agreement - Service Point.

Enter a Long Description to fully describe the severance event type.