Visits
Limitations & best practice

Visits — Limitations & best practice

Tips for managing Visits: permissions, audience limits, address filtering, routing, outcome tracking, and best practices.

June 26, 2026
ID:
250

Access and permissions

  • Visibility of Visits depends on administrator setup and user permissions. If a team member cannot see the Visits menu, it has not been enabled for the account or for that user — have an administrator enable it and grant access.

Audience limit

  • Lists over 5,000 records cannot be selected in the Audience step. If a list exceeds this limit, split or refine it before adding it to the visit.

Address filtering

  • The address type filter is optional. Leaving it blank means no restriction by type, so every address on the included contacts is eligible. Address types are account-configured, so the available options depend on your setup. For door-to-door runs, the common practice is to select a street-style address type.
  • Primary address only is a separate checkbox that limits the run to each contact's primary address. Use it when you only want to visit people at their primary location.

Route ordering

  • You choose Group addresses by: Street or Suburb in the builder (Step 2). Within each group, addresses are split by odd / even house numbers automatically — this odds/evens ordering is built in, not a configurable setting. The result is optimised for on-foot runs rather than driving, and addresses cannot be manually re-ordered.

Outcome discipline

  • Use the in-field actions consistently so the Visits landing page breakdown is meaningful:
    • Contact made = you reached someone and completed the survey (rolls up to Successful).
    • Nobody available = attempted, but no one was available (rolls up to Unsuccessful).
    • Skipped = no attempt made at all (rolls up to Unattempted).
  • Only Contact made (with the survey submitted) creates a Post and writes back to the contact's profile, so make sure you complete the survey when you do make contact.

Building and resuming

  • You do not have to build a visit in one sitting. Use Save and close mid-build, and Finalise list only when you are ready to run the visit.

Best practice

  • Set Visited by me and the Visit time accurately at each door — these drive reporting.
  • Apply address tags in the field to capture context (for example, access notes) for future runs. Tags are account-configured and have no defaults, so set them up before relying on them.
  • Use Someone Else to capture conversations with people who are not yet contacts, rather than skipping the interaction.
  • Seed audiences from saved Lists where possible for speed and consistency, and add individuals only for one-off additions.