Manage Canvassing Campaigns

The Canvassing workspace combines campaign setup, mapped territories, assignments, property loading, field rules, competitions, and reporting. Owners and managers can create and edit campaign basics from the native mobile app or use the web command center for complete setup. Assigned representatives complete field work from the native app.

Enable Access

The organization owner can open Canvassing and select Enable Canvassing. Enabling or disabling the feature changes access to the module but does not delete historical campaigns, visits, or GPS records.

The default access model is:

Custom roles use View Canvassing and Manage Canvassing. View-only users are restricted to their active assignments. Creating campaigns, importing properties, changing assignments, editing settings, and reopening completed work require Manage Canvassing. Organization-wide raw GPS remains limited to owners and managers even if another role receives a custom manage permission.

Native property context follows the same layered access model. An assigned representative can see the selected target and its canvassing attempt history. Linked estimate summaries additionally require View Clients and View Estimates; prior-service summaries require View Clients and View Jobs. A role without those permissions sees an unavailable message rather than a misleading empty history. Grant the underlying permissions only when that representative should see those CRM records.

Create a Campaign

On mobile, open Canvass > Campaigns from the manager team-map header or + Manage action. Select +, enter the name, offer, description, and date window, then choose whether to create it as Active or Draft. Select an existing card to edit those details. The cards also provide the allowed activate, pause, resume, complete, reopen, archive, and restore actions.

On web, open Canvassing > Campaigns & territories.

1. Under New campaign, enter the campaign name and optional offer.
2. Select Create campaign. The web quick-create action starts the campaign

as active; use Pause immediately if field work is not ready.

1. In Campaign lifecycle, add or revise the description, offer, start date, and end date.
2. Use Activate, Pause, Resume, Complete, Archive, or Reopen as the campaign changes.

Duplicate creates a clean draft with the prior campaign details, territories, and target properties. It does not copy active assignments, shifts, visits, or historical results.

Archived campaigns can be restored to a draft. Completed campaigns can be reopened as active when more work is required.

Creating or refreshing a campaign does not recenter the map. After you pan or zoom, the command center keeps that camera position while it refreshes properties for the visible area, and it preserves your saved Map or Satellite choice. The property list opens with 25 rows and supports 25, 50, or 100 rows per page.

Draw and Assign a Territory

Mobile

On the manager Canvass team map:

1. Select an active campaign.
2. Select Draw territory.
3. Tap at least three different map points around the work area.
4. Use Undo or Clear if the boundary needs correction.
5. Enter the territory name and select at least one eligible rep.
6. Select Save territory.

The mobile server validates every selected rep as an active workspace member, then saves the boundary and assignment set together. If the assignment step fails, it cleans up the new boundary. Unassigned territories are still listed for managers and can be assigned later with Balance doors.

Manage Houses and Knocks on Mobile

After selecting a territory, the manager map loads its complete paginated target set and displays up to 500 map markers, prioritizing houses with recorded attempts. The Territory houses card shows total, knocked, unvisited, and do-not-knock counts plus the most recent activity.

Select Edit boundary to reshape a saved territory. Trace the replacement outline by dragging on the map, use Clear or Undo as needed, and save. Only the polygon changes; campaign membership, assignments, targets, attempts, and dispositions remain intact.

Tap a marker or Dispo row to review append-only attempt history and record a new outcome. No-contact outcomes appear in a compact swipeable control and save with one tap; Conversation / details opens required notes, contact, follow-up, and appointment fields. Contact outcomes provide a multi-select service picker for common residential work, and those selections carry into the estimate handoff. Qualified visits can use Save + quote to create or match the Door Knocking lead, assign the signed-in rep, and open the native residential builder immediately. Manager entries use the same server disposition configuration and validation as representative entries. Quote Sent and Sold are explicit lead-backed outcomes: each requires a confirmed customer name and creates or matches the Door Knocking client and lead before the visit can be stored. Tap an empty point inside the boundary to reverse-geocode and add a missing property; normal organization, active campaign, boundary, duplicate-address, nearby-coordinate, and idempotency checks still apply.

Web

1. Under New territory, select a campaign.
2. Select Draw boundary.
3. Click at least three map points around the work area.
4. Enter a territory name.
5. Select one or more active owners, managers, or sales representatives.
6. Select Save territory.

More than one representative can share a team territory. Use Save assignments on an existing territory to replace its active assignment set.

Use Redraw boundary to edit a territory later. The new polygon must still contain every property already assigned to that territory. Existing visits remain attached to their original territory and are never rewritten by a boundary edit.

Territory Lifecycle

A territory can move through Assigned, In progress, Paused, and Completed. Normal completion is blocked while unvisited properties remain. A manager can enter an override explanation and complete the territory when a documented exception is necessary.

Use Reopen to return a completed territory to paused work. Assignment changes and lifecycle transitions are locked while they are saved so an active shift cannot race a removal or completion.

Move Unvisited Properties

Use Move unvisited properties to transfer selected targets between territories in the same open campaign.

• Only properties with no recorded attempt can move.
• Visit history never moves.
• A direct target assignee is cleared during the move; review destination assignments afterward.
• A single operation is limited to 500 selected targets.

Load Target Properties

Every property belongs to the organization and can be reused in later campaigns. A campaign target connects that property to one territory for the current campaign. Clean Estimate Pro compares both normalized addresses and coordinates so CSV, CRM, map-entry, and field-created properties share the same duplicate rules.

CSV Import

Download the sample from Property CSV import. Supported columns are:

address_line1,address_line2,city,state,zip,latitude,longitude,parcel_id,owner_name,property_type

Select the campaign and territory, choose the file, and select Preview import. The preview shows valid rows, invalid rows, existing properties that will be reused, exact-address and nearby-coordinate matches, duplicates inside the file, geocoded rows, cache hits, unresolved addresses, and properties outside the territory.

Important limits and safeguards:

• A file can contain up to 5,000 rows and 5 MB of CSV text.
• Quoted commas, escaped double quotes, Windows or Unix line endings, and line breaks inside quoted fields are supported.
• Malformed quoting, duplicate header names, missing or extra columns, oversized cells, and latitude without longitude (or longitude without latitude) are rejected during preview.
• At most 100 missing-coordinate addresses can be geocoded in one request. Add coordinates or split larger geocoding batches.
• Geocoding happens on the server and uses a private key.
• The secure geocode cache is reused when possible.
• Unresolved or out-of-territory rows block confirmation; nothing is silently placed outside the boundary.
• A coordinate within 12 meters of an organization property is treated as the same property, even when the submitted address is formatted differently.
• An existing property is reused without replacing its saved organization details.
• A target already used elsewhere in the same campaign is not silently moved.
• Preview and confirmation repeat the duplicate checks. CSV, CRM, map, and field submissions are serialized at the organization level so simultaneous requests cannot create nearby duplicates.

The preview is a validation step. No properties are written until you select Confirm properties.

Add a Property from the Map

Under Add property from map:

1. Select an open territory.
2. Enter the street, city, state, and ZIP.
3. Select Pick exact point on map and click the property location.
4. Select Add property.

The point must be inside the selected territory. If the normalized address already exists or an organization property is within 12 meters, Clean Estimate Pro reuses that property instead of creating a duplicate. It does not silently move a target that is already assigned elsewhere in the campaign.

Load Existing Clients or Leads

Use Load CRM properties to search complete service addresses from existing clients or leads.

1. Choose Existing clients or Existing leads.
2. Select an open campaign and territory.
3. Search by name or address.
4. Select records from the current page.
5. Select Add selected properties.

All selected addresses must resolve inside the territory before the batch is added. Exact-address and within-12-meter matches reuse the organization property, reused properties keep their CRM links, and an existing campaign target is not moved to another territory.

Property Provider Integrations

The server includes a vendor-neutral adapter interface for future parcel or address providers. The core product does not require a provider, and the current manager screen does not present a provider search/import control. CSV, map entry, clients, and leads remain the available manager property sources until an integration package registers and exposes a provider workflow.

Configure Field Policy

Open Canvassing settings > Field policy.

The default review distance is 150 meters and the default raw GPS retention is 180 days. A distance flag saves the visit and asks for review; it is not an automatic accusation or proof of misconduct.

The server can also attach review signals for mocked-location reports, outside or unverifiable territory boundaries, implausible travel, unusually rapid door activity, repeated visits clustered at one point, low shift coverage, and long location interruptions. When route data is available, the review evidence includes the nearest route point from the same representative and shift within the surrounding time window, including its time and distance from the visit. These are non-accusatory integrity prompts for human review, not automated employment decisions.

Choose retention and employee-notice practices that meet your local legal and labor requirements. Background tracking runs only during an active canvassing shift.

The current manager AI surface remains aggregate and scoped even when the private-coaching policy preference is on; it does not expose a conversation archive.

Review Recovered Visit Requests

Each mobile door action has a durable request identity bound to the organization, representative, assignment, shift, target, and submitted details. A retry reuses the completed visit instead of creating another attempt, lead, appointment, or automatic customer message. If an interrupted request must be recovered after its processing lease becomes stale, Clean Estimate Pro reuses any durable CRM intake result, suppresses automatic communications, and adds a manager-review reason. Completed request fingerprints are retained for 45 days—beyond the supported 30-day offline replay window—then removed in bounded service-only batches; active or recoverable claims remain. Review the property history and linked CRM records before manually contacting the customer.

Configure Outcomes

Open Canvassing settings > Dispositions to review system outcomes or add an organization-specific outcome.

For each custom disposition you can set:

• Label, stable code, icon key, marker color, and sort order
• Whether it is active or completes the target
• Whether it counts as a conversation, qualified lead, or appointment
• Whether a note or follow-up is required
• Whether it creates an organization-wide do-not-knock restriction

System dispositions are read-only. Custom dispositions can be edited or archived. The web and native maps use the configured label, color, and status abbreviation, so color is never the only status indicator.

Do-not-knock applies to the reusable organization property across campaigns. Clearing or adding it from the property panel requires a manager explanation and records the override. A representative's confirmed mobile restriction is also projected immediately across every downloaded target for that property, including offline copies, while the authoritative server write waits to synchronize. When a connected representative opens a property from a stale map page, the fresh server projection likewise applies a newer office or teammate restriction across every downloaded target for that property before the sheet allows another outcome.

Configure XP, Goals, and Templates

Open Canvassing settings > XP & goals to:

• Enable or disable gamification.
• Choose full standings or rank-only representative privacy.
• Choose the native representative leaderboard's featured metric: balanced scorecard, XP, unique doors, conversations, qualified leads, appointments, estimates sent, sales, completed revenue, contact rate, appointment rate, or close rate. XP ranks by signed XP; every other selection keeps the main rank on the balanced scorecard and emphasizes the selected count, currency value, or percentage without turning that value into the ranking by itself.
• Set an optional temporary XP multiplier and expiration.
• Set XP values for verified visits, CRM outcomes, estimates, sales, jobs, Suds Club sales, and completed revenue.
• Store daily, weekly, and monthly representative goals.

XP is server-authoritative. A mobile button tap does not award XP by itself; the server validates the underlying event and uses source-linked idempotency to prevent duplicate awards.

Leaderboard XP is projected from the same signed XP ledger. The server accepts only known canvassing event/source pairs whose live visit, target, shift, competition, achievement, or downstream attribution belongs to the same organization and representative. Direct browser writes to XP events and gamification profiles are blocked. When completed work is reopened or cancelled, an immutable negative reversal remains visible in period XP; a balanced score never turns that penalty into a positive contribution.

Use Estimate templates to store up to 12 named residential starting-point configurations with approved service keys, an optional package key, and a customer note. After a representative records an eligible outcome during the current shift, the native Canvass flow presents these as quick-estimate choices. Selecting one opens the standard Residential Estimate builder with the approved starting values; it never overrides configured pricing, tax, discount authorization, or Red Line controls.

Before a field rollout, confirm the active residential price book has one supported row for each offered service, valid add-on size options, current approved custom-item templates, and a published Suds Club setup if the team offers membership. Native builders receive those values and the rep's effective permissions in one revisioned server bundle. Sent estimates must match the exact revision and server-calculated total that the rep reviewed, so a pricing or catalog change made while a phone is offline stops the stale send for review instead of silently carrying the old price forward.

Set the organization's IANA timezone under Settings > Company Information before a pilot. The native Your verified goals panel shows daily doors and contacts, weekly qualified leads and appointments, and monthly sales and completed revenue in that timezone. Goal and leaderboard windows are derived in PostgreSQL for Today, Week, and Month, including daylight-saving transitions, repeated local midnights, and skipped local midnights, instead of using fixed UTC boundaries. The same organization-local bounds apply to operational, XP, and balanced-scorecard standings. Organizations upgraded without a saved valid timezone use UTC until an owner selects another IANA zone.

The web command center labels From and To with that IANA timezone. Reset selects the organization's current calendar date and the prior 29 dates. Date-only edges use the first real instant of the local start date through one millisecond before the first real instant of the next local date, including daylight-saving dates whose midnight is skipped or repeated. Reports, property results, representative drills, route review, CSV exports, and Manager AI therefore share one calendar scope. Report headings and daily activity chart buckets use the same organization-local calendar dates and identify the timezone.

Progress comes from server-validated visits and attributed outcomes; visits waiting for manager review do not increase operational goals. Contact, appointment, and close rates follow the cohort of verified visits in the selected period, including later linked outcomes. Appointment, estimate, sale, and revenue cards credit the period in which the downstream activity occurred, so their counts can intentionally differ from cohort rate numerators. The native full-screen standings panel can filter by authorized campaign, territory, and Sales reps only, and each card includes verified doors, contacts, qualified leads, appointments, estimates sent, sales, revenue, contact, appointment, and close rates, plus XP. The configured metric is promoted and highlighted on every card even when the main rank remains balanced. Owners and managers receive organization-wide live campaign and territory choices; representatives receive only active assigned scopes. The native result is bounded to the top 25 plus the current representative's own row, including at most 26 identity profiles.

The mobile app refreshes only while the standings panel is open, using a staggered interval of about 120–150 seconds and a stable-principal server rate limit. A live full-visibility response can show the top 25 plus the current representative, but those teammate identities are never persisted. Version 4 offline standings retain only the signed-in representative's own row under the private Current user label, with the download time and exact organization, user, period, campaign, territory, and role-filter provenance for no more than five minutes. Echoed period, filters, and ordered organization-timezone bounds must match; malformed, incomplete, expired, more-than-30-seconds-future, or differently scoped snapshots are rejected. Legacy version 3 identity-bearing snapshots never render and are removed when cache maintenance can write. Authorization failures, disabled standings, and rank-only privacy changes purge incompatible data; if a local privacy purge fails, an in-memory barrier blocks later offline standings for that organization and user until a safe authoritative result is cached.

Drill into representative results

In the web command center, open Reporting and select a representative's name to inspect verified visits, or select the linked Verified doors, Estimates, or Sales value to inspect that exact source type. Clean Estimate Pro preserves the selected representative plus the report's organization-local date, campaign, territory, disposition, and address filters, then switches to a paginated Field list containing only matching verified source targets. Visits waiting for manager review and records outside the live organization scope are excluded.

The Source representative, match-count, and Last matching activity columns describe the exact source set. Match count follows the selected focus: one distinct verified door, individual verified visits, distinct linked estimate records, or distinct sold targets. A campaign and territory label disambiguates the same reusable property when it appears as more than one canvassing target. Select Details to carry that exact target ID, representative, period, campaign, territory, and disposition scope into the matching visits and estimate or sale attributions. Appointment and sale conversion in the drill follows the selected verified-visit cohort, including linked outcomes recorded later. This makes the aggregate traceable to its exact source records without weakening normal organization, property, or CRM access checks.

Run a Competition

Under Team competitions:

1. Enter a name, start and end time, metric, minimum qualifying activity, prize or recognition, and optional XP bonus.
2. Optionally scope the competition to a campaign, territory, or selected eligible users.
3. Create the draft and select Activate when ready.
4. Review View standings before selecting Finalize.

Supported competition metrics include doors, conversations, leads, appointments, estimates, sales, completed revenue, and XP. Finalization stores the reviewed standings and winner. A contest-linked XP bonus is idempotent, so retrying verification cannot intentionally award it twice.

The competition panel and the organization XP leaderboard are related but separate. A contest is described as an XP competition only when its selected metric is XP.

Next Steps

• Send representatives to Door-to-Door Canvassing.
• Review results in Canvassing Reporting and Exports.
• Configure safe assistance with Canvassing AI.
• Complete Canvassing Launch Readiness before enabling a live organization.