Custom Email Templates, Multi-Day Routing, and Enhanced Performance Scaling

New features

• Organization — Email templates: Admins can open Email templates under Organization and customize the HTML (and optionally the subject line) for the emails your customers and team get—quotes sent, invoices, receipts, withdrawn notices, team invites, form invites, manual messages from Communications, and workflow alerts. Use the built-in placeholders for your company name, links, and large sections like line items; Preview shows sample data, Save applies your version, and Reset brings back the default wording and layout.
• Jobs — multi-day visits: In the job workspace Schedule & visits section, when you add a recurring series you can choose Multi-day (date range): set start and end dates and which weekdays to include (Monday–Friday on by default; Saturday and Sunday optional). The app creates a visit for every matching day in that span. If you change the dates or weekdays later, open visits follow the new plan; completed and skipped visits are left as-is. If an open visit you would remove still has an invoice, the app asks you to handle that first.
• Estimates & invoices — Activity: After you send an estimate or invoice email, you can see a simple timeline of what happened next—each send, when the customer’s mail app loaded images (best-effort “opened”), when they opened the proposal or pay page, and when they accepted, declined, or paid. Times use your device’s time zone (the browser you’re in). Notes on estimates and client notes on invoices moved below your line totals so totals stay up top.
• Estimates — notes: Each customer quote has Internal, Client, and Crew note areas (same place as Activity—under your line totals). Client notes support simple Markdown (bold, lists, etc.) and appear on the customer proposal page, in send/resend email, PDF export, and on invoices you create from that estimate. Internal and crew notes stay in your org only.
• Organization settings: Admins can set default client notes for new estimates (same Markdown)—handy for standard terms or a short welcome blurb you still edit per quote.
• Invoices — client notes: Draft and sent invoices have a client notes field (Markdown). Customers see them in invoice email, PDF, and the preview your team opens before sending.
• Saved routes (replaces “route templates” in the app): the sidebar tab is now Saved routes. Each saved route has an On the calendar section—Upcoming by default, plus Past and All—so you can see when that pattern runs, add a one-time schedule route on a date, or add recurring routes the same way as recurring job visits. The schedule can open a specific week with a link that includes the date.
• Schedule — recurring routes: When you add a route from a saved route, you can set how often it repeats (similar to recurring job visits) and save a recurring route so upcoming weeks fill in automatically. The app can gather visits that fit the pattern onto each new route row; completed visits stay where they are. Open route options (sliders) on a row that belongs to a series to edit the pattern or detach that day’s route from the series.

Improvements

• Scout — Schedule routes: Ask Scout about drive times and distances between stops on a route (it uses your route start / shop like the map). Scout can propose Run actions to change stop order or optimize for driving time (same idea as Optimize route on the route map). It also calls out stops that don’t have a usable address for driving directions.
• Scout — Run on schedule steps: If placing a job on the calendar from a Scout action fails, the app now shows the real reason when it is safe to share (same guidance as the Schedule tab), and edited fields are merged with the saved action so a partial edit does not drop other values. Run on an action that already finished or failed explains that you need a new step or the Schedule tab instead of a generic error.
• Scout: When you open a job from Scout’s quick details, you get an Open job workspace button to jump straight to that job’s full workspace. Calendar-style answers also drop stray visit row IDs so the thread stays readable. When describing a customer’s email or phone for billing, Scout shows the contact details—not raw contact IDs before the address or number.
• Scout — CRM: When you ask who was added most recently, Scout uses the list ordered by when each customer was added, not alphabetically by name—and it finishes after that fetch instead of looping the same request until “too many fetch rounds.”
• Organization — Usage, Team, Finance, Insights: Long communication histories and activity logs load in pages as you scroll (with search on the communication log where it helps). Finance → Agreed price vs. job costs supports search and keeps loading more rows the same way. Insights tag filters load all of your CRM tags, not just the first page.
• Support (your account): The Support page loads your tickets in pages (with search on title and messages), and each conversation loads more messages as you scroll—same limits the app and Scout rely on so long threads stay fast.
• Forms: The main forms list shows how many responses each form has, and the Responses page can search by submitter name or email (same paging rules as other org lists: 25 per load, up to 50 per request).
• Members: Search by name or email, filter by role and status, and the roster loads in pages (with more as you scroll) so large teams stay quick to open.
• Invoices: The Invoices and Recurring tabs load 25 rows at a time (up to 50 per request) and load more as you scroll, with a total count on the server so long lists stay fast. Invoice Activity in the workspace loads in pages; use Load more activity when there is more to show.
• Estimates: The quotes list and incoming requests list load in pages of 25 (the server caps a single request at 50), with more rows loading as you scroll—so large orgs stay responsive the same way as other long lists in the app.
• Jobs: The job list and Scout use the same paged job, visit, expense, and invoice lists (25 per request, up to 50), with load more as you scroll on the job list and in the Expenses and Invoice modals. The job workspace loads all visit pages in the background so scheduling and bulk actions stay complete. After you mark an invoice paid, send it, change the amount, or delete it from the workspace, the job’s costs & profit snapshot and billing summary update right away (no refresh needed).
• CRM: Customer search matches email, phone numbers, and property names and addresses—not just names. The customer list loads in pages of 25 and keeps loading as you scroll; an empty search shows No results for your search. Tag pickers load tags in pages so large orgs stay responsive. Each customer shows when they were added in your device’s time zone (list and detail).
• Communications: The page no longer shows the expandable Texting costs & Twilio note under the title. The Text messages column always shows a frosted Coming soon overlay (TheYardOS is still waiting on approval to send texts) until that’s removed in a future release; Send text stays off in this tab for now. Message history loads in pages—scroll down in the email or text column to load older messages (newest stay at the top of the email list).
• Org dashboard — sidebar: The left-hand module list is reordered for a clearer day-to-day flow—Scout is at the top, Schedule sits next to Saved routes, Estimates, Invoices, and Catalog are grouped together, and Forms sits near the bottom (just above Support).
• Phones & tablets: Dragging visits on the Schedule, reordering estimate lines and choice sets, reordering stops on the route map, and reordering roles under Members now use the same pointer-based drag as desktop—no more relying on touch-inconsistent HTML5 drag-and-drop.
• CRM — Import customers (CSV): The review step flags rows that share the same email and/or the same name in your file (only rows without a merge key are linked that way), and flags any row—including a merge-key first row—that matches someone already in your CRM by email or name. Each row has an Import / Skip toggle, plus Approve all duplicates or Suggested skips. Merge-key matches note that skipping may orphan follow-on rows in the file.
• Estimates & invoices — Activity: Timeline times show in readable form in your device’s time zone (not a long UTC ISO string). The note under Activity explains that “email opened” only appears after the customer’s mail app loads images (Gmail and others often hide them until the recipient chooses to show them).
• Estimates — PDF export: The header is tighter (logo lines up with your company name and ESTIMATE without a big empty gap), and Created shows when the quote was first saved in your organization’s time zone (not a raw UTC calendar day).
• Estimates — notes: Under Notes, use Internal, Client, and Crew tabs to focus one note at a time. Each tab has a Preview of how Markdown renders (including internal and crew notes for your team), and it updates as you type (saving still happens on the same auto-save timing as before). The note toolbar stays compact (no extra help line). Invoices client notes and organization default client notes use the same live preview.
• CRM (phones): The customer list scrolls inside a fixed-height area so it does not push the detail panel miles down the page. When you tap a customer, the view scrolls to the detail so you land on their profile right away.
• Org dashboard — What’s new: Small red badges on Estimates, Jobs, and CRM show how many new estimate requests, jobs, or customers you have not seen in the list yet. Open the list once: new rows are highlighted, then they clear from the badge count for you (each person tracks their own).
• Estimates — Adjust panel: The line Adjust drawer stays open when you click or drag outside it; close it with Save line, Cancel, or the Adjust (sliders) button again—same idea on invoice line Adjust (only one drawer open at a time; click Adjust again to close).
• Estimates / job costs — packages: Edit package lines only appears for real package rows (nested bundle), not for normal lines where the UI could pick up a stale row attribute.
• Estimates — Adjust inside packages: The line retail field in the line panel now matches the Line retail pill (it includes the same parent-package quantity roll-up as line cost and quantity).
• Line list (estimates & job costs): Each line shows unit amount and quantity without a “×” between them, since custom formulas can replace quantity × unit cost.
• Custom line formula (estimates, job costs, invoices): Only the switch turns it on or off (the label no longer covers the whole title). Use {{ quantity }} and {{ unit_cost }} (unit price in dollars). The formula is dollar math; the app turns the result into the line’s cents for you—no extra “× 100” at the end. How it works was updated to match. Clearing the option goes back to the default math.
• Estimates — packages: When you open Edit package lines, each row’s quantity, line cost, and line retail reflect how many times the package appears on the parent (and further up if packages nest): stored quantities stay the same; the workspace shows the effective numbers used for the parent line’s bundle cost and retail. Quantities on the line read like 6 (3 × 2) (effective total, then parent package × line qty). The footer totals inside that editor use the same scaling so internal cost, retail, margin, and customer total match what rolls up to the parent. You can set a custom gross margin (or line retail) on individual lines inside the package—Use estimate default pricing still follows the package header—and parent package or quote totals use those numbers when they roll up. Changing quantity on a package line and saving updates the line; nested rows still get unit cost and retail from the package, and quantity is yours for bundle configuration.
• Saved routes: The pattern list searches by name and loads more as you scroll; On the calendar and Recurring series also load in pages when there are many rows.
• Schedule: Visits for a day that are not on any route strip show on a Not on a route row when there are any (empty days no longer show that row). Use All routes or Recurring series in the toolbar: recurring strips show a Recurring badge; in Recurring-only view, one-time strips hide and their visits collect under Other routes (hidden) when needed. Dragging those visits onto a route saves stop order correctly. When the last visit leaves a route strip (moved, taken off routes for the day, or deleted), the empty strip is removed automatically—no extra prompt. Dragging work onto a day that had no route yet adds the new route row immediately so visits don’t vanish from the grid until refresh.
• Schedule — Jobs to schedule: The drawer list loads in pages as you scroll, and Search / priority run on the server so large pools stay fast. Empty search with no matches shows No results for your search.