Door-to-Door Canvassing

The mobile app has a focused Canvassing screen for logging a door visit. It is not the full canvassing workspace described in Manage Canvassing Campaigns — there is no in-app map, door list, or shift tracking yet. A rep who needs to browse territory doors, see the map, or run a tracked shift still does that from the web app; the mobile screen only records what happened at one door.

Reach the Screen

Open More > Canvassing. This entry only appears for a member with the View canvassing permission. It is on by default for owners and admins and off by default for sales reps and crew; an organization can grant it to a specific rep the same way it grants other per-person mobile permissions.

The phone has no synced list of assigned or nearby canvassing properties yet, so the screen cannot be browsed by map or address. To log a visit, enter the property's canvassing ID — get it from a canvassing lead or a link they send you — and select Open.

Log a Visit

The visit screen shows:

• A short notice that the app looks up your position only when you tap

Save, only for that one visit, and never tracks location in the background or between visits.

• A Disposition picker: No Answer, Not Home, Not Interested, Interested,

Follow Up, Appointment Set, Estimate Created, Sold, Already Customer, Renter, Vacant, Inaccessible, Bad Address, and Do Not Knock. This is the organization's standard set; a disposition an organization has renamed or disabled on the web still shows here by its default label.

• A Note field. It is required for Follow Up, Inaccessible, and

Bad Address, and optional for every other disposition, up to 2,000 characters.

Select a disposition and add a note if one is required. For Follow Up, the signed internal Android preview also asks for Follow-up date (required) and Follow-up time (required). Both begin blank, so choose the intended date and time explicitly; the app displays the campaign's effective timezone. A daylight-saving time that does not exist is rejected. When a fall-back clock time occurs twice, the earlier instant is used and the app shows a notice. Other dispositions do not add these fields.

These approved mobile changes are scoped to the signed internal Android QA preview. They are not generally distributed; no public Android or iOS release is confirmed. Select Save visit after the required note and, for Follow Up, date and time are complete. A visit cannot be saved while the phone is offline; the screen disables Save visit and shows a reconnect hint until the connection returns. Visits are not queued for offline upload.

If a save response is uncertain, retry the same unsaved visit in the same form. The retry uses the saved visit, so it will not create a second visit.

Location Permission

The first time you save a visit, the app asks the operating system for foreground location permission. This is the same system prompt used for other one-time location lookups, and it exists so the visit can record how close your device was to the property. The prompt only appears once: after you grant or deny it, the OS remembers your choice and does not ask again on a later visit.

A visit still saves when location is denied or unavailable. Denying the prompt, a location timeout, or a device error never blocks or delays Save visit — the visit is recorded without coordinates. Nothing is lost, and there is no retry needed on your part.

When a position is captured, the app tries a fresh reading for a couple of seconds and, if that does not resolve in time, falls back to the device's last known position instead. This is a one-time lookup for that visit only; the app never tracks position continuously and does not run in the background.

After You Save

The saved-visit screen confirms Visit saved. If the captured position (or the absence of one) puts the visit far from the property's known location, the screen also shows a note that it was flagged for manager review. Select Log another visit to open the entry screen again, or Done to return to More.

What the Office Sees

The office interface does not display the coordinates captured for a visit. A manager reviewing canvassing activity on the web sees only whether a visit was flagged for being far from its target property, not a position on a map. This means a visit logged with location denied or unavailable looks the same to the office as one captured right at the door — both simply show as not flagged, unless the visit's distance (when a position exists) trips the review threshold. Do not tell a rep that the office can see exactly where they stood; it cannot.

What This Screen Does Not Do Yet

This is a visit-logging screen, not the full canvassing field workspace. It does not currently include a map, a door list, active-shift tracking, XP, competitions, AI coaching, lead or appointment capture, or an in-app path to build a residential estimate from a visit. Those workflows remain web-only or unbuilt on mobile; see Manage Canvassing Campaigns and Canvassing Reporting and Exports for the web workspace.

Upcoming on-shift route capture

The one-time visit lookup above is separate from route capture. Optional route capture remains off and is not available in the released app. It will collect only after the representative gives explicit consent and grants the required location permissions. Android requires precise location and background location. On iOS, foreground location must be granted as When In Use or Always, and background location must also be granted. iOS may provide approximate locations; the app cannot determine whether iOS is providing precise or approximate location, and the accuracy reported with each point is retained.

The internal Android preview now includes updated Android location permissions and a background-service declaration, plus startup progress messages. Its fresh cold-launch check reached the sign-in screen, but did not authenticate or start location collection. The cause of the earlier blank start remains unknown. The background task shares the app's Clerk provider and cached-session configuration and joins startup initialization already in progress. A task can stop waiting after its timeout, but Clerk's SDK cannot cancel a load already underway, which may finish later. Authenticated background cold-start and sign-out cleanup have not been verified. Route capture remains off; the preview checks do not make it available to representatives. Route capture will not run off duty, and will stop when the shift ends, the representative signs out or changes organizations, or canvassing access or a required location permission is lost.

Authorized teammates with Manage Canvassing can now save Point retention (days) (7 to 365) and Collection interval (seconds) (5 to 300) in web Canvassing settings > Location collection & retention. Blank values remain unconfigured; no defaults are selected. Saving the policy does not start collection. The selected period is intended for raw route points; non-coordinate shift summaries are retained. The retention purge is paused and has not completed a run, so the selected period is not an active deletion guarantee.

For the planned offline queue and shift-end retry behavior, see Working Offline. For the organization policy, see Manage Canvassing Campaigns.