.png?sv=2022-11-02&spr=https&st=2025-06-26T19%3A40%3A53Z&se=2025-06-26T19%3A50%3A53Z&sr=c&sp=r&sig=MVKqkzIrOfOxj64qjQSt8L%2BG3UOtx3EOvuikUzNpLoQ%3D){kind=logo}
Progressive Pacing Mode
- DarkLight
Progressive Pacing Mode
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Select Progressive from the Pacing Mode dropdown list.
Select an appropriate option for Action on AMD.
Select None if you want no action to take if an Answering Machine is detected.
Select Continue with Agent to continue the call with the agent on the line. The agent decides on the next action.
Select Disconnect the Call to disconnect the call when Answering Machine is detected. This option allows only a retry for the contact.
Select Leave a Voice-Mail to leave a voice mail to the customer when an Answering Machine is detected.
Background AMD specifies what action the application must take if an Answering Machine is detected. By default, it is set to OFF. This is applicable only when the Enhanced CCA option is set to ON and the Pacing mode is Predictive Cruise Control, Predictive Expert Call Ratio, or Progressive.
If Background AMD is set to ON, select one of the values from Action on AMD.
Select a Driver App. A DriverApp defines the CCXML application that you can use for the outbound calls.
Enhancement CCA field is not active for this pacing mode.
Select Nailer App from the dropdown. This is applicable only for agent-based campaigns. Specify a CCXML application that establishes contact with an available agent. This is also called as nailing the agent.
If you want to change the pacing mode of a POM campaign during runtime, turn the Runtime Change Pacing Type to ON.
Note:
When you change the pacing type during a campaign runtime, certain fields may be rendered non-relevant to the changed pacing type. These fields are not enabled.Turn the Silent Call Detection to ON. On CCA timeout, based on the following configuration of the silence call parameter, a resulting action occurs as follows:
Silence call detection ON indicates POM defines the call flow in the contact strategy.
Silence call detection OFF indicates POM classifies the call as Answer Human. The customer has an option to configure different actions for a silence call.
Based on the configuration, if POM detects a silence call, POM performs one of the following actions: Connects a call to the agent. Runs an application. Disconnects the call and attempts to connect the same call on another phone.
Turn the Allocation to ON if required. The allocation switch decides how the ports are allocated to the tasks depending on the value selected. The default value is Dynamic port allocation.
Enter a Default Completion Code. Agents normally provide a completion code on completion of a call. In the event of an agent not providing this information, specify the completion code and assign the completion code to the call.
Set a number to set the Max Agents. This the maximum number of agents that can be allocated to this task - in this case, this POM campaign.
Set a number to set the Min Agents. This the minimum number of agents that can be allocated to this task, in this case, this POM campaign.
Set a number to configure the Over Dial Ratio. This is the ratio by which the dialer dials out excess contacts. For example, if the Agent: Dialing ratio is set at 2, the application dials out two contacts for each agent in the Available state. If the Over Dial Ratio is set to 1, it dials out an additional two contacts - that is, a total of four contacts for each agent.
Enter a Priority. This denotes the priority for dialing out uploaded contacts. The higher the number is the better the priority.
Example: a task with Priority 7 gets more ports assigned to complete this task as compared to one with a Priority 5.
Enter Sender’s Address.
Contact List Attribute
Contact List Attributes are Business Fields on Campaign Manager. These attributes are synchronized from the Avaya POM server. These contact list attributes are listed on the left. You can associate a maximum of 25 attributes to this POM campaign. The attributes you associate here appear as Business Fields on your campaigns mapped to this POM campaign (group). The following points are applicable in respect of Contact List Attributes.
Go to the Contact List Attributes.
All attributes are shown with data type as String on the Campaign > Business Parameters. Attributes with DateTime are shown with DateTime data type and not string.
Ensure the business parameters you upload as part of the contact files have the same data type as it was created such as DateTime, Number, and so on. If there is a conflict, the contact with such error must be skipped from dialing.
Contacts skipped from dialing are shown with Outcome as Delivered. There are no further updates available to indicate these were not dialed.
Note:If the campaign is activated, you cannot edit the mapping.Select the attribute and click > to move this attribute from the Available Attributes to the Assigned Attribute. You can select multiple attributes. To select all attributes and move them, click >>.
CPA Settings
The CPA Settings section allows you to configure the various parameters for performing the Call Classification Analysis (CCA). The CPA Settings screen is shown here. This section is common for all the pacing modes.
Select a CCA Start from the On Connect and On Progress. On Connect allows CCA to commence from the moment the call is answered and On Progress allows CCA to commence immediately when POM finishes dialing the number and the call progress starts.
Set a number to enter the CCA Timeout in milliseconds. This is the value you set for CCA to time out if not completed by the application.
The default value of On Connect is 7500 and it varies between 5000 and 20000.
The default value of On Progress is 24000 and it varies between 5000 and 45000.
If required, turn the Compliance Timer to ON. The default is ON.
If you set the timers to OFF, the POM driver waits for the result of the call classification before starting any application or connecting to the agent, and the maximum wait time for CCA result is defined by the CCA Timeout.
If you set the compliance timers to ON, POM waits for call classification results till the expiry of the compliance timers. If call classification results are not available within the given time, Answer Human treatment is started for the call. The completion code gets updated as per the classification events received till the call is alive for Notification campaign; or before getting patched to the agent for an agent-based campaign.
If Compliance Timer is enabled, enter the following parameters:
Enter the Start of Voice Timeout. This is the timeout value if start of voice is not detected. Set the value in milliseconds. The default value is 2000. The combined value of the Start of Voice Timeout and Live Voice Timeout cannot be more than the CCA Timeout value.
Enter the Live Voice Timeout. This is the timeout value if a live human voice is not detected. Set the value in milliseconds. The default value is 1800. The combined value of the Start of Voice Timeout and Live Voice Timeout cannot be more than the CCA Timeout value.
Set the value in the AMD False Positive Rate under the Nuisance Rate Calculation. This setting in milliseconds determines when to consider an answering machine detection as a false positive.
Enable or Disable the Consider Answer Machine by Agent switch.
Note:When Consider Answer Machine By Agent is True, such calls are considered in the Nuisance Rate Calculations.Click Save.
In the Attributes tab, enter a Name and a Description for the Call Type. Leave other fields blank or with default values.
Fields
Field | Description |
|---|---|
Overdial ratio | Sets how many additional contacts are dialed per available agent. For example, with a 2:1 agent-to-dial ratio, the application dials two contacts per agent. If overdial ratio is 1, it dials two more, totaling four. |
On connect | Starts call classification analysis (CCA) when the call is answered. |
On progress | Starts CCA immediately after POM finishes dialing and call progress begins. |
CCA timeout | Sets the maximum time for CCA to complete. If not completed, it times out. On connect default: 7,500 ms (range: 5,000–20,000 ms). On progress default: 24,000 ms (range: 5,000–45,000 ms). |
Compliance timer | If off, POM waits for classification results before starting the app or connecting to an agent, up to the CCA timeout. If on, POM waits until the compliance timer expires. If no result is received, it triggers Answer Human treatment. |
Start of voice timeout | Sets the wait time to detect voice. Default is 2,000 ms. Combined with live voice timeout, must not exceed the CCA timeout. |
Live voice timeout | Sets the wait time to detect a live voice. Default is 1,800 ms. Combined with start of voice timeout, must not exceed the CCA timeout. |
Driver app | Specifies the CCXML app used for outbound calls. The selected app must have all required resources (TTS, ASR). |
Allocation | Defines how ports are assigned. Default is dynamic port allocation. |
Call pace | Sets the number of call attempts made during the selected time unit. For example, 100 calls per minute. |
Min. ports | Sets the minimum number of ports used for campaign dialing. |
Max. ports | Sets the maximum number of ports used for campaign dialing. |
Call pace time unit | Time unit used to apply the call pace. Options: Seconds, Minute, or Hour. |
Was this article helpful?