This is a script for handling incoming communications. It can call or be called by other scripts. When the subsidiary script completes, the calling script resumes. The calling script can pass parameters to the subsidiary script using variables, and the subsidiary service can pass parameters back to the parent. You are able to nest scripts up to ten levels deep in this way. This allows you to adopt a modular approach to your workflow designs, and to create reusable scripts that perform a specialised task across multiple services.
See also, Create a Script for Handling Incoming Communications.
This is a script for use in OUTBOUND campaigns only exposing additional functionality that is used in outbound services. Creating such scripts is described in the storm OUTBOUND Configuration Guide.
This is designed to perform tidy-up routines (for example, database updates) when a script ends and is particularly useful in a call-handling service. If you configure a script to call a clear down handler script, the clear down handler script runs as soon as the parent script ends but also if one of the parties hangs up before the script has finished.
Note: you can run a clear down handler service only from a main script, and not from a subsidiary script. However, when a subsidiary script ends, its user variables can be passed back to the parent, allowing a single clear down handler to perform clean-up operations for nested scripts.
See also, Implement a Clear Down Handler.
This is a script used exclusively for conducting a text-based survey with customers engaged in text-based interactions such as web chat. The script must be called by another script. When this subsidiary survey script completes, the calling script resumes.