|
Informs the calling script that the outbound call should not be made and dispositions |
Supported Script Types
|
| Phone |
Properties
| Property | Details |
|---|---|
| Disposition | Select a disposition from the drop-down that you want to result from this action firing. |
Branches
| Branch | Details |
|---|---|
|
Default |
Path taken unless the script meets a condition that requires it to take one of the other branches. It is also taken if the other branches are not defined. |
Tips & Tricks
- This action automatically passes back a FALSE value to the calling script indicating that the call should not be made.
- The END attribute must be checked in the Script Action Editor to enforce this as a final action within a script.
- The ability to customize who receives a call is accomplished through a suppression feature that intercepts dial requests and verifies that they do not exist in a customer-supplied suppression list.
- Administrators have the ability to enter a phone number into the system through CXone and compare outgoing calls against this list. If a match is found, it will suspend the dial attempt and return a specified disposition
Result that the agent or system assigns to the contact when the interaction ends. that indicates that it was suppressed. This is helpful to administrators who need certain phone numbers pulled from active calling lists. The list of matching phone numbers can be entered either individually or in a batch. A log report confirms all entries and changes made to the entered records. - This feature can be coupled with Addtodnc to ensure customers that do not wish to be called can be immediately suppressed from all active outbound Used to automate delivery of interactions based on agent skills, abilities, and knowledge.
- The application supports a web service interface that allows a CRM Third-party systems that manage such things as contacts, sales information, support details, and case histories. application to interface with CXone and to “approve” each call before it is dialed.
- The suppression system is able to accept input from the UI, Web Service interface, or an uploaded text file. Each suppression request that is defined to expire at a specified date and time in the future can optionally specify scope with a specified start time and end time.
- Suppresscall should not be used for mass suppression. The filters within the outbound strategy are a better method for that type of suppression.