This page was last edited on July 17, 2020, at 16:13.
Comments or questions about this documentation? Contact us for support!
Treatment sequences allow you to apply different treatments to each consecutive instance of the same call result. For example, if a Busy call result is received four times in sequence, you might want to apply a different action to each occurrence. Each treatment in the sequence must have a unique treatment name, an Apply to Record action, and a unique, consecutive sequence number. Treatments are linked by assigning the same call result to each treatment in the sequence.
Note: | Campaign sequences are not the same as treatment sequences. See Campaigns for more information about campaign sequences. |
Apply these general rules to treatment sequences.
Note: | Treatments using the Apply to Call action cannot be sequenced. Set the Number in Sequence value to 1, as OCS always identifies this action with a sequence value of 1 even if another value is specified. |
The following table shows Treatment objects that will be used in Examples 1 and 2, which follow.
Treatment Object Name |
Call Result |
Number in Sequence |
Treatment Action (Apply to Record) |
Busy1 | Busy | 1 | Redial |
Busy2 | Busy | 2 | Retry in (60 min.) |
AnsMach1 | Answering Machine Detected | 1 | Retry in (60 min.) |
AnsMach2 | Answering Machine Detected | 2 | Retry at specified date |
NoAnswer | No Answer | 1 | Retry in (60 min.) |
In this example, the Maximum Attempts value in the Calling List object is 8, and a record is dialed five times. The results are shown in the following table.
Call Result |
Treatment Action (Apply to Record) |
Reached Party? |
Busy | Redial | No |
Answering Machine Detected | Retry in (60 min.) | No |
Busy | Redial | No |
Answering Machine Detected | Retry in (60 min.) | No |
Answering Machine Detected | Retry at specified date | No |
Answer | No treatment | Yes |
In Example 1, the call did not reach its intended party and, on the fifth dial attempt, the second number in the Answering Machine Detected treatment sequence is executed.
When the number of times the telephone number is dialed matches the Maximum Attempts value from the calling list, the final outcome of the last attempt is applied and logged in the database. In this example the calling list object's Maximum Attempts value is 8. Using the same Treatment objects from Example 1, a record is dialed eight times, with the results shown in the following table.
Number of Attempts |
Call Result |
Treatment Action (Apply to Record) |
Reached Party |
1 | Answering Machine Detected | Retry in (60 min.) | No |
2 | Busy | Redial | No |
3 | Answering Machine Detected | Retry in (60 min.) | No |
4 | Busy | Redial | No |
5 | Answering Machine Detected | Retry in (60 min.) | No |
6 | Busy | Redial | No |
7 | Answering Machine Detected | Retry in (60 min.) | No |
8 | Busy | Redial | No |
In Example 2, the call did not reach its intended party after eight attempts. Because the Maximum Attempts value is 8, dialing stops and OCS applies the final outcome.