All guides
Run the branch 6 min read

Who gets which lead: scope, zones, fit and rotation

The Routing tab is where you tell Team Flow which permits are yours, who takes leads, what each rep takes, and which names your customer file uses for them.

This guide is hands-on. Follow along in the app.
A free trial takes two minutes: 25 project views or 14 days, whichever comes first. No card.
Open this as a guided tour in the appTeam Flow, with Scout · 11 steps on the real screen. Sign in first if you are not already.Start

Two answers switch routing on: where you sell, and who takes leads. Everything else on the Routing tab is refinement. The order leads route in never changes, and the page states it: the rep who owns the account, then the rep who has worked that builder before (two or more past leads), then the rep whose zone the site is in, then rotation.

The Routing tab: the routing order written out in one paragraph, then the rep names found in the customer file with a Routes to dropdown for each
The Routing tab states the order, then asks you to link the rep names your customer file uses.

Scope: which permits are yours

The card at the top reads your scope as a sentence (Kelowna, Vernon, Kamloops, Penticton · Lumber & Framing, Windows & Doors) and it is the whole team's. Edit it here and three questions open: Where do you sell? (a province, a region, or municipalities, one level at a time), What builds do you supply? (the project-type groups, and whether you take new builds, alterations, or both; a house alteration is filed as a house, so this is the only way to leave those out), and Smallest job worth a rep's time (the build's cost, never your invoice). A live count tells you how many permits in the latest import match before you apply.

NoteThis is Territory Intelligence's setup, saved once. Change it here and the Territory page changes; change it there and the week changes. There is no second copy.

Link the names in your file

If your customer file has a rep column, the tab lists every name it found, how many accounts carry it, and a Routes to dropdown. Until a name is linked, that rep's accounts route by zone and rotation; once it is, they route to that teammate first. A name that is not on the team yet: invite them, or pick whoever covers those accounts now.

Each rep: takes leads, fit, zones, share, names

  • Takes leads is the switch. An unticked rep gets nothing, not even their own accounts.
  • Fit is which builds they take: project-type groups, new builds or alterations, and a value range. Zone and rotation only deal them those. Fit is eligibility, never relevance: it never shrinks the week. A lead nobody fits stays on This week under No eligible rep until someone's fit covers it or you pick a rep by hand.
  • A relationship routes past fit. A builder they own, a name in your file, or a builder they have worked twice still goes to them, flagged Outside their fit.
  • Zones are their patch, picked from the same zones Territory scored. Two reps can share a zone; each new lead there goes to whichever claimant takes that kind of build and has the fewest open assigned leads, and the page tells you who is up next.
  • Share weights the rotation. 2 gets twice the rotation leads of 1; 0 opts a rep out of rotation but keeps their account, zone and history leads.
  • Names in your files are the spellings your customer file or ERP uses for this rep (Sarah, S. Miller). Same link as the table above.

What to set on day one

  1. 1
    Scope, then reps
    Set where you sell and which builds. Tick Takes leads on every rep who works new leads.
  2. 2
    Link the file's rep names
    If you have a rep column, link every name. This alone routes most of the week correctly, because ownership beats everything.
  3. 3
    Claim zones
    Give each rep the zones they actually drive. Leave fit wide open unless a rep genuinely never sells into a build type; a narrow fit just pushes leads into No eligible rep.
  4. 4
    Let history earn ownership
    When a Worked them before row is right, tap Make it their account. From then on it is a statement, not an inference.
Keep reading
Set up your territory and load your customer file
Run the branch · 7 min
Reading the gap: your accounts, the leak, and the zones
Run the branch · 6 min
The free coverage check, and what happens to your file
Run the branch · 3 min

See it on your own area

Everything in this guide runs live in BuildMapper: a scored map, the right time to call, Scout, your AI assistant, and a pipeline. Free trial: 25 project views or 14 days, whichever comes first, no card.