Follow-up action is typically a business function executed when a customer contract is moved from one collection stage to another. Each collection stage is mapped to a single or multiple predefined actions.
Whenever a customer contract is moved to certain stage, the corresponding actions are taken place in an order, over a period of time.
The actions can be set for billing an agreement, provisioning the services, sending reminder STB mails or OSD messages etc. When a contract is moved back to the normal stage, some of the actions are reversed.
For Example:
Let's consider following two actions are defined in the system and mapped to a stage called Stage1 resulting suspension of services:
Action1: Generate Suspend Provisioning Request
Action2: Sending reminder messages with customized text to the customers
Action3: Suppress Billing
Whenever a customer contract is moved to Stage1, the above three actions are taken place automatically. As a part of collection process, a suspend provisioning request is generated to suspend the services, a reminder message is sent to the subscriber informing him about the contract suspension and also bill generation process is disabled towards such suspension.
Later, when the contract is moved back to the normal stage (to ACTIVE status), the bill generation process is enabled again.
Note: Various Message Templates can be defined in the system for sending customized mails to the customer.