Skip to content

Help centre

How it works, and where it stops.

123 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 2 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 in Shop info, your labor rate in Labor rates, your taxes on the sales tax list, hours and capacity in Hours, and the words on your invoice before the first real job.

  • Getting your people on

    Adding somebody creates their account immediately and shows a temporary password for a few minutes. That password cannot open the account — the teammate requests a reset link at sign-in, then chooses a private password.

  • 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.

  • Paying for Torqix

    Pay monthly by card, review the plan and its dates, or schedule cancellation from Plan & billing; Manage billing keeps the card, invoices and receipts.

Running the day

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

  • Creating an estimate from anywhere

    One New estimate screen: choose Estimate or Quick quote, find or add the customer and car, then write the first concern and create it.

  • Working a repair order, tab by tab

    What each tab of the order screen is for — services, summary, inspections, time, parts and files — and how to send it, take a payment and refund one.

  • Seeing warranty coverage when a car comes back

    Set the shop's month and mileage term once. Write-up then points to past paid work that is still inside both limits.

  • 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, the car you are clocked onto first and then in promise order, with the live punch, job approvals, open inspections and the next safe action in one bay-sized view.

  • Asking for a part or more work from the bay

    A technician sends an unpriced request from the ticket, then an advisor either turns it into an ordinary priced line or declines it with a note.

  • Reading a ticket's conversation and Activity

    Use Message for everything said to and by the customer, and Activity for the order's newest-first audit sentences. Activity is in the order's rail and under Summary, a page at a time for the whole trail.

  • 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.

  • Taking arrival photos when a car is dropped off

    Walk round the car one photo at a time on your phone, mark the damage that was already there, tap through fuel, mileage, warning lights and keys, and keep a record nobody can change afterwards.

  • Using the calendar and opening hours

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

  • Seeing and renaming your part categories

    See how the shelf is filed, how many parts sit under each category, and rename a category without changing past sales.

  • Correcting several parts at once

    Fix the quantity of up to eight parts under one reason, and read back every correction the shop has made.

  • Counting the shelf with a cycle count

    Count one bin, one vendor, one category or the whole shelf, see what disagreed, and post the differences to your stock.

  • Printing barcode labels for parts and bins

    Print scannable labels for one part, everything in a bin, or every bin front, on a label roll or ordinary address sheets.

  • Seeing the schedule in your own calendar

    Make a private link that shows the shop schedule in Google, Apple, Outlook or another calendar, and reset it if it gets out.

  • Your shop's own torque specs and labor times

    Keep the torque figures and labor times your shop has measured, mark the ones you stand behind, and see what people looked up and could not find.

  • Stocking, quoting and selling tires

    Put tires on the rack, find a size, quote three options, and sell tires from the rack onto a repair order with their DOT week on the line.

  • 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.

  • Merging two records for the same car

    Compare two cars with the same VIN, move one car's whole history into the record you keep, and understand the 30-day undo.

  • 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.

  • Working a service card

    Every service on an order is one card: its total, its authorization and Approve and Decline on top with everything else in one menu, its labor and parts as tables, and one line at the foot to add more and read its total.

  • 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 today's punches and your week, and use the manager-only correction trail when a saved punch needs to change.

  • 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 can be renamed and their recipe lines edited or removed, the vendor book is searched and each vendor is changed from its row's Edit panel, and every inspection template says when it was made.

  • What this car's tires have measured

    A car's History tab gathers mileage, tire readings and findings. Its Tires section shows every tread and pressure reading, 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.

  • Correcting a car's details, and where its mileage comes from

    Fix a VIN, plate, colour or unit number on the car's Vehicle info tab. History > Mileage log lists every odometer reading, including the one written on each ticket.

  • 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.

  • Finding any repair order, open or long closed

    Repair orders lists every repair order and counter sale the shop has written — what is on the board and everything that has left it — with status tabs that count what they hold, one search box, a date range and an export of what you see.

  • 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

  • Card readers at the counter — not built. Card payments through Torqix are text-to-pay only: a pay link the customer opens on a phone. Tapping, inserting or swiping a card on a counter reader needs card-reader hardware and is not built, so those are still recorded as Card from an outside terminal.
  • Paying online from an estimate — not built. A requested deposit can be paid by card from the signed estimate page, through the shop's own Stripe account. Paying the whole estimate online before work is approved is not built, and neither are pay-later financing or bank (ACH) payments: Checkout is card-only.
  • 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.

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.

  • The reply customers get when you are closed

    Turn on one automatic reply that tells anyone who writes after hours when you open next, in your own words.

  • Looking up what a customer agreed to

    Type an email address or phone number and read every consent decision on record for it, even if the customer record has gone.

  • 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.

  • Tasks about a customer

    Write down a call or errand on the customer, work open tasks from People to call, and keep the completed record with the person.

  • 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.

  • Running a fleet account

    A fleet's record in one place: its numbered units, every order with its PO, the live statement and one-cheque payments, payments taken, maintenance, and the account's terms.

  • Scheduling a customer message

    Choose the words, any photos or files, 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.

  • Automatic messages

    Your own words, sent when something happens and nobody presses send. Every one is off until you switch it on, texts only go to numbers with permission, and one switch pauses them all.

  • 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.

  • Recording customers' consent to be texted

    Torqix texts a number only once the customer's consent is recorded. Record it one customer at a time on their Customer info page, or for many customers at once from Settings › Text messages.

  • Texting with a customer

    Send from the customer's conversation after consent is on file, find replies in the same place, and file replies that Torqix cannot safely match to one customer.

  • 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.

  • What your customers see: approving, the glovebox and booking

    The three pages a customer opens from your links — approving an estimate, their glovebox and booking a visit — and what they press on each.

  • Leads from your website

    Publish the work request form, put its link where your customers are, and every request becomes its own order at the top of your Workflow board — until somebody takes it.

  • Working the work-request queue

    Read what a customer sent, start the one estimate that belongs to it, book the work when it is ready, or leave a clear human verdict.

  • Service reminders and review requests

    Two worklists between visits, plus separate opt-in automatic events for due cars and paid-in-full review asks. Both automatic switches start off and keep the same consent and safety stops.

  • The conversation beside the ticket

    One customer's whole conversation opens at the side of the screen: the messages fill it, one mark per channel says whether each send went, the reason waits in a tooltip, and two small toggles say 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 fourteen placeholders the product fills in from the customer, the car, the ticket, your letterhead and your work request form.

Reports

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

  • Reading the dashboard

    Six figures across the top, each against the last period, then who owes the shop, which invoices are largest and who is booked next, plus one link to the open work.

  • 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 reports a shop uses on one page, grouped by the question each answers, with related views and detail kept together.

  • 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.

  • Your effective labor rate

    What an hour of billed labor actually sold for — labor sold divided by the hours billed — where to read it, and why an older month says Not recorded.

  • 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, the effective labor rate the sales reports share has a page of its own, 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.
  • Porting a texting number, and releasing a number from Torqix — not built. Torqix staff connect a shop's already-provisioned Twilio or Telnyx number (setting-up-text-messaging), or Get a number from Torqix: a local number bought in the shop's own account with its US A2P 10DLC registration filed for it (getting-a-texting-number-from-torqix). Torqix still cannot port an existing number in, and there is no screen to release a number from Torqix or move from it back to the shop's own account — that is a request to Torqix support. On the shop's own account Torqix never submits carrier registration; staff record each step done in the carrier's console.

People and access

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

  • Asking for time off, and answering a request

    Ask for days away from the time clock, see where your request stands, and approve or decline requests as a manager.

  • 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.

  • Testers, recording and reporting a problem

    Torqix platform staff enroll a tester from the admin tenant page. The tester reads what is recorded and what never is, presses I understand, and is then recorded with PostHog, with every customer detail blanked out, until they pause.

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.

  • Set up the phone receptionist

    Choose what the receptionist says and may do, which languages it speaks and the voice callers hear, read the work a caller left behind, and understand what callers hear first, how it answers when asked if it is a person, and the human fallback around every call.

  • 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.

  • Explaining a repair to your customer in plain words

    Each service on an estimate can carry three short parts — what you found, why it matters, and what waiting means — drafted for you and sent only after you approve them.

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.

  • API keys and webhooks

    Give an integration only the API scopes it needs, keep the one-time key safe, and receive signed webhook notices without exposing customer details in their bodies.

  • 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

  • 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.