Service Workspace & Catalog Discounts Update

New features

• CRM — customer title: You can set an optional courtesy title (Mr., Mrs., Ms., Dr., and similar) on residential customers, or leave it as Not specified. CSV import can include a title column; common column names are recognized, and odd values are skipped so the rest of the import still works.

• Catalog discounts: Create reusable percent or fixed discounts under Catalog → Discounts, apply them on estimates and invoices, and see them on customer-facing quotes, estimate PDFs, and invoice PDFs (subtotal, discount line, total). Discounts flow through accepted work into jobs and invoices where pricing is connected.

• Visit workspace: Each scheduled visit has its own page for status, crew, line items, and invoices (including what’s outstanding, profit so far, and actions like send or mark paid), with easy links back to the job and Schedule. Open it from Schedule or from upcoming visits on the job. Map pins for visits line up with the property address the same way as on Schedule.

Improvements

• CRM — discount: Customer discount uses the same picker pattern as elsewhere (search, selected discount, clear, add new).

• Catalog discounts: The add/edit discount screen is clearer (percent vs fixed, only the fields you need, better spacing on phones). Selected discounts on default pricing show as compact cards. Invoice totals and customer invoice preview show subtotal, discount name and amount, and total due in a consistent way. From pickers, New saves and applies the discount right away; each row can be removed with a short warning if it’s in use.

• Default line pricing: Save is the main action when pricing or discounts change (replacing a separate “apply default pricing” step); changes save when you’re done editing. Discount rows stay out of the way when there’s nothing to show.

• Scout — jobs: Suggested create/edit job flows match the real job form: waitlist, one-time, and recurring. Schedule details read in plain language (service date, visit range, recurring options) instead of raw technical data.

• Job workspace — Schedule: Saving or changing schedule type goes through one Review schedule changes step (what will happen to visits) instead of multiple pop-ups. Recurring changes show what will be added or removed before you apply.

• Jobs list: Status reflects visits across the app, not separate status tabs on the list. Bulk actions focus on priority, crew, and rescheduling visits. Upcoming visits on a job are tappable cards with date, status, title when set, crew, and invoice count, plus a link to Schedule when there are more visits than fit on the card.

• Invoices — line items: Draft and sent invoice lines align with job-style cost and retail, unit cost and quantity, optional custom line formulas, and default pricing with gross margin in Adjust. Adding lines uses unit cost so retail follows your margin settings.

• Line items — margin: Jobs and visits support default gross margin or markup (like estimates) and optional per-line margin in Adjust. List rows show cost and retail together, with a clear tag when a line uses its own margin. Visit invoices built from templates carry over margin and cost settings when applicable.

• Job workspace layout: Billing lines and job costs are combined into one Line items area (catalog, packages, cost/retail, include on invoice). Costs and profit sit with billing and customer payments (outstanding, profit to date, create invoice). The old separate “finance & records” block is gone; service location map and areas stay when a property is set.

• Creating and editing jobs: You choose waitlist, one-time, or recurring up front; visits and patterns save with Create job / Save changes without a separate “create series” step. Multi-day jobs switch cleanly between a single service date and a start/end range. Crew and budgeted hours for visits live under the schedule section with a tighter layout. Fewer redundant confirmation dialogs when changing schedule type.

• Copy: Long explanatory paragraphs were removed from add/edit job and related screens so labels and controls carry the story.

• Leaving jobs and visits: Back waits for in-flight saves to finish so “unsaved changes” prompts match what you actually chose. Visit save prompts stack buttons clearly; background saves use the same small status chip as the job workspace.

Bug fixes

• CRM: After Save changes on customer details, that section stays open instead of collapsing.

• Jobs: Saving the workspace (including when a catalog discount is applied) shows a clear error message when something fails instead of a vague technical message.

• Invoices: Creating a draft invoice for a customer-only job works again, with readable errors if save fails.

• Default line pricing — discounts: The catalog discount picker shows and saves correctly on jobs, visits, and the Invoices tab when default line pricing is in use.

• Job and visit line items: Line retail again shows the customer price instead of matching internal line cost. Invoice line Adjust no longer shows an extra redundant unit price field when using a custom line amount formula.

• Scout — schedules: Weekdays and single-day vs multi-day schedules are interpreted correctly when the assistant suggests job schedules. Customer search in the assistant focuses on name, company, and contact details.

• Estimates, jobs, and pickers: Text and line items save when you finish editing or leave a field—not on short pauses while typing. Catalog and package pickers stay visible under the nav and don’t close when you pick a line. Line category suggestions appear reliably above nearby content.

• Visit workspace: Back always offers save or discard when you have unsaved changes; failed saves restore buttons and labels; catalog and custom lines save correctly for visit-only work.

• Schedule changes: Switching to one-time, recurring, or waitlist previews impact on visits first, updates invoices when visits change, and avoids leaving stray visits or confusing states when you change types or crews.

• Autosave and schedule: Background save no longer overwrites schedule work in progress; schedule changes only apply when you use the dedicated save/move actions. Creating a job is smoother (no stray “leave site?” warnings, line items included on create), and multi-day vs single-day fields show correctly on new jobs.