Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
|
Phone attributes configured in the Time Zone Phone Attributes field
|
Guard time of phone attributes
|
Result
|
|---|---|---|
|
Phone 1
Phone 2
|
Phone 1: 9:40 to 10:00
Phone 2: 9:30 to 9:45
|
As the guard times of phone 1 and phone 2 overlap, POM can pick up the record for dialing between 9:30 to 10:00.
|
|
Phone 1
Phone 2
|
Phone 1: 9:30 to 9:45
Phone 2: 13:00 to 13:15
|
As the guard time of phone 1 is open first, POM can pick up the record for dialing between 9:30 to 9:45.
If POM is busy dialing and processing other records and does not pick the record between 9:30 to 9:45, POM considers the record as not callable.
POM again considers the record as callable when the guard time of phone 2 is open, that is, from 13:00 to 13:15.
|
|
Phone 1
Phone 2
|
Phone 1: No open guard time for the current day
Phone 2: 10:00 to 10:15
|
POM can pick up the record for dialing between 10:00 and 10:15.
|
|
Phone 1
Phone 2
|
Phone 1: No open guard time for the current day
Phone 2: No open guard time for the current day
|
POM considers the record as not callable because no open guard time is available for any of the phone attributes for the current day.
|
|
Phone attributes configured in the Time Zone Phone Attributes field
|
Order of dialing the phone attributes as per the campaign strategy
|
Guard time of phone 1 and phone 2
|
Time at which POM picks up the record from the Job table for dialing
|
Time at which POM actually dials the record
|
Condition at the time of actual dialing of the record
|
Result
|
|---|---|---|---|---|---|---|
|
Phone 1
|
Phone 1
Phone 2
|
Phone 1 guard time: 15:00 to 15:15
Phone 2 guard time: 15:13 to 15:20
|
15:14
|
15:16
|
Guard time of phone 1 is closed for dialing.
|
According to the campaign strategy, phone 1 is to be dialed first. However, as the guard time of phone 1 is closed during actual dialing, POM evaluates the guard time of phone 2 provided the Skipover To Next Phone property of the Call node is enabled.
As the guard time of phone 2 is open during actual dialing, POM dials phone 2.
If the Skipover To Next Phone property of the Call task node is disabled, POM marks the record as temporarily restricted without evaluating the guard time of phone 2.
|
|
Phone 1
|
Phone 2
Phone 1
|
Phone 1 guard time: 15:00 to 15:15
Phone 2 guard time: 15:13 to 15:20
|
15:14
|
15:16
|
Guard time of phone 1 is closed for dialing.
|
According to the campaign strategy, phone 2 is to be dialed first.
As the guard time of phone 2 is open during actual dialing, POM dials phone 2.
|
|
Phone 1
|
Phone 1
Phone 2
|
Phone 1 guard time: 15:00 to 15:15
Phone 2 guard time: 15:13 to 15:20
|
15:14
|
15:22
|
Guard time of phone 1 is closed for dialing.
|
According to the campaign strategy, phone 1 is to be dialed first. However, as the guard time of phone 1 is closed during actual dialing, POM evaluates the guard time of phone 2 provided the Skipover To Next Phone property of the Call node is enabled.
As the guard time of phone 2 is also closed during actual dialing, POM marks the record as restricted.
|
|
Phone 1
|
Phone 1
Phone 2
|
Phone 1 guard time: 11:00 to 11:15
Phone 2 guard time: 11:10 to 11:25
|
11:02
|
-
|
Guard time of phone 1 is open for dialing.
|
According to the campaign strategy, phone 1 is to be dialed first.
The following are the scenarios:
|
|
Phone 1
|
Phone 2
Phone 1
|
Phone 1 guard time: 11:00 to 11:15
Phone 2 guard time: 11:10 to 11:25
|
11:02
|
-
|
Guard time of phone 1 is open for dialing.
|
According to the campaign strategy, phone 2 is to be dialed first.
The following are the scenarios:
|