Tech Scheduling & Routing

Two related-but-independent admin tools live under this banner, each helping explain a different kind of automatic routing in SecurityTrax:

• Tech Schedule Assignment Runs — an audit log of every auto-scheduler run. Use it to debug "why did this appointment get assigned to this tech?" questions.
• Zip Relation Manager — the zip-code-to-location mapping that drives default location assignments for new leads and customers.

Each reaches from a different card on the Admin index. They're collected here because they share the "configure the auto-router" theme, but their mechanics are distinct.

Tech Schedule Assignment Runs

Requires. Tech Scheduler with View, plus slot scheduling enabled with appointments left unassigned (auto-assign-on-create turned off).

Route: admin.tech-schedule-assignment-runs.index.

A log of every time the tech auto-scheduler fired — a cron job that looks at unassigned work and picks techs for it based on the active Scheduling Profile.

When it's hidden. This tool only assigns unassigned slot appointments, so it's hidden unless your company both uses slot scheduling and leaves appointments unassigned on create. When auto-assign-on-create is on, every appointment already has a tech the moment it's booked — there are no runs to review, so the card and route are removed.

Each row:

Use this page when someone asks "why did X get assigned job Y?" or "why didn't Y get a job when she was free?". Open the relevant run, expand details, and read the scheduler's reasoning.

Zip Relation Manager

Requires. Administration Page.

Route: admin.zip-relation-manager.index.

A spreadsheet-style tool for mapping postal codes → locations → routing defaults. When a new lead or customer arrives with an address, SecurityTrax uses this mapping to pre-fill their default location (and, sometimes, sales rep or work-order territory).

The page

The layout is close to a spreadsheet — one row per zip code, with columns for the assigned location, any territory tags, and other routing defaults. You can:

• Paste bulk data — copy from Excel and paste into the grid.
• Upload a CSV for bulk import.
• Edit individual rows inline.
• Highlight unmapped zips — zips that exist in customer addresses but don't have a mapping row yet.

Step-by-step: importing zip mappings from a spreadsheet

1. In Excel, prepare a sheet with one row per zip code. Columns: Zip, Location, optional Territory, optional Notes.
2. Copy the entire range (including headers).
3. In the Zip Relation Manager, click Paste and paste into the import dialog.
4. SecurityTrax parses, validates, and shows a preview. Fix any errors (invalid zips, unknown locations) and re-submit.
5. Confirm the import. New rows are added; existing rows are updated where the Zip key matches.

Finding unmapped zips

The page has a Show unmapped zips filter that surfaces zips present in customer addresses but missing from the mapping table. Work through the list to make sure every zip you actually have customers in is mapped.

Non-obvious behaviors

• Tech scheduler vs. lead routing. These are two separate systems. The tech scheduler runs periodic cron jobs; lead routing happens when leads are created or assigned. Failures and configurations are unrelated.
• Multiple groups matching. If a lead matches several lead queue groups, priority decides which one routes first. Non-priority groups may or may not also assign, depending on company config.
• Zip mapping is fallback, not override. If a lead's location is explicitly set by another mechanism (e.g. a source integration), the zip mapping doesn't override. It's a default-when-no-other-signal.

Related

• Scheduling Profiles — what the tech scheduler consults to decide how to assign.
• Locations — the destinations that zip mappings point at.
• Leads — where routed leads ultimately land.
• Calendar — the visible outcome of tech-scheduler assignments.