Canvassing scripts
How to build a canvassing script with survey questions, branching logic, and automatic tagging from responses.
On this page
A script is the structured conversation volunteers follow at each door: opening text, a sequence of survey questions, and closing text. Create and manage scripts from the Scripts section of the canvassing workspace. One script can power many walk lists. See Canvassing for an overview of territories, walk lists, and sessions.
Managing scripts
Every script has three parts:
- Opening text: what the volunteer reads when someone answers the door.
- Questions: the survey the volunteer works through during the conversation.
- Closing text: the wrap-up statement after the survey is complete.
Attaching a script to a walk list
Attach a script when you create or edit a walk list. Only one script can be active on a walk list at a time.
Where responses are stored
Responses are captured per attempt. If the same address is visited in a later session, the new responses are stored as a separate attempt and do not overwrite previous ones.
Survey question types
Each question has a type that controls how the volunteer enters the response:
| Type | How the volunteer responds |
|---|---|
| Single choice | Picks one option from a list |
| Multiple choice | Picks one or more options from a list |
| Yes / No | Answers yes or no |
| Scale | Selects a number within a defined range |
| Support level | Records a support score for the contact |
| Number | Enters a numeric value |
| Text | Types a free-text response |
Choice-based questions carry answer options, and each option can specify which question to show next.
Branching logic
When branching is enabled, the survey adapts based on prior answers. A volunteer who confirms the contact is already registered, for example, skips the voter-registration section.
To set up branching, enable it on the script, then set a next-question on each answer option for choice questions. For conditions that span multiple answers, add skip rules directly on the question to be skipped. Where no rule applies, the survey advances in sequence.
Automatic tagging and field updates
A question can apply a CRM tag when a specific answer is selected. Selecting
"Strong support" on a support-level question can apply a strong-supporter tag
without post-session work. Tags applied this way are immediately available for
segments and follow-up campaigns.
A question can also write its response to a field on the contact record, useful for capturing a phone number collected at the door or confirming an address. The contact record updates when the session syncs.
Why this matters
Consistent scripts mean every volunteer delivers the same conversation, so your response data is comparable across teams and sessions. Branching logic keeps conversations relevant rather than forcing volunteers to read questions that do not apply. Automatic tagging turns door responses into actionable segments the moment a session closes, removing the manual step of reviewing transcripts. When your scripts are well-structured, the data you collect is ready to drive your next round of outreach without extra cleanup.