VAN Canvass Results for System Call Results and Script Results
This guide will cover some of the finer details needed for understanding the outcomes generated by calling in ThruTalk and the data your VAN is receiving. To learn more about System Call Results and Script Results click here.
System Call Results versus Script Results and their outcomes
Your list will produce two types of "canvass" code results to sync to VAN:
- System results - are collected from calls where the call is not answered or when the sound detected by the dialing system is not a human voice.
- Script results - are collected from calls that are delivered to your callers. These outcomes are selected manually through the starting question template. The default starting question must be used, and the existing selections can not be edited for the sync to work correctly.
System results will sync to VAN with these "canvass" codes applied to the call results for calls not answered by a human:
- Voicemail = Not home
- Busy Signal = Not home
- Deliverability Error = Deliverability Error
- No Answer = Not Home
- Not Dialed = Does not sync. for how to use those results.
Script results will sync to VAN with these "canvass" codes, which are unchangeable for the Starting Question Template:
Note: If the caller does not record script results, the canvass code will sync back as “not home”.
The default starting question is recommended for accurate syncing of system call results.