Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.


Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Delivery and Retry Options

Use the Delivery and Retry options to define how the system should handle a call in any given scenario. More specifically:

  • Use Delivery options to define the circumstances in which the system either connects the call to an agent or drops the call (available for the voice channel only).
  • Use Retry options to tell the system how to respond to a particular delivery result or disposition code.

This article describes all Delivery and Retry options. It focuses heavily on Retry options and provides detailed instructions on how to define a treatment plan. If you're looking for information about device escalation, go here. For information about SCXML-based treatments, go here.

Delivery Options

Use the Delivery Options tab to define the circumstances in which the system connects a call to an agent.

By default, the Deliver to Live Person option is enabled and cannot be disabled. When the system detects a voice on the line, it connects the call to an agent.

Click Advanced to see more delivery options. By default, the system drops the call if it detects an answering machine, fax machine, or silence. When you enable any of these options, the system connects the call to an agent within the agent group. Optionally, you can change the default destination DN if you want to connect the call to a different routing point.

Retry Options

Use the Retry Options tab to define the way in which the system retries contact attempts based on either a delivery result or a disposition code. For example, you could specify the following:

  • If the delivery result is Busy
  • Wait 30 minutes (Interval)
  • Then redial the number (Apply to Record action)
  • Every 5 minutes (Increment)
  • Up to a maximum of 3 times (Retry Count)
  • Then move to the next record in the chain and apply the same treatment (Next Action)

This section describes how to create a treatment plan like the one outlined above.

The first part defines the following key menu options:

Then, you'll learn how to define a treatment based on either a delivery resultor a disposition code.

Retry Options (Treatment Properties) Defined

The following table defines all available Retry options.

Retry Option Description
Delivery Result Used when the treatment plan is based on the result of a contact attempt (a voice call or a text). See the Treatments based on Call/Delivery Results for more information.
Disposition Code (Applies to the voice channel only) Used when the treatment plan is based on disposition codes. See Treatments based on Disposition Codes for more information.
Apply to Record Defines the action the system takes in response to a given delivery result or disposition code. See the Apply to Record Options section for a description of each option.
Retry Count The maximum number of consecutive attempts to retry a record.
Interval The time (measured in DD:HH:MM) that the system waits between the first contact attempt and the first Apply to Record attempt.
Increment The number of minutes added to the previous redial time interval.
Date/Time Required when you select Retry at a specified date or Next in chain at specified date from the Apply to Record menu.
List Required when you select Suppress from the Apply to Record menu. All suppression lists stored in CX Contact with an expiration date set to Never, regardless of type (Client ID or Device), populate in this menu.
More Enables you to change Copy Contact configurations.
Next Action Defines the way in which the system moves through a batch of chained records after the Apply to Record action has been completed. See the Next Actions section for more information.

Apply to Record Options Defined

Apply to Record defines the action that results from a given delivery result, delivery result, or disposition code. In the example statement If the delivery result is Busy, redial the number, the Apply to Record action is Redial.

The options are as follows:

  • Redial - Redials the number.
  • Retry in - Retries once according to the values specified in the Retry Count and Interval fields (for example, retry once in 60 minutes).
  • Retry at specified date - Redials the record on the date specified in the Date field.
  • No Treatment - Does not apply a treatment.
  • Suppress - Adds the record to the suppression list specified in the List menu.
  • Copy Contact - Copies the contact from the current Contact list to a target contact list. There are two types of Copy functions:
    • Copy as General (or as new) - Creates a new General record in the Target Contact list with immediate availability.
    • Copy as Rescheduled - Creates a new Rescheduled record in the Target Contact list that will be processed after a specific delay (for example, 2 hours).

The Retry options available to you depend on the Apply to Record option you selected. This table illustrates the available Retry options for each Apply to Record action.

Apply to Record Options Retry Count Interval Increment Date/Time List
Redial
Retry in
Retry at specified date
No treatment
Suppress
Copy Contact

Next Action Options Defined

Use the Next Action options to define how the system should move through a batch of chained records based on a given delivery result, delivery result, or disposition code. The options are as follows:

Next Action Description
Next in chain The system immediately attempts the next record in the chain.
Next in chain after The system waits until the time specified in the Interval field before attempting the next record in the chain.
Next in chain at specified date The system waits until the date and time specified in the Date/Time field before attempting the next record in the chain.
Update all records in chain The system updates all chained records with the delivery results. It does not proceed with any of the next-in-chain actions.
Suppress then Next in chain Once a record has been added to target suppression list, the system immediately attempts the next record in the chain.
Suppress then Next in chain after Once a record has been added to target suppression list, the system waits until the time specified in the Interval field before attempting the next record in the chain.
Suppress then Next in chain at specified date Once a record has been added to target suppression list, the system waits until the date and time specified in the Date/Time field before attempting the next record in the chain.

The table below illustrates the mandatory Retry options for each Next Actions option:

Next Action Retry Count Interval Increment Date/Time List
Next in chain
Next in chain after
Next in chain at specified date
Update all records in chain
Suppress then Next in chain
Suppress then Next in chain after
Suppress then Next in chain at specified date
Example
  • Delivery Result: No Answer
  • Apply to Record: Retry In
  • Retry Count: 2
  • Interval: 00:00:30
  • Increment: 10 min
  • Next Action: Next in chain

With a chain of three records, the behavior is as follows:

  1. The system attempts the first record in the chain. There is no answer.
    • Retry 1: The system retries the record 30 minutes later. There is no answer.
    • Retry 2: The system retries the record after 30 minutes plus the additional 10-minute increment. There is no answer.
  2. The system dials the second record in the chain. There is no answer.
    • Retry 1: The system retries the record 30 minutes later. There is no answer.
    • Retry 2: The system retries the record after 30 minutes plus the additional 10-minute increment. There is no answer.
  3. The system attempts the third record in the chain. There is no answer.
    • Retry 1: The system retries the record 30 minutes later. There is no answer.
    • Retry 2: The system retries the record after 30 minutes plus the additional 10-minute increment. There is no answer.

The records are updated in the contact list and the system stops processing the chain.

Important

Notes about Next Actions:

  • When a chain ends, it is updated in the contact list and the system stops processing that chain.
  • The Interval and Increment options are not applicable to the Next in chain at specified date action.
  • If a record within a chain is suppressed, CX Contact continues to move through the chain according to the option specified in the Next Action menu.

Treatments based on Delivery Results

To define a treatment based on delivery results:

  1. Leave the Use Disposition Codes switch set to the Off position.
  2. Select one or more delivery results for the treatment (for example Busy),
  3. Go through the Retry Options to define the treatment.
CXC Treatments DispCodesOff.png
Example

For Busy delivery results, you want the system to do the following:

  • Wait 15 minutes before retrying the record
  • Retry the record a maximum of 3 times
  • Wait 5 minutes between each retry

To achieve these results, specify the following:

  • Delivery Result: Busy
  • Apply to Record: Retry In
  • Retry Count: 3 times
  • Interval: 00:00:15
  • Increment: 5 min

(The Date/Time and Next Action fields are not required. Refer to the Next Actions section for an example using a Next in chain action.)

CXC TreatmentExample.png

Description of Delivery Results

The following table describes all possible delivery results.

[+] Click for a description of delivery result values

Treatments based on Disposition Codes

Important
This option applies to the voice channel only

.

To create disposition-level treatments:

First, create a business attribute in the Configuration Manager section of the configuration environment (Platform Administration or Genesys Administrator Extension). In the Business Attribute Values folder, create the list of disposition codes that you want to populate in CX Contact when you define the treatment.

CXC GAX DispositionCodes.png

For more information about business attributes, refer to the Business Attributes page in the Platform Administration guide (for cloud) or the Business Attributes page in the Genesys Administrator Extension Help guide (for premise).

Next, in CX Contact, go to the Settings page, and in the Disposition Codes field on the General tab, specify the display name of the business attribute that stores the disposition codes (Business Attribute Values). In the screenshot below, notice that the value in the Disposition Code field (CXC Disposition Codes) matches the display name of the business attribute (CXC Disposition Codes) in the screenshot above.

Important
When you create a business attribute, you specify a name and a display name for it. Always reference the display name in CX Contact.
CXC Settings CXCDispCodes.png

Then, in CX Contact, go to the Retry Options tab and do the following:

  1. Set the Use Disposition Codes switch to the 'On' position.
  2. Select one or more disposition codes from the Disposition Code menu.
  3. Go through the Retry Options to define the treatment.
CXC RetryOptionsAll.png
Important
If a treatment is defined for both a delivery result and a disposition code, CX Contact gives priority to the disposition code when applying the call treatment.
This page was last edited on September 24, 2019, at 11:08.

Feedback

Comment on this article:

blog comments powered by Disqus