Pip: If you have ever wished your field service software could do approximately thirty-seven more things simultaneously, ServiceWorks Academy has been busy.
Mara: This episode covers the October 14th, 2026 product enhancement document — a wide-ranging release touching scheduling, inventory, purchasing, integrations, and the mobile app.
Pip: Let's start with what's actually in the release.
October 14th, 2026: What Got Built and Why
Mara: The release covers improvements across the web platform, the mobile app, and third-party integrations — all aimed at reducing the friction technicians and dispatchers hit in daily workflows.
Pip: The scheduling changes are a good place to anchor that, because the document is direct about the stakes: "Changing the schedule date or technician after a trip has started can remove the job from the technician's route and may cause the job to be overlooked."
Mara: So the fix is a warning popup that fires when someone tries to reschedule a trip already marked En Route — the job stays on the route, and the warning steers the user toward creating a new schedule instead.
Pip: A guardrail, basically. The kind of thing that only gets built after someone learns the hard way.
Mara: Alongside that, technician job counts now appear next to each technician's name across the Staff View, Calendar View, fourth board, and Create Job page — updating in real time as jobs are assigned, moved, or reassigned, without a page refresh.
Mara: The inventory side gets a similarly practical addition: a Save and Add New Inventory button that saves the current item and immediately opens a blank form for the next one, clearing all fields automatically and preventing duplicates if the button is clicked more than once.
Pip: For shops entering a lot of parts at once, that one turn removes a genuinely tedious loop.
Mara: The Markup Calculator lands in the same practical territory — added directly to line items so users can enter a markup value, see the resulting selling price, and apply it without leaving the item section. Changing the cost or price automatically recalculates the markup percentage.
Mara: On the purchasing side, a clickable job number now appears in the Receive PO grid when a PO is tied to exactly one job, opening that job in a new tab while keeping the PO view open. The document also details Purchase Order cancellation status visibility, Final Disposition tracking for returned parts with automatic line-item separation for partial returns, and Reliable Core Part handling that automatically adds or swaps the correct core suffix when the distributor changes between Marcone and Reliable.
Pip: The integrations section is where the release gets genuinely dense.
Mara: The NSA Availability Process is the most involved piece — it sends technician availability and capacity to the NSA portal on a daily 7:30 AM UTC scheduler run, organized by technician, zone, ZIP code, service class, and time range. The upshot is that what ServiceWorks knows about technician capacity is what the NSA portal reflects, automatically.
Mara: The LG integration now supports order creation from both web and mobile, and purchase orders submitted through ServiceWorks are automatically flagged as urgent, which defaults them to FedEx Air shipping to match how orders placed directly in the LG portal behave. The ORHP email interception enhancement prevents duplicate jobs by checking an incoming dispatch number against existing records before creating anything new.
Mara: The mobile app additions run parallel to the web changes: Schedule Board task management with drag-and-drop, the same En Route warning logic, Part Triage with Service Panda integration, a Will Call and Pickup option under Shipping Strategy during PO creation, Bulk Part Pickup so technicians can confirm multiple parts across different jobs in one action, a Manual Data Sync shortcut accessible from any screen, and improved Brand and Product Family search that correctly returns short names like GE and LG without irrelevant results.
Pip: The Customer A/R and Statements update is worth a specific call-out — statements now calculate only from completed jobs, so open or unfinished work no longer inflates a customer's balance.
Mara: Right, and the API endpoint for warranty claim payments extends that accuracy to integrations — full and partial payments can be submitted, tracked, and reconciled against specific warranty claims, with the customer payment field left unchanged and validation blocking unauthorized requests.
Mara: Rounding out the release: Call Source and Call Type filters on the All Jobs page, a Job Type filter on the Invoice page, notes added to the Claim Processor screen that surface as banners on the associated job, an Assigned To column in the Task grid, four new customer last-name legends for templates and emails, History section updates that default to the Open Jobs tab and correctly display today's cancelled jobs, and Part Triage item matching that auto-populates available details when no inventory match is found.
Pip: That last one matters — instead of a dead end, the technician gets a form with what's already known and a prompt for what's missing.
Mara: Taken together, the throughline here is reducing the gap between what the system knows and what the person using it can act on — in scheduling, in inventory, in payments, in the field.
Pip: More of that next time, presumably. The software is not slowing down.
