The Components Of A Cut Process

Cut processes are simpler than overdue processes as they simply contain one or more "cut events". These events are the service agreement-specific actions designed to encourage the customer to pay. For example, you might set up cut events that:

• Create field activities to cut service
• Send letters (via the creation of a customer contact)
• Create To Do entries
• Impact the account's credit rating
• Create a case (e.g., to manage a customer with life support issues)
• ... (the list is only limited by your imagination as algorithms are used to perform the event's actions)

You define the number and type of events by configuring cut process templates. When the system creates a cut process, it copies the events defined on the related template.

It's important to note that all cut events are created when the cut process is created. The Overdue / Cut Event Manager is responsible for activating the cut events at the appropriate time. Activation of an event causes the system to do whatever the event indicates (e.g., send a letter, send a To Do entry to a user, create a field activity, etc.)

Cut processes do not have their own log as their history is maintained on the parent overdue process's log.