What’s New on the Platform — August 2–24, 2026

Rollout note: These improvements are being released in stages. Availability may vary by workspace while each change completes final validation.

Over the last three weeks, we focused on one simple but important goal: everything Exoserva promises you and your customers should match what actually happens.

An appointment time should be genuinely available. A price should come from your price book. Rescheduling should update the calendar, not just the message. And an incoming request should never disappear just because an AI service is temporarily unavailable.

The result is more accurate online booking, a more reliable AI assistant, faster lead-to-job workflows, and clearer scheduling, invoicing, and time tracking.

Here’s the rundown.

:rocket: The Big Stuff

  1. Online booking understands your real schedule more accurately.
    Exoserva accounts for booked time, working hours, breaks, time zones, travel time, and buffers between jobs. Customers are offered times that can actually be booked.

  2. The AI assistant follows through on the action.
    When a customer asks to reschedule, change an address, or cancel an appointment, the assistant checks your rules and updates the actual job. When a person needs to step in, it hands the request to your team with the right priority.

  3. Incoming messages and leads are much harder to lose.
    A message is saved before AI processing begins. If an external AI service is temporarily unavailable, the request stays in Inbox for your team instead of disappearing.

  4. The path from conversation to job is shorter.
    A qualified lead can become a job directly from Inbox. Exoserva carries over the customer and conversation context, opens the job you just created, and avoids unnecessary duplicates.

  5. Dispatch is more precise.
    Technician assignment can account for availability, distance, and skills. Arrival at the property is recorded separately from the start of work, giving you a more honest schedule and timesheet.

  6. Prices, taxes, and totals stay more consistent.
    We strengthened the shared calculation rules between the price book, jobs, estimates, and invoices so the same service does not drift to a different amount in another part of the platform.

:date: Online Booking & Scheduling

Online booking is becoming more accurate in the situations contractors deal with every day.

  • A booked job blocks the time even when a technician has not been assigned yet.
  • A time offered to a customer keeps its exact date, time, and time zone.
  • Confirmation dates no longer shift by a day for businesses west of UTC.
  • Working hours, breaks, and technician-specific time blocks are taken into account.
  • You can set buffers before and after a job.
  • The platform distinguishes between an exact requested time and an approximate preference.
  • You can promise an arrival window instead of pretending the technician will arrive at an exact minute.
  • Addresses are checked against map data instead of being guessed from the city name alone.
  • Multi-day work displays more accurately on the schedule.
  • Times are presented in your company’s time zone, not the server’s.

We also continued improving the public booking form. Customers can choose a service option, upload a photo of the issue, and give your team more useful information before the first call.

If a booking link is invalid or the business cannot be found, the customer will see a clear not-found state instead of an empty or broken booking form.

:robot: An AI Assistant That Makes Fewer Promises and Completes More Actions

The biggest AI improvement is that the assistant relies more heavily on your company’s real data.

  • Service prices come from your price book instead of being improvised.
  • Before promising a visit, the assistant checks your service area.
  • Questions about licensing and insurance are handled using your company’s information.
  • Emergency and urgent requests are escalated to a person with the correct priority.
  • Rescheduling changes the actual calendar entry.
  • An address change triggers a new service-area check.
  • The assistant respects the time, price, duration, and buffer selected by the customer.
  • A qualified lead keeps its context when it becomes a job.
  • Replies are checked before they go out so customers do not receive technical, incomplete, or contradictory messages.

When an automated reply cannot be completed safely, Exoserva preserves the request for your team instead of silently losing it.

:speech_balloon: Inbox & Customer Communication

We removed several situations that could make a conversation confusing for the office.

  • Inbox shows the team member who actually replied.
  • An incoming message is saved before AI processing begins.
  • Replies stay attached to the correct customer and business number.
  • Deleted staff contacts are no longer used to resolve new SMS messages.
  • Important notifications are not buried under dozens of duplicate events.
  • Urgent messages appear as urgent instead of ordinary information.
  • A Create Job draft survives if you close the panel and return later.
  • After creating a job from Inbox, you land on the job you just created.
  • One conversation cannot accidentally change another customer’s information.
  • Internal AI observation processes no longer speak inside the customer thread.

We also improved handling for leads arriving from external sources, including Yelp and Thumbtack, so your team can work with them more like ordinary customer conversations.

:toolbox: Jobs & Field Work

The path from assignment to completion is clearer for both the office and the technician.

  • A technician can be assigned automatically after online booking.
  • Assignment can consider availability, distance, and required skills.
  • Technicians have clearer actions for heading out, arriving, starting, and completing work.
  • Arrival and the start of work are recorded as separate events.
  • The customer receives the arrival notification at the right moment.
  • Busy means the technician is occupied now, not that they had a job sometime in the past.
  • A cancelled job can close correctly even if no technician was ever assigned.
  • Job line items use one shared structure across related documents.
  • Editing a customer or job preserves fields that were not changed.
  • Headline counts more accurately describe the records shown beneath them.

This reduces the number of manual corrections between the schedule, job, estimate, and invoice.

:dollar_banknote: Price Book, Estimates & Invoices

We continued strengthening the shared rules behind pricing.

Price Book

  • Money values are stored and handled in one consistent format.
  • Each price has a defined unit.
  • Clearly invalid values are refused instead of quietly reaching a customer.
  • Price changes are recorded in the audit history.
  • The “book as” setting is saved and used by online booking.
  • Public booking receives only the safe pricing information it needs.

Estimates, Invoices & Payments

  • Currency and tax presentation is more consistent.
  • The displayed tax rate must agree with the calculated tax.
  • Payment deadlines are clearer for the customer.
  • An invoice created after job completion appears in the list immediately instead of waiting for cache refresh.
  • After a successful subscription payment, the new company plan appears without delay.
  • Partial payments and related totals are handled more accurately.
  • Businesses can roll out an option for customers to leave a tip on the payment page.

Our goal is for every job to have one understandable financial story from the price book through final payment.

:busts_in_silhouette: Team, Time Tracking & Payroll

We reworked several parts of time and wage handling.

  • Time entries keep their state after the page refreshes.
  • Shift duration and pay calculations use consistent rounding.
  • Invalid or incomplete entries are less likely to slip silently into payroll totals.
  • Employee working hours can be respected during scheduling.
  • Availability, timesheets, and related team settings are easier to understand together.
  • Managers get a clearer view of where recorded hours and calculated amounts came from.

These improvements are especially useful for businesses using Exoserva not only for dispatch, but also for daily field-team oversight.

:mobile_phone: Interface & Mobile Work

We continued bringing the main workflows into one consistent interface.

  • Navigation is more consistent across sections.
  • Tables adapt better to smaller screens.
  • Panels and forms are easier to use on a phone.
  • Drafts survive an accidental panel close.
  • Dashboard, Jobs, and Inbox counts better match the data beneath them.
  • Tapping a notification opens the relevant screen.
  • Long lists and operational pages are easier to scan during the workday.
  • Fields, buttons, and actions use more consistent language and states.
  • Errors appear closer to the place where the user needs to take action.

:bell: Notifications

Notifications are becoming less noisy and more useful.

  • Repeated events can be grouped instead of filling the entire list.
  • Urgency is displayed correctly.
  • An assigned technician receives a job notification.
  • New customer messages stay visible to the owner and operator.
  • Dispatch and notification settings keep the state selected by the owner.
  • The notification stream can recover without forcing a full page reload.

:sparkles: Stability & Security

A large part of this period’s work happened in places users should not have to notice.

  • An interrupted request no longer keeps a database connection forever.
  • Concurrent AI conversations use platform resources more safely.
  • Fresh databases complete required setup more reliably.
  • A database outage is no longer presented to the user as “wrong password.”
  • An inbound SMS is preserved even when AI is temporarily unavailable.
  • One company’s data is prevented from affecting another company’s customers.
  • Internal failures are shaped to avoid exposing sensitive technical details.
  • Platform updates go through stricter database, migration, and critical-journey checks.

What’s Next

We’re continuing the deeper price book integration, more precise labor and material calculations, recovery of interrupted booking workflows, and additional end-to-end checks for public booking.

If you notice a situation where the schedule, price, message, or status does not match what actually happened, tell us in Community. Those examples help us fix the entire workflow—not just the screen where the issue appeared.