What shipped, and when.

Rooms your crew can actually talk in — photos, PDFs, spreadsheets, whatever needs passing around — with @names that reach the person you meant. It sits beside the chat you already had on a repair order, which is still there for talk about one car. Nothing said in a team room can be texted or emailed to a customer: it is not the kind of record this product sends from, so there is no setting to get wrong.

Type a plate, get the car — and get told plainly how confident the decode is and which fields it could not fill. A lookup that quietly guesses the engine is worse than one that admits it does not know, because the guess ends up on an estimate. Anything it got wrong is one tap to correct, and the correction is remembered.

Deleted customers, vehicles, jobs, parts, menu services and spec entries go to a trash you can see and restore from, rather than going away. Repair orders are not on that list, because they cannot be deleted in the first place — work history stays. Anything that cannot be restored says so before you press the button instead of after.

One grid: every role down one side, everything they can do across the top, and an answer in each box. Building it turned up nine places where the old roles gave somebody more than they should have had, and those are fixed. If you have ever asked "can the new tech see what we pay for parts?", the answer is now on a page instead of in somebody's memory.

Every screen in the product was rebuilt on one design system — one set of type sizes, one set of colours, real contrast under bay lighting, and a dark theme for the night shift. Bay mode keeps the comfortable reading density and grows every target to 56 pixels, so a wall tablet is genuinely usable with gloves on. The inspection buttons were 26 pixels tall in every density before this. They are not now.

Torqix installs to the home screen on Android and iOS and opens like an app, with no store to go through. It is the same product, not a stripped-down technician app — the thing every competitor's mobile reviews complain about.

Every database query the product made was crossing the country and coming back, because the servers had defaulted to one side of the continent and the database sits on the other. Sign-in paid that toll a dozen times over. The servers now run in the same region as the database. This one is written up in full on the status page, because how we found it matters more than the fix.

Pick an interval and the cars that are due find their way onto a worklist by themselves, derived from the work you actually finished. Nothing is ever sent automatically: the reminder is drafted into the ordinary message composer and a person presses send. Tell it to stop asking about a car and it stops, permanently.

Decide that a ticket needs the mileage, a phone number, an email or the VIN before it can be invoiced, and it does. When it refuses it names exactly what is missing, in shop words, all of it at once. An owner or manager can override with a typed reason, and the reason lands on the invoice's record where it can be read later.

A paid ticket offers to ask for a review. The message reads like a person wrote it, has a graceful way out in it for a customer who was not delighted, and goes through the same consent rules as every other text. It is never automatic — somebody chooses to ask, every time.

Write your quality checklist once and a ticket cannot reach ready until the boxes are ticked, or until somebody types why they are skipping it. The skip is loud on the record rather than silent, because a checklist is a promise to the customer and skipping one is a decision a person makes.

Every long text box in the product — the note you were writing, the message you were half-way through, the concern on a quote — saves itself as you type and comes back if you navigate away or close the tab by accident. This is the single most common complaint about the software this replaces.

Your filters, your hidden lanes and your density are remembered per person, not per shop, so the owner on a big monitor and the advisor on a laptop each get their own board back. When a filter is on, the board says so out loud — an emptier board should never read as a slower shop.

One shortcut, from any screen: a customer, a plate, a repair order number, a quote, an invoice number, even a dollar amount or a legacy order number from your old system. Every competitor in this category is criticised for click counts. This is the answer that does not require redesigning a single screen.

Techs and advisors can talk on the repair order itself — what they found, what it needs, whether to call the customer. It is visually unmistakable from the customer's message thread and the customer can never see it, which is proven by a test on every build rather than by us saying so.

One button on every page. It sends what screen you were on and any errors the browser saw, so you do not have to reproduce anything or describe it well. Phone numbers, emails, plates and VINs are stripped out before it leaves your browser — a support ticket is not a place your customer's details should end up.

Quotes have their own numbering, so a phone price check does not consume an RO number forever. When a quote turns into work it converts into a real repair order and keeps its old quote number on the record, at the price the customer was actually shown.

Build the jobs you sell every week once — labour and the parts kit — and drop one onto a ticket in two clicks. Hours are stored, rates are not: raise your labour rate and future work prices at the new rate while work already on a ticket keeps what it was quoted at.

Every job a customer declined or deferred lands on a worklist with a date, derived from your actual tickets rather than from anybody remembering to add it. "Quote it" copies the work into a fresh quote at the price the customer was originally shown, so following up never silently reprices the job.

Sell a box of blades to somebody who walked in, take the money, done — and it does not pretend to be a repair. A counter sale never counts as a car in the shop and never drags your average ticket down, while its revenue still lands in the day's sales.

Every movement of every part is recorded with a reason, and the on-hand number is recalculated from that history rather than nudged up and down — so the count can never disagree with the story behind it. An adjustment without a reason is refused. Going negative is allowed, loudly, because refusing to fit a part over a data problem stops a real repair.

The answer to a labour guide full of holes is not a better guide, it is your shop's own confirmed times, with the name of whoever verified them attached. Every lookup that finds nothing is recorded, so the list of holes worth filling writes itself, and the library gets more valuable the longer you work. It is yours.

Ask about a customer, a car, its history or today's numbers and it answers from your records instead of from a model's imagination. It cannot change anything: every action it proposes is a draft that a person reads, edits and confirms, and it cannot show the day's money to somebody who is not allowed to see the day's money.

Drop your old system's exports in — customers, vehicles, service history, inventory — and see a dry run of exactly what would happen before anything is written, including the duplicates it wants to merge. If the result is wrong, undo the whole import. The current reverse export is one button and names the record families it does and does not include.