SIGNAL

Communicates with another script by triggering the ONSIGNAL event.

Supported Script Types


Generic	Email	Chat	Phone	Voicemail	Work Item

ContactID: The unique identifier of the script to signal.
Parameters: A value (0-9) that indicates the number of parameters to send to the signaled script. Parameters are named SP1 through SPn (where n is the Param Count).

Default: The Default branch condition will be used unless another branch condition is met.
OnError: The Error branch condition is triggered if the Contact IDA unique numerical identifier assigned to each contact. does not exist.

Use SIGNAL to interrupt another script and pass parameters to it. Up to nine parameters may be passed. The other script may be actively processing other actions when the signal arrives. It will immediately abort whatever it is doing and jump to an ONSIGNAL event action, if one is present.
The current implementation does not ensure that multiple ONSIGNAL events will not interrupt one another. It is possible for a script to be signaled twice at the same moment and behave as if it were signaled only once. This can be avoided by careful script writing.
You must reference the correct Contact IDA unique numerical identifier assigned to each contact.. Typically this is handled by using a variable saved in the database using the PUTVALUE action.
An example would be creating an after-hours tech support script. A customer calls in and multiple scripts are spawned to call four on-call technicians at the same time. When one of the scripts reaches a live technician (rather than voicemail or no answer), the spawned script signals the original script and the two calls are joined.