A Handler can contain one task node such as Call, SMS, Mail, Custom, or Selector.
A state is associated with each handler. There are three system defined states: initial, wait, and done. The campaign strategy is executed for each contact record filtered in the campaign. The execution starts at the Handler node with initial state. You can have only one Handler node with state as initial. The handler for initial state is mandatory.
You can add custom handlers and move the records from initial state to other state by using NextState property of Result or ResultProcessor nodes or through the FailState property of the Retry node.
States can have any value except wait or done.
For example, for Call Busy result, you have added a Retry node and given three retry attempts after 10 minutes. If after three attempts the phone is still busy, you can move the contact to another state, such as sendmail. You can add a Mail task node to send a mail to the contact.
Note:
The state names are case-sensitive.
The following table lists the properties of the node and their descriptions:
Property Name |
Description |
Name |
Type a display name for the handler node. If you do not specify a name, the default name is Handler. |
Description |
Specify a description for the handler node. |
State |
State can have any name except, done and wait. When the campaign job starts, all records are in an initial state. When the processing is over, the records move to done state. When a record reaches the done state, it moves out of the campaign. You have to name one of your handlers as initial. You cannot add a handler for wait and done state. If a contact record is in wait state, it remains in that state until some call disposition moves the record to the next state. |
Edit Description |
Click to edit the description of the handler node. |
