Do Not Call VAN Sync Result
When a contact is marked as Do Not Call during a ThruTalk call in a VAN-integrated campaign, that preference can be synced directly back to VAN. This helps maintain accurate contact preferences across platforms and ensures your volunteers don’t waste time trying to call people who’ve opted out. In this guide, we’ll show how that sync appears in VAN and what conditions must be in place for it to work properly.
TABLE OF CONTENTS
Reviewing VAN Do Not Call Contacts
Here’s how to confirm that a contact’s Do Not Call status has synced to VAN. When a contact is marked as Do Not Call in a VAN-integrated ThruTalk campaign, ThruTalk syncs a contact history record to VAN with the result code Do Not Call.
Screenshot of black text in a table on a white background from VAN. One entry shows a result code "Do Not Call." [NEW IMAGE]
In the Vital Stats and Contact Preferences section of the contact’s VAN record, the checkbox for Do Not Call will also be selected.
Sync Requirements and Troubleshooting Notes
Make sure the following conditions are met to ensure successful syncing.
- Canvass Result Must Exist: Your VAN committee must include the canvass result "Do Not Call." If it doesn't, the sync will fail. Contact your VAN admins to request that this result be added.
- API Key Required: VAN-integrated campaigns must use a ThruTalk account with an active VAN API key. For setup instructions, check out our guide on How to Set Up VAN Syncing Campaigns in ThruTalk.
- VAN ID Mapping: The mapping must match the script type. All groups or previous campaigns targeted in the campaign must be mapped with a VAN ID type that matches the script's committee type (either MyVoters or MyCampaign).
- Sync Status: Sync applies only to VAN-integrated campaigns. If a contact is opted out in a non-VAN-integrated campaign or marked as Do Not Call through other tools (such as the Do Not Call Management page or Phone Number Lookup page), that status will not sync back to VAN.