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, refer to our guide about System Call Results and Script Results.

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. To redial those contacts, refer to our guide on Dialing Hour Enforcement.

Script results will sync to VAN with these "canvass" codes, which are unchangeable for the Starting Question Template:

• Deceased = Deceased
• Deliverability Error = Deliverability Error
• Moved = Moved
• Not home/No Contact = Not home
• Refused = Refused
• Voicemail = Not home
• Wrong Number = Wrong Number

NOTE - If the caller does not record script results, the canvass code will sync back as "not home."

All starting question results, excluding "Talked to correct person," will sync to VAN with their applicable canvass code. This means if you branch to a survey question or activist code its applicable canvass result will not sync to VAN unless branching from "Talked to correct person." 

The default starting question is uneditable to ensure accurate syncing of system call results.