Where it counts · Before it happens

The job that will miss its due date, flagged the day before.

Remaining hours, the part's ETA and the due date you gave the customer, read together — so the risk shows on Home while there is still a bay and a phone call to fix it.

How it works

Three facts the shop already records, read together every hour.

  1. 01

    The due date is the customer's

    Set once at intake, in the customer's words. It moves only when a person moves it.

  2. 02

    The estimated ready time is computed

    From the hours left on the jobs, the parts' ETAs and the bay bookings. Never typed.

  3. 03

    At risk is the gap

    When the estimate runs past the due date, Home says so first — with the reassign, expedite, call and reschedule options side by side.

Home › Action required with a due date at risk and the Review risk view — from the fixture shop.

What you get

A calmer counter.

One queue, most urgent first
Home's Action required is the shop's exceptions as a table — the due date at risk, the reply not acted on, the car ready and the customer not told.
Changing the due date is never the default
Review risk shows what else could give — a bay, a part, a technician — before it offers a new date.
The customer hears first from you
Relay drafts the message; a person sends it. Nothing reaches the customer from a timer.
It reads the parts chain
A part needed with no purchase recorded is a risk the day it is needed, not the day it is missing.

Status

What this page promises is what the product does today. A date is a date, not a guarantee.

  • In the productDue date set at intake and moved only by a person
  • In the productHome › Action required, sorted by urgency, filtered to the role
  • Coming · November 2026Estimated ready time from hours, parts and bays, with the at-risk flag
  • Coming · November 2026Review risk with the options side by side

See it on your own shop's numbers.

Request a demo and a person replies by email, or start free and import on a Saturday.