Skip to content

Help centre

How it works, and where it stops.

81 articles, each one checked against the running product rather than against a plan. Every one of them ends by saying what it cannot do — the missing button, the report that does not exist, the thing you still have to do by hand. You can read all of this before you sign up, because finding out afterwards is how software loses a shop.

It is also nowhere near finished. Below every shelf is what we have not covered: 10 of them because the feature does not exist yet, and 7 because it does and we have not written it down.

Categories

Getting started

From signing up to a car on the board and an invoice out the door.

  • Signing up and signing in

    What Torqix asks for, what you get, and what happens the first time you sign in.

  • Setting your shop up

    Put who and where your shop is on the Profile, labour pricing and tax in Shop settings, hours and capacity in Schedule settings, and the words on your invoice before the first real job.

  • Getting your people on

    Adding somebody creates their account there and then and shows you a temporary password once. That password cannot open the account — the teammate finishes through a reset link sent to their own email.

  • Your first repair order, end to end

    Customer, then car, then estimate, then approval, then invoice, then payment. Roughly ten minutes the first time.

  • Finding your way around

    A dark rail of the places you live in, a second column of everything else beside it, and one keyboard shortcut that skips both.

Running the day

The board, My day, the schedule, inspections, parts — the work itself.

  • Creating an estimate from anywhere

    Open one estimate setup, choose or add the customer and vehicle there, write the first concern if you have it, and start the ticket.

  • The board and its three views

    Columns, List and Parts & Tires show the same live work from different angles, with your board lens saved for your next visit.

  • Working from My day

    Your assigned repair-order work in promise order, with the live punch, job approvals, open inspections and the next safe action in one bay-sized view.

  • Reading a ticket's Comms and Activity

    Use Comms for everything said or completed around one order, and Activity for the order's newest-first audit sentences.

  • Keeping every customer concern answered

    Keep the customer's questions in the order they raised them, show which job or short note answers each one, and review the open list before invoicing or closing.

  • Using the calendar and opening hours

    Book and move appointments on the day, week and month calendar, make closed time visible, and set the hours and bay capacity that new bookings must obey.

  • Online booking from your own website

    Turn on a public page that shows your real open times, link it from your own website, and confirm every request yourself before it touches the calendar.

  • Taking a part from the shelf through receiving

    Keep the parts shelf useful, price from markup bands, place purchase orders and record each delivery against its line.

  • Signing invoices and inspections

    When the shop requires it, a customer types their name on a portal invoice or completed inspection and the signed state becomes immutable evidence.

  • Promised time, and how late risk is worked out

    When you tell a customer the car goes home, write it down. The board then flags what is late or heading that way — and says 'unknown' when it genuinely cannot tell.

  • Holding a service back from the customer

    Keep a service on your ticket and off the customer's estimate — the shop total still carries it, their copy and its totals do not, and it cannot be invoiced until you show it.

  • The customer's signature, typed and drawn

    Approving work means typing a name. Drawing one as well is optional, adds evidence, and is never allowed to be the only way in.

  • The document library

    Find the PDFs Torqix already made and the quotes, tech sheets and how-tos your shop brought in.

  • Using the time clock

    Clock in against a job or shop time, read your own week, type in a shift that never got punched, and close a punch somebody left open — every change carrying a reason and a before-and-after record.

  • Where a punch was made

    The time log says whether each end of a shift happened at the shop, how far away it was, or that no position was shared — and no punch ever waits on one.

  • Your menu, your suppliers and your checklists

    Canned services group themselves by category and price at today's rate, the vendor book is searched and edited in the row, and every inspection template says when it was made.

  • What this car's tires have measured

    A car's Tires tab gathers every tread and pressure reading its inspections have taken, one row per visit and one column per wheel, newest first.

  • Keeping what you found with the car

    Vehicle findings keep an observation with the car after the visit ends, until somebody resolves it. Both screens sit behind a customer key, so a technician's findings arrive here through the inspection sheet.

  • Taking a digital inspection from checklist to estimate

    Build the checklist, record findings and photos at the car, and let an advisor choose which problems become work.

  • Finding a car by plate, VIN or year, make and model

    One box takes all three. It asks your own records first, so a car you already know never gets added twice — and it says plainly when a plate cannot be looked up.

  • What saves by itself, and what still needs Save

    On a repair order the hours, rate, quantity, price and every note box save themselves and the top right says so. Settings pages, message boxes and the Notes tab still need the button.

Money

Pricing, invoices, what you get paid, and who in the shop can see what a part cost.

Not covered here yet

  • Taking card payments — not built. Torqix has a deterministic simulator for test rows, including tokenization, authorization, capture, refunds and invoice payment links. It refuses live rows: no real processor adapter, merchant-account connection, hosted card collection, terminal or text-to-pay path exists. Cash, cheque and outside card terminals are recorded after the fact.
  • Requesting and applying deposits — not written. Percentage and fixed deposit requests ship, the money is recorded as taken on an outside terminal, and the next invoice absorbs it automatically. The article must say two things out loud: Torqix does not process the payment itself, and nobody chooses which invoice a deposit lands on.
  • Paying online from an estimate — not built. The customer portal approves work but cannot take live money. A test-only invoice payment link proves the processor workflow against test rows; it does not accept payment on an estimate, support a deposit request or move real money.
  • Connecting QuickBooks Online — not built. The raw-REST engine, exact-cent mapper, per-document reconciliation, manual retry, hourly drain and signed browser-bound authorisation flow ship and are tested. Torqix's platform owner still has to register the Intuit app and install its client id and secret; then each shop authorizes its own QuickBooks company. Until the platform item is complete the accounting screen offers no dead Connect button, and the books export remains the working way out.
  • Syncing to Xero — not built. The accounting engine speaks QuickBooks Online only. Xero has no transport, authorisation flow or mapping layer; the books export remains the way out.
  • Your bill, your plan, and cancelling — not written. Owners can review the subscription, record or reverse a cancellation, and see the displayed last day and read-only grace date. The scheduled clock and most write gates ship, but ticket actions remain outside the read-only boundary and there is still no subscription payment provider; the reachable workflow needs its own full article.

Customers and keeping them

Records, vehicles, messages, follow-ups and reminders. Included, not an add-on.

  • Retiring phone numbers and removing email addresses

    Keep a customer's active contact details accurate without mistaking a retired phone or removed email for something the 30-day trash can restore.

  • Chasing follow-ups and cold estimates

    Follow-ups gathers declined work and, when you choose a threshold, files inactive estimates off the board without changing or losing them.

  • Messages waiting and the notification bell

    The messages badge counts shop conversations awaiting a person, while the bell keeps a separate feed of events you have not seen.

  • Merging two customer records

    Compare two customer records, choose what survives, keep their history and contact details, and understand the 30-day undo.

  • Scheduling a customer message

    Choose the words, one channel, and a future time in your shop's timezone; the conversation shows who scheduled it and lets a person cancel any time before it leaves.

  • Campaigns to a list of customers

    Draft one bounded text or email campaign from a saved segment, inspect every recipient, approve the audience separately, then send in person-run batches with live consent checked each time.

  • Sending a quick status update

    Save a few lines, one photo, or a short MP4 on the ticket, send its private link through the customer conversation, and see when it was viewed and answered.

  • The digital glovebox

    A private link that gives a customer their own service history, paid invoices, shared inspections and what is due next — with no account to create.

  • Leads from your website

    Publish the work request form, put its link where your customers are, and turn what strangers send into customers — one human press at a time.

  • Service reminders and review requests

    Two worklists between visits — cars overdue for service, and paid tickets worth a review ask. Torqix writes the words; a person reads them and presses send, every time.

  • The conversation beside the ticket

    One customer's whole conversation opens next to the order, with a chip per ticket, a mark per channel saying what became of each send, and two switches naming where the next message goes.

  • Sending a customer a picture

    A photo attached in the conversation goes with the text and with the email, the full-size one stays on the conversation for your team, and Torqix tells you when a carrier will squeeze it or cannot carry it.

  • The sentences you send most often

    Message templates are the lines you say twenty times a week, written once, with thirteen placeholders the product fills in from the customer, the car, the ticket and your letterhead.

Not covered here yet

  • Texting a customer, and consent — not written. Two-way messaging and per-number consent ship and badly need an article.
  • Tasks about a customer — not written. Customer tasks can be created, completed, reopened and moved to the same 30-day bin as everything else, and an open task joins the follow-up worklist. Undocumented.

Reports

The opening dashboard, what the numbers mean, where they come from, and what they refuse to guess.

  • Reading the dashboard

    Four short answers at opening time: who owes the shop, which invoices are largest, where the work sits, and who is booked next.

  • Looking across your shops

    One organization-wide view of work, sales and receivables, with fleet and individual money separated and ratios recalculated from the underlying totals.

  • Finding the report you need

    The whole report library on one page, grouped by the question each report answers, searched from one box — and the ones your access does not include stay listed and say why.

  • Scheduling a report by email

    Choose a live report's delivery rhythm and date window, see when it will run, resume a paused delivery, or unsubscribe.

  • Your estimate close rate

    How much of the quoted work customers said yes to — by ticket and by value. Built so that revising an estimate can neither manufacture a lost sale nor make a declined one disappear.

  • Keeping score on promised times

    Every promise that came due in a window: what was first said, every move and its written reason, and — only where the record can prove it — whether it was kept.

Not covered here yet

  • Where each individual report's figures come from — not written. The library itself is documented now — how the reports are grouped, searched, starred, withheld and exported. What is still missing is a page per report: only the estimate close rate and the promised-times score have one, and every other report is explained by the single sentence on its row plus whatever notes it prints above its own table.

Shop settings

Hours, rates, tax, your invoice, how the shop looks and reads.

Not covered here yet

  • Adding a second location — not built. An account runs the one shop it was created with. Customers, vehicles and their history are already held at the organization, and the fleet and org-level roll-up reports pool over every shop an account has — but nothing creates a second one: the limit check `createLocationWithinPlan` is written and tested with no caller, there is no add-location screen, and the platform's Add a shop makes another organization. Whether the door opens, and what a location after the first costs, are both undecided.
  • Buying, porting and carrier-registering a texting number — not built. A shop can bring an already-provisioned Twilio or Telnyx number, seal that provider's credentials and record each US A2P 10DLC checkpoint in Settings. Torqix cannot search for, buy, port or release a number, and it never submits carrier registration: the shop owner completes that work in the carrier portal and records only non-secret progress here.

People and access

Roles, what each one can open, and how to check it rather than assume it.

  • Changing what a role can do

    The permission matrix is yours to edit, one key at a time, for this shop. Six keys and the owner column never move.

  • Making somebody set a new password

    Three controls on a person's card: send them a link, end their sessions, or stop their password working until they choose a new one.

  • Setting up two-factor

    Connect an authenticator, save the one-time recovery codes, trust or revoke a browser, and turn two-factor off safely.

  • Using a passkey

    Add, name, use, and remove the passkeys that belong to your Torqix account.

  • When Torqix support looks at your shop

    Support can read the shape of your account and cannot change a thing in it — unless you hand them a code and a time limit yourself.

Not covered here yet

  • Building a custom role — not built. Checked 2026-09-11. The six Torqix roles are still fixed — no create or delete, and a seventh role is not a thing that can exist. A shop can now give any role but Owner its own name and can move every non-reserved key between those five roles; clearing the shop name returns the built-in name without changing access.

The assistant

What it can see, what it will never do on its own, and how to turn it off.

  • The assistant drafts. You confirm.

    It can look anything up on its own. Anything that would change your shop — including a text, a note, a job, an estimate or a pricing matrix — comes back as a draft for a person to review.

  • Asking the assistant how to use Torqix

    Ask it product questions in plain words — how do I invite a technician, where do deposits live, can Torqix take card payments. It answers from these help articles, names the article it used, and says so honestly when the answer is that a feature is not built.

  • Setting up and testing the phone agent

    Add sealed provider credentials, test the receptionist without a call, choose its policy, and understand the consent, message and transcript records a real call requires.

  • Talking your findings onto the ticket

    A technician says what they found, the assistant sorts it into cause and correction, and nothing reaches the job until a person presses confirm.

Not covered here yet

  • Choosing and connecting a model in the shop app — not built. No shop can choose or connect the language model from the product. Model selection is deployment configuration; the provider-credential screen is for telephony and voice and does not expose an LLM picker.

Moving in from another system

Bringing customers, vehicles, parts and history across — and undoing it.

  • Bringing your old shop across

    Connect to Shopmonkey with an API key or bring CSV exports from any system. Both paths preview before writing; their boundaries and undo rules differ.

Not covered here yet

  • Importing your photos — not built. Checked again on 2026-09-11. Message history now comes across: matched on the source's own customer identity, linked to a ticket where the source names one, keeping direction, channel and the original time, stamped as imported, and incapable of being sent — the importer takes no transport and maps every row to a state that has already happened. Consent is untouched, and old conversation evidence is not treated as permission for a new message. Bringing conversation history across cannot be undone, because Torqix never deletes a message, and the import screen says so before the shop confirms. PHOTOS still do not come: the source returns signed URLs rather than bytes, there is no vendor-backed allowlist for the host named by that data, and the confirmation snapshot cannot safely keep the capability for later. Those URLs are dropped before anything is stored, and each reference is counted and reported as not fetched. The receipt now tells the shop to download the original arrival photos before ending Shopmonkey access and attach the evidence it needs to keep to the matching repair order in Torqix. Inspections do not come either.

The safety net

The trash, the 30-day window, the audit log, and getting your data back out.

Not covered here yet

  • Reading the audit trail — not written. The audit screen and hourly tamper-evidence route ship. The route refuses to seal anything until the platform operator supplies an audit signing key or keyring and AUDIT_CHAIN_DATABASE_URL with the required owner access; source code cannot prove those deployment credentials are installed, so the article must not blur scheduled into operating.

Reference

What this product's words mean, its shortcuts, and the short answers.

  • Sorting, paging and saving list views

    The shop's record and inventory lists show exact totals, use 50-row pages, sort before paging and keep the view in the URL.

  • What the words mean

    The pairs that sound interchangeable at first: repair order and quote, job and line, promised and due, estimate and invoice, ready and paid, follow-up and finding.

Not covered here yet

  • API keys, webhooks and the integrations catalogue — not written. An owner can mint a scoped API key, read the public REST surface against it, and point signed outbound webhooks at their own systems — all shipped, all undocumented. The integrations screen beside them is a status catalogue of seven named vendors rather than a connect screen, and saying so plainly is half the article.
  • Parts-supplier punch-out and two-way calendar sync — not built. Procurement defines one provider seam for PartsTech, RepairLink and Nexpart, with only a test fake behind it: Torqix has no vendor agreement, credentials or live client for any of the three. Calendar has a working read-only ICS subscription feed; it has no adapter, credential flow or integration card for two-way sync.

How this is written

No article here oversells the product.

A help centre is the second thing a shop reads and the first one it checks. If the first article promises a button that does not exist, nothing on the second one is believed — so every claim in here was written against the code that renders the screen, and where the natural sentence would have been wrong, the article says what actually happens instead.

What shipped and when is on the changelog. What we commit to as a company is on promises, with the same distinction drawn between what works today and what is still policy.