Feedback

  • Contents
 

IS_Action_SkipPreviewCall

Definition

This function is essentially equivalent to using IS_Action_CallComplete, but with a wrap up code of ‘Skipped – Agent Skip’. This action skips a call that has been previewed.  This action is used when the calling mode is set to Preview—whereby agents are presented with the next call record and given the choice to place the call, skip, reschedule, or delete the call record.  IS_Action_SkipPreviewCall should be used when an agent presses a button to skip the call.  It tells Dialer that another preview call is needed.

This action does not make the record uncallable under any circumstances. Once IS_Action_SkipPreviewCall has been initiated, no further changes can be made to the Dialer attributes.  All element data is written to the server.  If an update occurs to an element after this action, the update will be lost. Scripter will recognize click events from any HTML element whose name has an associated action documented in this API (e.g.: "IS_Action_CallComplete").  If the script needs to associate several buttons with the same action, then define the action using a meta element and call the click event on the meta element from the button(s).

Attributes

The IS_Action_SkipPreviewCall element has the following attributes:

wrapupcode

The wrap up code to be used for the disposition.  This should be the full wrap up code e.g. Skipped - Agent Skip.

[abandoned]

The optional Abandoned attribute indicates even though the outbound call achieved call connect and routed to an Agent, the Dialer should consider it abandoned from a pacing, compliance and reporting perspective.  The default value of this attribute is false.

[callback]

The callback property ensures that this action executes asynchronously in Interaction Connect. Starting with 2018 R3, all Interaction Scripter actions (IS_Actions) provide a callback property for use in Connect scripts only. In the example below, statements inside the highlighted callback function block execute only after the action completes. The callback will return an error if the action fails. See Writing custom scripts for Interaction Connect or Scripter .NET.

Here's how to use the .callback property in a script for Interaction Connect:

function IS_Action_SkipPreviewCall() {
  IS_Action_SkipPreviewCall.wrapupcode = "Skipped - Agent Skip";
  IS_Action_SkipPreviewCall.callback = function(error) {     if (error) {       console.error("IS_Action_SkipPreviewCall failed.");     } else {       console.log("IS_Action_SkipPreviewCall succeeded.");     }   } }

Example 1

This is an example of a "Skip Call" button that skips the Preview call that has been presented to the agent.

<body>
    <input type=button name="IS_Action_SkipPreviewCall" value="Skip Call">
</body>

Example 2

This is an example of a "Skip Call" button that invokes the "SkipCall" script function. The WrapUpCode attribute is manually populated with the appropriate value before the call is dispositioned.

<head>
    <meta name="IS_Action_SkipPreviewCall">
    <script language=javascript>
        function SkipCall() {
            IS_Action_SkipPreviewCall.wrapupcode = "Skipped - Agent Skip";
            IS_Action_SkipPreviewCall.click();
        }
    </script>
</head>
<body>     <input type=button value="Skip Call" onclick='SkipCall()'> </body>

Example 3

<head>
    <meta name="IS_Action_SkipPreviewCall">
    <script language="javascript">
        function IS_SkipPreviewCall(p_page) {
            IS_Action_SkipPreviewCall.wrapupcode = "Skipped - Agent Skip";
            IS_Action_SkipPreviewCall.click();
            if (p_page != null) location.href = p_page;
        }
    </script>
</head>
<body>     <input type=button value="Skip Preview Call" onclick="IS_SkipPreviewCall(null);"> </body>