Skip to content
Use cases

Keep territory ownership and team access clear.

Multiple territories introduce questions a single crew does not face: who owns an inquiry, who may see the customer, and which team should do the work? Go Time includes organization and routing workflows that can support those conversations.

Lead pipeline in Go Time
Lead pipeline · Product view styled in light mode. Available views depend on role and setup.
01 / The context

A shared brand does not mean shared responsibility for every job.

Separate organizations and roles need deliberate setup. Decide which staff work within a location and who needs broader oversight. Keep routing and reporting expectations explicit so an inquiry is not bounced between teams and a local user does not receive inappropriate access.

02 / The workflow

What this looks like in practice.

  1. Map the operating structure

    List the locations, territories, users, and responsibilities. Bring the structure to a demo and identify any corporate oversight requirements. Confirm how your business maps to organizations and permissions before importing customers or assigning staff.

  2. Define lead ownership

    Review territory-based or round-robin routing where applicable. Decide who handles overlapping areas, missed responses, and reassignment. Test examples at the boundary between locations, because those are the cases most likely to expose unclear rules.

  3. Validate local and oversight views

    Review a location user’s experience and the authorized oversight experience separately. Check customer visibility, job assignments, and reporting scope using representative examples. Include access review in onboarding and when staff responsibilities change.

03 / A closer look

Example: an inquiry near a territory boundary.

The team checks the applicable rule, assigns the inquiry to the appropriate location, and records the next action. If responsibility changes, it follows the agreed reassignment process. This example illustrates governance; it does not promise unrestricted sharing of every record across organizations.

Keep the handoff clear

  • Territories and responsibilities mapped
  • Boundary cases tested in routing
  • Access reviewed by role and organization
04 / Questions worth asking

Before you get started.

Does unlimited users mean unlimited organizations?

No. Unlimited users describes the published user allowance. Review multi-organization structure, provisioning, and commercial terms with the team.

Can every location see every other location’s customers?

Do not assume that. Access depends on organization structure, roles, and permissions. Verify the exact local and oversight views during configuration.

Your business, your workflow

Bring a real job. We’ll walk it through.

See the office side, the field side, and the handoffs in between. Ask the questions that matter to your team.