Repair management for shops and service centres
Every repair, from the counter to collection. Without losing track.
Check the device in with a ticket and QR code, quote, take photos, send the job to another shop and hand it back to the customer, always knowing where the work stands, where the device is and what is still to be paid.
Nothing to install. On the front-desk computer and on the technician's phone.
- Checked in
- today, 10:42
- Customer
- Ana Ferreira
- Device
- Lenovo ThinkPad T14
- Fault
- Dead after a thunderstorm.
01Three statuses, not one
A repair is never just “in progress”.
Most tools squeeze everything into a single status. Here the work, the device and the money run on separate tracks, and every change is logged: who, when and through which channel.
-
Technical
The work: not started, diagnosing, quote pending, waiting for parts, repairing, done.
-
Location
Where the device is: in store, on its way to another shop, at the service provider, collected by the customer.
-
Payment
What the customer paid: unpaid, paid or no charge. Invoices stay in your certified invoicing software.
What has stalled shows up on its own.
The dashboard lists what needs attention: customers who haven't replied in three days, parts late by a week, finished repairs not yet collected, collections still unpaid.
02How it works
From the counter to collection, in five steps.
-
01
Check-in
Customer, device, fault, accessories and condition. Print the ticket with terms and a signature line, or email it. The QR code takes the customer to live tracking.
-
02
Diagnosis and quote
An internal report and a customer report, an itemised quote with an expiry date, and the customer's answer on record.
-
03
Repair
Assigned technicians, internal notes, photos taken on the phone and the history of every status change.
-
04
Hand-off
If the job goes to another shop, their work order stays linked to yours, with a quote between shops and a confirmed return.
-
05
Collection
Collection on record and payment with amount, method and invoice number. The customer sees the repair finished on the tracking page.
03Shop network
Work with other shops without opening yours.
A shop can hand a repair to a specialist service provider. Each keeps its own ticket, notes and prices; only what was deliberately shared passes between them.
Shared between both
- Device details and the fault
- Status of the work
- The quote between shops and the answer
- The published technical report
- Photos you choose to share
- Return of the device, or keeping it for parts
Stays in each shop
- The end customer's contact details
- Customer price and margin
- Internal costs
- Internal notes and internal report
- Which employee did what
The separation is enforced on the server and checked by automated tests, not just hidden on screen.
04For the end customer
Customers know where things stand, without calling.
Every ticket carries a QR code that opens a public page, no account needed: the repair status, what is left to do and when to collect, with the shop's contact details. No costs, internal notes or technicians' names.
- A4 check-in ticket with terms and conditions and a signature line
- Ticket emailed to the customer at check-in
- Tracking by QR code, designed for phones
05AI assistant
Ask the workshop the way you'd ask a colleague.
Connect Claude, or another MCP-compatible assistant, to your account. It reads the repairs with exactly the permissions your account has, and changes nothing.
Of the end customer, the assistant only receives the name. Every query is logged, and each person can disconnect their assistant at any time.
What has been waiting for parts for more than a week?
Three repairs have been “Waiting for parts” for 7 days or more. The oldest is EK-2026-00088, a graphics card, stuck for 12 days. Shall I group them by technician?
06Your data
Built to be trusted.
Each shop in its own space
No search, list or file crosses from one shop to another outside a hand-off.
Roles that fit
Administrator, manager, technician and front desk, or roles you create by choosing each permission.
Activity log
Who did what, when and through which channel: web, AI assistant or system.
Private attachments
Photos and documents kept out of public reach, opened only by people who can see the repair.
07Plans
Pay for what your shop uses.
The essentials come with every plan. Modules are added when the shop needs them. Prices and limits on users and repairs per month are set for each shop.
In every plan
- Customers and devices
- Check-in with ticket and QR code
- Statuses, notes and technical reports
- Technician assignment and attention queue
- Photos and attachments
- Activity log
Modules
- Customer quotes
- Itemised quotes with an expiry date and the customer's answer.
- Payments
- Payment status, amount, method and invoice number.
- Shop network
- Send and receive repairs, quotes between shops and parts stock.
- Customer emails
- The check-in ticket sent by email.
- Custom roles
- Your own roles, with the permissions you choose.
- AI assistants
- Query the workshop from Claude and other MCP assistants.
08Questions
Before you book the demo.
Do I need to install anything?
No. It runs in the browser, on computers and phones. There is nothing to install or update.
Does it replace my invoicing software?
No. It records the payment and the invoice number; invoices are still issued in your certified invoicing software.
Can I use it without working with other shops?
Yes. A shop manages its repairs from start to finish; the shop network is a separate module.
Can technicians see costs and margins?
Only if their role allows it. Costs, margins and internal amounts are a permission of their own.
Is the AI assistant mandatory?
No. It only works for people who connect it to their account, it only reads, and it can be disconnected at any time.
See it working with your shop's repairs.
We book a demo and walk through the whole flow with examples from your day-to-day.
Book a demo