Advanced Route Mapping, CRM Imports, and Recurring Visit Management

New features

• Jobs: Recurring visit series are separate from one-off visits. Create a series with a repeat pattern (weekly or monthly), choose an end date, a fixed number of visits, or keep it ongoing. Visits from a series stay linked so you can filter them, see them in a From column, pause or edit the whole series (future visits are rebuilt from your changes), or delete the series and all its visits when nothing blocks removal. The app keeps up to 100 upcoming visits per series and adds more in the background when you’re running low. One-time visits stay independent—add them with a single date.
• CRM: Import customers from a CSV file—upload your export, match columns to names, phones, emails, billing and service addresses, and tags, then review and bring them into your directory. Optional merge key column to put several rows onto one customer (for example, multiple service addresses).
• Schedule route map: Each named route on a day has a Map button that opens a full-page map of that route’s stops in order (numbered pins and a path between them). The first row is your route start (organization default, template, or a location you save for that route) with address search; it stays first in the list and is not a customer visit. The app uses saved property coordinates when it has them, and tries to look up missing ones. Stops that still can’t be placed are called out as errors in the list so you can fix the address in CRM. Back returns you to the schedule.
• Route templates: Save reusable stop patterns tied to CRM properties or customers (shown under Route templates next to Schedule). When you Add route on the schedule, you can start from a template or create a blank route; strips linked to a template show a tag with the template name. New visits that match the template prefer the right route for that day, and stops can reorder to match the template until you drag them yourself.

Improvements

• Plans: Monthly property geocoding (saved addresses) and driving calculations (route map / drive times between stops) now have clear limits by plan, the same way Scout chats, emails, and texts do. If you hit a cap, the app explains what happened and you can upgrade when it makes sense for your team.
• Team: Organizations on an active paid plan (or with included access) can invite as many members as you need—there is no longer a small per-plan cap that blocked larger crews on higher tiers.
• Jobs · Schedule & visits: The three views are Recurring (manage series—the parents that generate visits), One-time (visits with no series, plus add a single visit), and Visits (every visit on the job). Editing a series still updates its visits; you can still tweak an individual visit on the Visits tab.
• CRM import: The import page links to a sample customer CSV you can open in Excel and try end-to-end. After Check import, open Preview every row to search all mapped customers before you commit.
• Organization settings: Set your default route start (shop or yard) with street, city, state, and ZIP plus the same street search suggestions as CRM; the app pins the location when you save settings. That address is the usual first stop on the route map; you can still override or reset to the org default on each route.
• Schedule route map: Between stops that have driving calculations (when Mapbox is configured), the sidebar shows estimated drive time (rounded to the nearest minute; hours + minutes when an hour or longer) and distance (miles, one decimal) from the cached route between consecutive pinned stops.
• Route templates: Each template can store its own route start (or follow the organization default). Creating a template from a schedule route copies that route’s effective start onto the template.
• Schedule: Optimize route (on the route map and under Route options) now targets round-trip time: route start → visits → back to the start, not a one-way run. With no completed stops, it uses a stronger pass (2-opt) on top of a nearest-neighbor start; completed stops stay fixed and the tool does not assume you’re driving home before stops still listed after the last open visit.
• Schedule route map: The map stays under the main site navigation when you scroll. Drag stops in the sidebar to change order (saved the same way as the schedule grid). Jobs without a service property no longer use the billing address on the map — they stay off the map until you set one; Set address opens a modal to search and pick from that customer’s saved properties (or use Add new property in CRM). Completed visits stay in the list but can’t be dragged.
• Schedule: The route map control is a map-pin icon under the route options (sliders) button on each strip.
• Schedule route map: When two or more stops share the same map point, they show as one wider pin (for example 1, 2) instead of stacked circles; open the pin to see each stop’s details.
• Schedule: In Route options, you can link a route template to an existing route (search, or None / Remove template), then Save to reorder stops to match the template (stops that don’t match any template row stay at the end). You can also create a new template from the current stops (customer + property when the job has one), in stop order—and that route is linked to the new template automatically with stops reordered like when you link one manually.
• Route templates: You can’t save a template with the same name as another (ignoring letter case). If the name matches, you’re asked whether to replace the existing template—replacing removes the old one, keeps schedule strips on the updated definition, and applies your new stops. The same prompt appears when you create a template from the schedule and pick a duplicate name.
• Route templates: For stops set to any job for customer, the Property field stays visible but is greyed out and disabled so it’s clear the stop isn’t tied to one address.
• Schedule: The template tag on a route strip sits above the route name so it doesn’t crowd the title.
• Schedule: Routes on each day are saved for your team (not just this browser). Each route has a name (default “Route”), its own stop order, and a sliders button to rename it, move the whole route to another day, or delete it when it has no stops. Add route creates another strip (optionally from a route template). After you move the last stop off a route, you can keep the empty route or delete it.

Bug fixes

• Jobs · Recurring visits: When the pattern’s first day (for example next Tuesday after your “starts” date) is already a few days in the past at save time, the app still creates that first visit on that day instead of skipping straight to the following week.
• Schedule: Dragging a job from Jobs to schedule onto the week grid no longer flashes the card at the bottom of the strip before it jumps to the right stop position (template-linked routes refresh once with full data; other routes update strip order in the DOM immediately before saving).
• Schedule: Moving a visit off a template-linked route and dropping it back on (or moving it from another route onto that strip) respects template stop order again instead of sticking the visit in the middle. Reordering stops that are already on that route still behaves as before.
• Scout chat no longer fails with a generic error when the assistant proposes actions in a slightly malformed JSON array (e.g. extra non-object entries).