Interaction Connect Supports Custom Outbound Scripts

Starting with PureConnect 2018 R3, call center agents can use Interaction Connect to process outbound Dialer calls with custom script screen pops. Previously, Interaction Connect supported base scripts only. Agents were required to use Interaction Scripter .NET client for campaigns with custom scripts. To use Interaction Connect instead, custom scripts must conform with new programming requirements.

Interaction Connect processes JavaScript asynchronously, breaking tasks into threads that execute independently. Conversely, Interaction Scripter .NET is synchronous. It waits for each script statement to finish before moving to the next. For this reason, Interaction Connect and Scripter .NET have divergent programming requirements.

• Custom scripts must be written for one client or the other.

• The same custom script cannot be used in both Scripter .NET and Interaction Connect.

• Legacy scripts written for Interaction Scripter .NET work as before in that client application.

• To be compatible with Interaction Connect, scripts must implement callback functions that indicate when asynchronous operations complete.

• Scripts written for Scripter .NET should not implement callbacks designed for Connect.

For more information, see Writing custom scripts for Interaction Connect or Scripter .NET, in the Interaction Scripter Developer's Guide.