Off-Season Scheduling, Expanded Scout Capabilities, & Precision Mapping

New features

• Catalog / Jobs — Your org can save off-seasons (named date ranges). In Catalog → Off seasons you add and edit them; on a job’s recurring series you pick one with the same search-and-chip pattern as discounts, or tap + to create a new window. Once an off-season exists, you can attach it to a schedule; recurring visit generation skips those dates, and edits to the dates apply the next time visits are expanded.

Improvements

• Scout / CRM — When you ask about service areas on a property, Scout’s CRM lookups now include path length and land area (human-readable labels plus numeric meters), aligned with what you see on the property map for open paths and closed shapes.
• CRM / properties — For a closed service area, Add points still works: tap near an edge to insert a new corner in the right place on the outline (not at the end). Taps too far from the shape are ignored, with a short hint.
• CRM / properties — On the service areas map, drawing tools use a crosshair (panning still uses a grab cursor), you can zoom in closer on satellite imagery, and the map stays put when you tap points or the path— it only moves when you pan, zoom, switch areas, or use Recenter.
• Scout — A small Send to support link under the mic and send buttons uses the same ticket flow as errors (chat link and a short transcript). You confirm before anything is sent.
• Scout — In the message box, Enter starts a new line (same as Shift+Enter). Messages send only when you tap Send.
• Tasks — You can set an optional time with the date (shown as Date and time), stored in the organization time zone. Scout is steered to create these for reminders and follow-ups instead of treating them like schedule visits.
• Scout — You can manage catalog off-seasons (create, rename or adjust dates, deactivate when unused) and attach or clear a catalog pause on a recurring job’s series from chat, including checking how many recurrence patterns still reference an off-season before removing it.
• Scout — You can add and update catalog items, create custom catalog categories, and remove or rename those custom categories (by listing categories with search, then running the delete or update action—no need to paste UUIDs when one row clearly matches) when your role allows those finance actions, including after a short “yes” or “create them” when you already pulled the catalog list in the same conversation. Run cards show which catalog row you are editing (not a bare “item id”), and Scout does not ask for a default margin on those rows—that stays in the estimate/invoice line flows in the app.

• Scout — Pending Run cards for catalog category and item actions show the readable name (or path) for the row you are deleting or editing, not a long UUID in the form.

• Scout — When a proposed task includes an assignee, the Run card shows their name and a dropdown so you can change or clear the assignee before running. Creating a task from Scout without an assignee still assigns it to you when you run it, so personal reminders show up with you as assignee.

• Scout — Booking jobs on the calendar stays date-first (no back-and-forth about morning/afternoon or visit clock times unless you clearly want a timed visit). New customers from a name like “Ryan Z” fill in first/last name correctly; optional property on a job no longer shows as the word “null” on Run cards when left blank.
• Scout — Follow-up messages can rely on what already happened in the chat: each assistant reply’s data lookups and completed Run results are summarized for Scout so it does not redo CRM creates or ignore a customer you just added.

Bug fixes

• CRM import — Download skipped rows (CSV) no longer fails with Access denied for members whose role can import customers; the action is now included in the same permissions as the rest of the import wizard.
• Members / roles — The Crew Member role again opens only My Day and Time (your own clock entries) by default. New organizations no longer grant extra org tabs such as Usage or Automations until an admin adds those permissions in Manage Roles. Existing crew roles are cleaned up when your site’s database update runs.
• Jobs / recurring — In the off-season search list, each row has an options control (same “knobs” style as elsewhere). Open it for Edit (catalog modal) or Delete (confirms; if this job still uses it, the schedule is cleared first, then the catalog entry is deactivated). Saving an edit to an off-season on the current schedule auto-updates the recurring series on the server so dates stay in sync.
• Jobs / recurring — Save schedule in the job workspace saves pattern-only changes when visit counts do not change. Single-letter search matches names; empty search states are accurate. The picker hides the off-season already on the schedule; the chip uses Remove.
• Jobs / Scout — Creating a job right after adding a customer (especially when copying a default catalog discount onto the job) no longer crashes with a meaningless “0” error. That came from using numeric row indexes on RealDictRow results (PostgreSQL treats row[0] as a column named 0, which raises KeyError(0)). Row reads now use column names everywhere in that path.
• Tasks — Opening a task with a long description no longer hides the Post comment button; the task detail panel scrolls so comments and Post stay reachable.
• Scout — Run cards (e.g. create a task) show up again when the assistant asks for data and proposes an action in the same reply.